Bug 216305 - [Viewers] FilteredTrees accessible listener speaks about preference pages
Summary: [Viewers] FilteredTrees accessible listener speaks about preference pages
Status: RESOLVED DUPLICATE of bug 227773
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 trivial (vote)
Target Milestone: 3.4 RC1   Edit
Assignee: Boris Bokowski CLA
QA Contact:
URL:
Whiteboard:
Keywords: accessibility
Depends on:
Blocks:
 
Reported: 2008-01-23 11:58 EST by Benno Baumgartner CLA
Modified: 2008-05-06 17:06 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Benno Baumgartner CLA 2008-01-23 11:58:04 EST 
I20080122-1600

In org.eclipse.ui.dialogs.FilteredTree.createFilterText(Composite) an accessible listener is installed for the filter text. 
Is:
 The listener returns following message '{0} {1} preference pages showing.'
Should:
 '{0} {1} items showing.'

The FilteredTree is API and may be used outside of the context of preferences.
Comment 1 Boris Bokowski CLA 2008-05-02 14:56:55 EDT 
Mass update - removing 3.4 target. This was one of the bugs I marked for investigation (and potential fixing) in 3.4 but I ran out of time. Please ping on the bug if fixing it would be really important for 3.4, and does not require API changes or feature work.
Comment 2 Benno Baumgartner CLA 2008-05-05 04:05:18 EDT 
(In reply to comment #1)
> Mass update - removing 3.4 target. This was one of the bugs I marked for
> investigation (and potential fixing) in 3.4 but I ran out of time. Please ping
> on the bug if fixing it would be really important for 3.4, and does not require
> API changes or feature work.

No API change, not a new feature, should not take more then 5 minutes to fix, important because we want to improve accessibility in 3.4...

Thanks
Comment 3 Boris Bokowski CLA 2008-05-06 17:06:03 EDT 
Turns out this was already fixed recently.

*** This bug has been marked as a duplicate of bug 227773 ***