Malfunctioning vertical tabs when nesting disabled
- Edited
Steps to reproduce:
This just happened randomly many weeks into working in a profile, so I have no idea.
I think shortly before this happened I downloaded a PDF from Google and it caused an infinite redirect loop, maybe related. Since then it happened again without an infinite download redirect loop, just by closing some tab in a big hieararchy. I find it happens after a while of working in a profile. Closing and re-opening profile window seems to help.
Note that the tab containing nested hierarchy cannot be closed (on the screenshot it’s the one labeled with json-ld), and cannot be switched to.
Update: there is a bug with repro that causes a similar GUI glitch, with non-nested tabs: https://orionfeedback.org/d/4380-malfunctioning-vertical-tabs-when-nesting-disabled (that repro doesn’t work for this bug though).
Expected behavior:
—
Orion, OS version; hardware type:
Version 0.99.123-beta (WebKit 615.1.16.1) macOS Ventura 13.2 build 22D49
Image/Video:
- Edited
Fun: it didn’t happen on the above recording, but the label of the tab that contains the Open tabs nested hierarchy seems to randomly change when it scrolls out of/into viewport. (It adopts the name of various tabs in the hierarchy.)
This glitch went away when Orion was restarted.
- Edited
It happens a lot in the latest version, actually. I think it concerns the last tab in the list, when it has children. Closing the tree caused this bug to happen again on another long-running profile. It doesn’t happen on a clean profile, so I don’t have a solid repro.
- Edited
Generally for the purposes of posting a bug report, if you can't reproduce it, it didn not happen. There is nothing we can do with an unreproducible bug, compared to 1,500 other reported and reproducible ones on this site.
Vlad As a dev, I know it can be difficult/impossible to know what exactly happens in my own software just by looking at GUI state without knowing the steps that led to it, and not knowing what exactly happens indeed makes a bug more difficult to fix, but 1) submitting it as soon as encountered at least pins down the exact version where this started to be observed (thus where a regression was possibly introduced), 2) this could be useful to another user / someone might share a good workaround (e.g. that doesn’t require browser restart in this case).
Vlad Recorded video here.
