Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 347603

Summary:	Command + F8 does not cycle thru Perspectives properly
Product:	[Eclipse Project] e4	Reporter:	Ankur Sharma <ankur_sharma>
Component:	UI	Assignee:	Project Inbox <e4.ui-inbox>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	normal
Priority:	P3	CC:	emoffatt, pinnamur, prakash, pwebster, remy.suen
Version:	1.0
Target Milestone:	---
Hardware:	PC
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:	stalebug

Description Ankur Sharma

2011-05-30 03:06:11 EDT

Eclipse 4.1 Build I20110524-1000

Navigation -> Next Perspective works fine. But the key binding does not.

The key binding on Mac is Command + F8. pressing it first time brings up the popup menu fine. But switching the perspective, it stops working.

This worked fine on windows for me.

Comment 1 Praveen

2011-05-30 06:49:56 EDT

Just that the focus is lost after switching perspective. If the focus is set to any view/editor, then the key binding works fine.

Comment 2 Praveen

2011-06-03 09:54:16 EDT

Surprisingly, only TAB key is responsive after the perspective is switched. No other keys are accepted at this stage - pressing Tab pass the focus to Composite (which is the clientArea of the workbench shell) and then, all key-bindings are restored back.

Comment 3 Eclipse Genie

2018-10-04 10:47:55 EDT

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.

--
The automated Eclipse Genie.

Comment 4 Lars Vogel

2019-06-05 07:26:44 EDT

This is a mass change to close all e4 bugs marked with "stalebug" whiteboard.

If this bug is still valid, please reopen and remove the "stalebug" keyword.