A bug’s life at Vivaldi
-
We depend on reports from the Vivaldi community to find and fix bugs. We appreciate your bug reports, and no reports are ignored. Here’s what happens with your bug report when it reaches Vivaldi browser.
Click here to see the full blog post
-
I don't have an issue with the Bug-tracker being closed, but I don't see why bug reporters cannot get some feedback on the bugs that they submitted, e.g.
- Marked as duplicate of {VB-Bug No)
- Fixed
- Cannot Reproduce
- By Design
- Assigned to developer
It would be much more encouraging than complete silence after the initial automated confirmation of submission.
I still have some very old bugs outstanding. It would be nice to know what is happening with them
(VB-8008) Gesture Mapping Column in Settings Can Collapse to Zero
(VB-8055) Icon to Show/Hide Panel on Wrong Side if Panels are on the Right
(VB-15651) Pinned Tabs Cannot be Stacked (but stacked tabs can be pinned by using a shortcut)
(VB-17208) Unable to Assign Rocker Gestures to Zoom in/out
(VB-18100) Find in Page Toolbar Shows with F3 Find Next -
@gwen-dragon said in A bug’s life at Vivaldi:
@pesala said in A bug’s life at Vivaldi:
would be nice to know what is happening with them
(VB-8008) Cannot reproduce (CNR)
(VB-18100) CNRThank you for checking. It is just as well I asked. Both are still very simple to reproduce.
(VB-8008) Resize the Settings dialogue horizontally:
(VB-18100) Press F3 in Opera 12.18, compare to Vivaldi.
I don't understand why (VB-8055) is invalid. Clearly, the icon should move to the right when the panels are on the right. Moving the mouse right across the monitor to close/open the panel makes it useless.
-
@gwen-dragon Do you understand the issue with F3 reported in (VB-18100) ? Firefox behaves exactly the same as Opera. Only Vivaldi shows the Find in Page Toolbar.
-
I understand the reasoning behind the tracker not being public, but I'd really like to see at least status information in a way. During the last year I sent in these tickets, there were 0 updates about them:
VB-23058
VB-25017
VB-27673
VB-25016
VB-26533
VB-27508
VB-27764
VB-27831 -
@pesala said in A bug’s life at Vivaldi:
I don't have an issue with the Bug-tracker being closed, but I don't see why bug reporters cannot get some feedback on the bugs that they submitted, e.g.
Marked as duplicate of {VB-Bug No)
Fixed
Cannot Reproduce
By Design
Assigned to developerSurely all the reporter would be concerned about is:
Duplicate - as he needs to look out for different bug number solution
Cannot Reproduce - can provide more information/detail (as you did above )Whereas:
By Design - does this mean it is now a Feature Request ?The progress (Assigned/Fixed) would be nice but not as important
- Assigned is simply an indication that none of above apply
- Fixed will appear in the changelog(s).
-
@tbgbe Assigned means someone is actually working on it. If it is not assigned then it is waiting in the queue so don't expect any progress for a while yet.
By Design means it's not regarded as a bug. E.g. if the panel button is supposed to be on the left when the panels are on the right, then it should be reposted in the Feature Request thread, which I did already.
@pesala said in Feature requests for Vivaldi 1.14:
Move Hide/Show Panel Button to Right If Panels are on the right
-
@pesala: While it was closed so long ago I no longer remember the exact reason why. Once a bug is made invalid it could mean we have other plans for it already, or its not something we want to put resources on (yet). Many invalid reports have ended up being picked up / fixed. Hope this gives some insight.
-
Makes no much sense in having a bug tracker when users of the software cannot even see other reported bugs or status.. not surprising you have so many duplicated...
mmb quick drag scrolling still broken. No idea what bug id that is.. probably reported multiple times.
-
@aronand There is a case for putting it somewhere else other than on the status bar, which may be disabled, but other places might have the same problem. Address bar space is precious and Extensions are on the right.
I have long used GestureRight, GestureLeft to show/hide the Panels.
-
@gwen-dragon: @pesala:
What Pesala said is what also I thought immediately after reading the article, because I have the same experiences with bugs reporting.
The problem with rejecting bug reports is that no-one who has reported an error knows what's happening to it and what status it has. For this reason unnecessary duplicates appear.
We should get at least some answer (by Jira system) when more information is needed to fully understand the bug, and those reports shouldn't be rejected.
It's not about answering in comments, because this does not solve the problem. -
@gwen-dragon:
@pesala:I don't see VB-18100 as an issue. On the contrary, I like the fact that I can see what is currently being searched in the page when I hit F3.
Moreover, it can also be used as a visual confirmation that the search has been done. For example when the searched word has not been found. If no toolbar is displayed, it may be misunderstood.When the search is done, you hit ESC anyway, at least to remove the yellow highlights of the results. As the toolbar is closed when hitting ESC, having displayed it does not even impact the user actions.
-
As others here have mentioned it would be great if users could view the issue tracker. Knowing whether or not a report already exists will cut down on duplicates and knowing the status can allow the reporters to provide more info if necessary.
-
Let's note also that the Sopranos are doing a huge work of triaging the bugs. It's worth saying it.
I totally agree that the status of the bugs should be public, at least for those filed by the public. Not necessary their name, or even the discussion in it. But just their status.
Finally, Vivaldi believes that a "good bug" is a bug that'll be filed again. Even if the first one is closed (by mistake or not), if it impact multiple persons, if it's important enough, somebody else will file it, and thus, there is another chance of fixing it.
-
I'm interested in knowing about your automated regression tests. What tools do you use, how tests are written, etc.
-
what about the idea from VB-34514 ?
btw: thanks for this article
-
Making the bug tracker publicly accessible is also a matter of missing JIRA licenses. It's simply not possible without paying a huge amount of money here.
OTOH sending status updates to the reporter's mail address is very much possible. We have been discussing this internally a few times already and I'm going to continue being an advocate for this. -
Clearing 94% of bugs per month is impressive.
It makes this regression, which essentially ruins a unique Vivaldi feature, all the more mystifying as it nears its one-year anniversary:
https://forum.vivaldi.net/topic/15429/tab-cycling-and-tab-opening-issues-while-using-tab-stacksPesala has it right. That needs to happen in some form. To think that a fundamental regression could go this long seems to put it in the same boat as feature requests, where you might get it one year but no promises (though be sure to upvote!).
They're two completely different things. One already exists and is bleeding out. The other hasn't been born yet.
-
@guilimote said in A bug’s life at Vivaldi:
Moreover, it can also be used as a visual confirmation that the search has been done. For example when the searched word has not been found. If no toolbar is displayed, it may be misunderstood.
When the word is found, it is highlighted. In the event that the search term is not found, nothing happens in Opera. In Firefox, the Find in Page toolbar is opened.
@guilimote said in A bug’s life at Vivaldi:
When the search is done, you hit ESC anyway, at least to remove the yellow highlights of the results.
You can press Esc, but you can just leave the highlighted text highlighted as a place-marker, or click on the page to remove it.
-
This is an interesting discussion, since I made the same argument 2 years ago and nothing has improved. Obviously I recognize that Vivaldi is a proprietary project and a public tracker may be difficult, but I think bug tracking still needs be more reciprocal. Regardless of anyone's stance on the subject, the current handling of bugs is inadequate. This can be demonstrated to a degree by the number of bugs in this thread that @gwen-dragon has reopened. Bugs should be expected and many more critical bugs do get fixed relatively quickly but unfortunately Vivaldi's development seems more focused on adding features than resolving regressions.
It's depressingly amusing that Vivaldi's team is so interested in communicating with their user-base when it comes to feature requests, yet seems almost opposed to putting the same effort into resolving issues. All the features in the world don't mean anything if they don't work correctly. I'm not trying to be disrespectful, however I always see; "You wanted xyz", "We heard you", "We listened"... Well, We've been saying we want improved bug handling, Is anybody listening?