What is the status of VB (=already reported bug/issue)?
-
Status of
- VB-14691 -
- VB-34482 -
- VB-38449 -
- VB-42578 -
- VB-42580 -
- VB-50906 -
- VB-51347 -
- VB-51349 -
- VB-51351 -
- VB-51352 -
- VB-51353 -
- VB-51354 -
- VB-51356 -
- VB-51360 -
Please
-
@LonM Status of the bugs are as follows:
VB-14691 - Closed / Cannot Reproduce
VB-34482 - Duplicate of VB-23668, which was fixed on 2018-09-30
VB-38449 - Duplicate of VB-38489, which was closed (cannot reproduce) on 2018-04-04
VB-42578 - Confirmed / Unassigned
VB-42580 - Duplicate of VB-33522, which is Confirmed / Unassigned
VB-50906 - Closed (Invalid) on 2019-03-26 (Reason: option is removed now)
VB-51347 - Open / Unconfirmed
VB-51349 - Open / Unconfirmed
VB-51351 - Open / Unconfirmed
VB-51352 - Open / Unconfirmed
VB-51353 - Open / Unconfirmed
VB-51354 - Open / Unconfirmed
VB-51356 - Open / Unconfirmed
VB-51360 - Open / Unconfirmed -
Status of VB-46204?
Thanks!
-
@GyozaGuy said in What is the status of VB (=already reported bug/issue)?:
VB-46204
Closed. Can Not Reproduce.
-
@mveljaca said in What is the status of VB (=already reported bug/issue)?:
can you please check the status of VB-51535 ?
Confirmed
-
I take it enough time has passed now for "the ink on them to dry".
Status of
- VB-50952
- VB-51056
- VB-51169
- VB-51190
- VB-51194
- VB-51209
- VB-51285
- VB-51298
- VB-51301
- VB-51306
- VB-51310
- VB-51331
- VB-51408
Please?
-
@naseyuki
It's closed as a duplicate of VB-48162, which is confirmed and assigned. Progress unknown. -
Hello, could I please get a status check on:
- VB-45879 -
- VB-46828 -
- VB-47976 -
- VB-48848 -
- VB-48966 -
- VB-49046 -
- VB-49323 -
- VB-49579 -
- VB-49792 -
- VB-50220 -
- VB-50337 -
- VB-50525 -
- VB-50944 -
- VB-51347 -
- VB-51349 -
- VB-51351 -
- VB-51352 -
- VB-51353 -
- VB-51354 -
- VB-51356 -
- VB-51360 -
- VB-51715 -
- VB-51716 -
- VB-51717 -
- VB-51755 -
Also, VB-51137/VB-51136 was marked as "invalid" - is there a reason given for this?
Thank you in advance.
-
Status VB-52226?
-
@Nlope Thanks for the report. It's too soon for any kind of a status update. The bug is only about 3 hours old, it is still Unconfirmed, and the only people who have access to the tools required to analyze your crash are currently asleep.
-
Status of VB-49398 and VB-44501?
-
@xyzzy Any new?
-
@Nlope Still too early to ask. Bugs do not move on a day-to-day time scale. There are thousands of them, because it usually takes weeks or months for them to be addressed. Only critical regressions or show-stoppers are usually looked at on same-day basis, and then mostly close to release. And even some of these cannot be solved with a quick turnaround.
On top of this, most of Europe, including Vivaldi, is in Holidays right now. We internal testers are not even getting nightly versions.
-
@Ayespy said in What is the status of VB (=already reported bug/issue)?:
@Nlope Still too early to ask. Bugs do not move on a day-to-day time scale. There are thousands of them, because it usually takes weeks or months for them to be addressed. Only critical regressions or show-stoppers are usually looked at on same-day basis, and then mostly close to release. And even some of these cannot be solved with a quick turnaround.
On top of this, most of Europe, including Vivaldi, is in Holidays right now. We internal testers are not even getting nightly versions.
I understand, thank you for the clarification.
-
@Gwen-Dragon Any news for some of these, particularly the unconfirmed ones?
Also here are some newer reports as well:
- VB-51794
- VB-51795
- VB-51821
- VB-52279
- VB-52280
-
Thanks, but I don't think I was clear enough. Is there any news for these as well?
@Gwen-Dragon said in What is the status of VB (=already reported bug/issue)?:
VB-51056 Unconfirmed
VB-51169 Unconfirmed
VB-51190 Unconfirmed
VB-51209 Invalid
VB-51298 Unconfirmed
VB-51301 Unconfirmed
VB-51306 UnconfirmedAlso after having a closer look through the changelog of snapshot 1525.4, VB-52279 was actually fixed as VB-51196
-
@AltCode Here's the updated status on these bugs:
VB-51056 Unconfirmed (FYI, I can't reproduce this)
VB-51169 Confirmed
VB-51190 Closed: Cannot Reproduce (Although there are other open/confirmed bugs about broken extension popup menus)
VB-51209 Closed: Invalid
VB-51298 Unconfirmed (Might require a HiDPI screen to reproduce)
VB-51301 Unconfirmed (I don't notice this problem)
VB-51306 Resolved: Duplicate (FYI, this setting was recently removed in recent 2.5 builds) -
Hey,
Could someone give me some info about these 3 old bugs?
I still reproduce every of them with the latest stable.- (VB-46918) Tab preview never close if "tab switch using mouse wheel" in a stack
- (VB-43950) Resize of tiled tabs is blocked if mouse moved too fast
- (VB-40353) Edition of theme name is too restrictive (can't erase and can't start like other name)
-
Hi, could I get a check-up of the following bug statuses?
- VB-52039 :
- VB-52051 :
- VB-52119 :
- VB-52216 :
- VB-52217 :
- VB-52218 :
- VB-52219 :
- VB-52248 :
-
Any update on this bug? It was reported on 17-08-2018 and reopened 8 months ago, but is still not fixed. It makes it very difficult to navigate in Explorer to open a local file if a video is in fullscreen in another window.
(VB-42709) Mouse Cursor Disappears on Open File Dialogue if Fullscreen window active
New screen shot sent to bug tracker.