Please report any other irregularities here.
When the user clicks on the "new tab" button to open a new tab, the viewport immediate switches to browser initial state -- ie, a blank page with the titlebar at the top of the screen. It would give the user a better sense of what just happened, and be less jarring, if, instead, the sidebar remained on screen long enough to show the new tab appear in the sidebar (with the indicator ring/ highlighting around it), and the sidebar then scrolling away. This could all happen very quickly so that it wouldn't get annoying, but would give the user a quick explanation of where they've moved to and how to get back to the others. Not the same as bug 465281, which is more about an indication of tabs having opened in the background.
Marcio - Brad tells me that you had an interesting tab transition effect?
How important is this?
tracking-fennec: 1.0+ → 1.0-
Hi folks, sorry I was super buried releasing extensions that are not popular. Just saw my name again as Pav pinged this thread. Here is what I did in the early days of the N810-based work: A model proposition with a resident master page that would display multiple "thumbnails" representing canvas-based views of real tabs. The actual tabs were sort of hidden. If the user pressed the mouse/finger to a given thumbnail representation, it would zoom in, to that real page. At that point in the project it was not simple for me to kick mouse/keyboard events, through the canvas, and real-kick the actual browser element. So I was not able to quickly produce a case where the fake page was the real page for the user interaction. So in order to let the user zoom in and access that thumbnail I had to quickly flip from the virtual canvas world to the real browser tab. The transition component was the fact we could zooom out and in from these full screen views for a given tab/browser and be able to see the whole world of tabs/pages from higher angle. It was like Mac OSX spaces in a way, a poor version in terms of rendering.
Sounds like just a delay on hiding the sidebar would work here?
This seems to actually work now -- when I open a new tab, it shows up and then the awesomescreen appears, so I know what just happened.
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
Verified on n810 with 1.9.2 nightly build 20090921
Status: RESOLVED → VERIFIED
Litmus testcase updated to regression test: https://litmus.mozilla.org/show_test.cgi?id=7379
Flags: in-litmus? → in-litmus+
You need to log in before you can comment on or make changes to this bug.