@lonm said in What about a feature with a bar percentage till the next stable release?:
Definitely not a stupid idea. It's a good idea that's implemented in many places for other projects: https://github.com/Microsoft/vscode/milestones
However, Vivaldi tends to operate on a WIR (When It's Ready) methodology for releases. Having a progress bar to keep track to might somewhat restrict the V devs to operate in the manner that they prefer.
Feeling much better now, hah! Thank you for replying.
@quhno said in What about a feature with a bar percentage till the next stable release?:
@meymigrou Yes, that would be fun, but difficult for various reasons:
For one browsers have become hellishly complicated things over the years and sometimes it is hard to change things without breaking others, then because there are different development streams and the builds are picked as soon as a stream becomes stable enough to release to the public without breaking (too many) things.
Sadly that can't always be predicted and picking a % value is next to impossible.
Yeah I get it now. Still, that would be fun! :D
Having a publicly accessible bug tracker would allow users with the same issue to add additional information about the issue themselves
environment info e.g. OS, Vivaldi build, pages/urls that are causing the issue
workarounds for the issue
whether other browsers exhibit the same issue
upvote issues e.g. "I'm having this problem too" for bugs and "I would like this feature too" for feature requests, to give the dev team some additional data for deciding which issues to prioritize
insights on what may be the root cause of the issue (for knowledgeable
attachments e.g. screenshot or screen recording
From a user's point of view, it'd be nice to have access to bug tracker where information about bugs are gathered all in one place instead of having to search through various online communities or comment sections for that kind of information.
Having a publicly accessible tracker would also allow users to watch or subscribe to issues such that they'll be notified by email when there are changes on the bug report such as status change (e.g. unconfirmed->confirmed, closed as not reproducible, invalid) or new comments on the report. This is better than having to post on forums to ask about the status of bug(s).
Another thing I observed is that sometimes when the devs cannot reproduce the issue or don't understand the report, they simply close the issue without notifying the user(s) instead of requesting for clarification or more information from the user(s). Then the user(s) find out through the intermediaries that the bugs are closed even though they can still reproduce it, at which point the bug gets reopened. This is clearly suboptimal. If there were a public tracker, not just the user(s) who reported the bugs, other users can also chime in if the devs need more information to reproduce or understand the issue.
@pesala Yes sure, thank you and please forgive me for not being more thorough. I also know of the list, but it is a list of all votes, which is not a quick read when there are many of them. And anyway is always slower than some indication that I - specifically I - already voted.
edit: I mean, something like "likes" in many sites, even though a bazillion people also liked the same as I did, I don't need to scroll through the list to recall if I already "liked" it.
Weird... For me the top search box doesn't search current forum/thread only, instead it search every forum & thread with the search word. Then if i click on the gears icon, it will simply take me to the same search page as the 2nd search function.
My point 2 suggestion is useful for thread with too many post, & it suppose to only show post with matched word. This will save time as you won't have to read every post in a thread to get info you need.
That's a general forum problem. There is no way to sort a subforum by date of creation and we can't see, if we voted for the original post of a thread from the subforum overview, which would be useful for the feature request section, but less so everywhere else. I'm afraid this can't be solved with help of the extension, because there is no way to check for a vote before opening the thread. This would have to be implemented by Vivaldi.
@pesala Perhaps "intuitive" was the wrong choice of words. But that doesn't change the fact that even if new users coming to the forum try to use search, they may struggle to use it effectively if it acts in a away that they do not expect (and if they are new, that expectation is likely built off of web search engines).
I do not know of anywhere that the syntax of searching on this forum is explained, there are certainly no links to such documentation on the search page. The advanced search drop-down helps a little, but even that doesn't offer an explanation of how the boolean operators are in use.
@pesala I don't know what to say. Now I have the same result as your 499. I confirm that they are 572, so there is always something that does not work properly, there are 73 and are not few.
The fact remains that the first post is 10 days ago, and is not correct and makes it difficult to follow the new posts.
To you, also correctly shows the new discussions today?
@luetage @Pesala Thank you for the considered feedback. I'm really impressed that there was a conscious decision and that someone actually remembered it.
Kudos to the community, the forum and your generosity.
@mossman yeah - especially old website doesn't look well! But modern websites should be good! That's great when websites have their own dark theme but I haven't seen any website with multiple themes or any kind of settings to adjust brightness or saturation. So for some people my extension still can help. Initially I developed it for myself since I have color vision deficiency.
Use keytroke Ctrl+Shift+Del
Select Delete data for All Time
Select only Browsing History
Hit button Clear browsing Data"
Delete the entries you want to delete