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

Bug 313156

Summary:	[Preferences] Bad accessibility of Resize Tree in the preferences dialog
Product:	[Eclipse Project] Platform	Reporter:	Remy Suen <remy.suen>
Component:	UI	Assignee:	Platform UI Triaged <platform-ui-triaged>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	major
Priority:	P3	CC:	markus.kell.r, ob1.eclipse, prakash
Version:	3.6	Keywords:	accessibility
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:	stalebug

Description Remy Suen

2010-05-17 11:04:15 EDT

I20100513-1500

1. Window > Preferences
2. Click the inverted black arrow on the top right hand corner > Resize tree
3. Use the keyboard to resize the tree a bit left/right.
4. Hit 'Enter'.
5. The dialog is closed. :(
6. Repeat steps 1 to 3.
7. Try using the 'Esc' key this time.
8. See step 5. Frown again. :(

I can't figure out how to persist my changes without having this dialog close.

Comment 1 Remy Suen

2010-05-17 11:04:31 EDT

(In reply to comment #0)
> I can't figure out how to persist my changes without having this dialog close.

I can use the mouse but that doesn't count. I meant using the keyboard.

Comment 2 Oleg Besedin

2010-05-17 15:14:15 EDT

Hmm... you can "tab" away from it :-).

Comment 3 Prakash Rangaraj

2010-05-18 01:21:11 EDT

You guys are lucky. In Mac, none of the keys help (tab, esc, enter). Its always in the trying to resize the dialog. Only way is to use to mouse :-(

Comment 4 Markus Keller

2012-06-04 06:28:16 EDT

The only reason for this Resize Tree action to exist is accessibility.

But accessibility is broken on Windows (Esc and Enter keys should put focus somewhere else, like e.g. a Tracker does), and on Mac (no way out).

Comment 5 Eclipse Genie

2019-10-02 03:19:21 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.