Alternative page cycle mode is broken in 10.5

Alternative page cycle mode is broken in 10.5

Ever since the first Opera 10.5 alphas, the opera:config#UserPrefs|AlternativePageCycleMode is not functioning properly, and is infact unusable.

Basically what happens is that multiple tabs get marked as focused and are not focusable afterwards:


I've reported this bug as DSK-274447 back in december.


To reproduce:

1. Enable Preferences -> Advanced -> Tabs -> "Cycle without showing list"
2. Set opera:config#UserPrefs|AlternativePageCycleMode to 0 or 2
3. Open 3 or more tabs, then cycle tabs with ctrl+tab or RMB+scroll down


Why is this important

Before this mode was called "alternative", it was infact the default page cycle mode for "Cycle without showing list" since atleast version 7.23.

It was only put into opera:config after around version 9.0, when the firefox-style tab cycling became the default. There was a big outcry of users used to the old mode so the opera:config option was added.

This mode is AFAIK the only one that retains hierarchical parent - child relationships between tabs, so you can predictably browse through child tabs open from a parent tab etc.

I've been using this mode for atleast 7 years (since version 7.23) and Opera is pretty much unusable without it for me, I cannot upgrade until this bug is fixed.

Please guys, fix this for us long-time users...

Heh, I submitted three bugs surrounding this issue 279631, 279633, and 279645 which break down the smaller symptoms of the greater problem. The odd thing is cycling backwards (ctrl+shift+tab/RM‏B+scroll up) works as expected.

I know why the bug appeared. Rewriting MDI from scratch is gonna come up against cases like this. It's annoying that it hasn't been fixed though.

This is still broken in 10.60 alpha

Please, can you just look into this, the new Opera is basically useless without this behaviour, which I've been used to since Opera 7.23.

Indeed. But we would seem to be the only to people using that combination.

For reference I submitted three bugs around specific points of this issue: DSK-279631, DSK-279633, DSK-279645. Although looking at what I submitted for the last of those three I did a pretty good job of mixing up "forward" and "backward" when referring to tab cycling — I hope that hasn't caused it to be closed prematurely…

Originally posted by desktopteam:

Changelog

Desktop/UI

• Fixed DSK-274447 (Cycling tabs "without list" and "alternative page cycle mode = 0" adds focus to all cycled tabs)

It sounds promising, but they've only fixed the visual issue.
Bug DSK-279633: Alternative Page Cycle Mode/Window Cycle Type combination does not match the behaviour of <10.50 versions — remains unfixed.

Still, that adds two more fixed bugs to my bug tracker (read, collection of notes in Opera ). Always heartening to see progress.

Wooho

http://my.opera.com/desktopteam/blog/2010/06/08/more-bug-fixing

Fixed DSK-274447 (Cycling tabs "without list" and "alternative page cycle mode = 0" adds focus to all cycled tabs)

Thanks, Opera devs
You made my day

Heh, you beat me by 19 seconds

Originally posted by BtEO:

Bug DSK-279633: Alternative Page Cycle Mode/Window Cycle Type combination does not match the behaviour of <10.50 versions

How is it different?
From what I can tell, alt. page cycle = 0 behaves the same as before...

Download the 9.10 classic installer from ftp.opera.com and install it elsewhere to compare.

Or from my records:

DSK-279633: Alternative Page Cycle Mode/Window Cycle Type combination does not match the behaviour of <10.50 versions.

DSK-279633@bugs.opera.com

Describe:
1. Set: opera:config#UserPrefs|WindowCycleType = 2 (cycle without showing list)
2. Set: opera:config#UserPrefs|AlternativePageCycleMode = 0
3. Open any website with at least two links. (call this tab A)
4. Open any two links in background tabs. (call these tabs B and C)
5. Cycle tabs using either ctrl+tab or RMB+mouse wheel

Should happen:
With tab A selected tab B should be focused next.
The window stack should have rotated such that it was ABC and is now BCA (meaning if tab B is closed C gains focus)
Further cycling continues to place the top tab to the bottom of the stack.

Does happen:
Tab C gains focus, the stack now reads CBA.

Note that this only happens when cycling forward though tabs (ctrl+tab, RMB+wheeldown), going backward (ctrl+shift+tab, RMB+Wheelup) works as expected.

My use case was most typically forums. I'd open each sub-forum with a middle-click dopping each new one to the bottom of the stack. Then a single down scroll would focus the frist of the tabs and within each sub-forum I'd follow the same proceedure for threads closing the sub-forum tab until I get back to the original tab — where a single down scroll would bring me to all the opened threads in turn.