Community
Participate
Working Groups
Build Identifier: 20090920-1017 If you create multiple documents and only Ctrl+PageDown can work instead of Alt+PageDown, but the description os the help guide is inconsistent with the actual behavior. (Not sure if it's a content issue or shortcut functionality issue.) Reproducible: Always Steps to Reproduce: 1.Open Ec and Ctrl+Shift+; to open the shortcut list pop up. 2.The shorcut of next Sub-tab says Alt+PageDown.
Probably a case where the documentation got out of sync with the behaviour. Could you please tell us which part of the documentation you refer to (which section, or which URL)? Thanks!
Sure. I did not find the detailed URL in the help document, but here is what you can do. Press the Ctrl + Shift + L (by default) to open a pop-up menu (looks like a large block of tooltip) which is shown in the right-bottom of the current view by default, and then scroll down to find the Next Sub-tab item, then you will find the issue I mentioned. Btw, I did not find the description for "Previous Sub-tab" (which can work if I say Ctrl + PageUp), should it also be covered here? (In reply to comment #1) > Probably a case where the documentation got out of sync with the behaviour. > Could you please tell us which part of the documentation you refer to (which > section, or which URL)? Thanks!
If I understood that right, this bug is only about the Ctrl+Shift+L popup, not about help documents (Help > Help Contents > ...). In 3.6, the platform defines "Next Tab" / "Previous Tab" commands, but does not assign key bindings by default, since all major platforms already support Ctrl+PageDown/PageUp natively (see bug 86248 comment 13). The Next / Previous Sub-Tab commands switch between sub-tabs inside a view or editor, e.g. in multi-page editors like the plugin.xml editor.
IF that's the root cause, at least we need to update the static content in the pupup to be consistent with the actual shorcutkey behavior =) That makes User clear. Thanks! (In reply to comment #3) > If I understood that right, this bug is only about the Ctrl+Shift+L popup, not > about help documents (Help > Help Contents > ...). > In 3.6, the platform defines "Next Tab" / "Previous Tab" commands, but does not > assign key bindings by default, since all major platforms already support > Ctrl+PageDown/PageUp natively (see bug 86248 comment 13). > The Next / Previous Sub-Tab commands switch between sub-tabs inside a view or > editor, e.g. in multi-page editors like the plugin.xml editor.
*** Bug 313679 has been marked as a duplicate of this bug. ***
For 3.7, I guess we should just assign Ctrl+PageDown/Up to the Next/Previous Tab commands. I know it's redundant, but we do the same for Cut, Copy, Paste, Delete, Select All, so we can do it here as well. But before we can do that, TraversePageHandler must be enhanced to work with embedded Swing widgets as well (see WidgetMethodHandler). [Implementation note: In TraversePageHandler 1.2, getMethodToExecute() returns the wrong method, but that's not a problem since the returned method is not used anywhere.]
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
