Community
Participate
Working Groups
I opened this bug to track the remaining issues of bug 102081. The original bug was just getting too much to keep track of. There are a few lower priority issues left to consider with the FilteredTree changes: 1. make filtered tree work with categories (example, experimental Keys preference page) 2. identify other potential useful places to use a filtered tree (wizard selection pages, perhaps) 3. investigate race condition: + I believe there is a race condition between the refresh job and the effects of pressing enter. It's possible that the refresh job has not yet run (in response to filter text changes) when the "enter" key is handled by the traverse listener.
I think the instructions we provide in the text field could be improved too. "type filter text" is ambiguous and speaks in terms of the implementation. Some suggestions: - "Type words to match here" - in Mozilla Firefox, the Manage Bookmarks dialog has a text field labeled "Search:" - in Mozilla Thunderbird, the search box at top right has a search icon (with minimal extra graphic noise - see attachment)
Created attachment 29268 [details] Screen shot of Thunderbird search field
Doug, the issue you want addressed is 1. Add to list: 4) make filtered tree API, including investigation of whether or not having a generic superclass with tree and list implementations is worthwhile. Hmm, this is becoming a catch-all bug for general filtered tree issues. The issue Nick brings up in comment #1 is now a separate bug 119985
Changes released for bug 74795 adresses issue 1. Also, filtered tree has been added to wizard selection pages. The only remaining issue is the possible race condition so I am changing the title of the bug to reflect this.
Cannot reproduce the race condition is not reproducable.
