Closed
Bug 26342
Opened 26 years ago
Closed 25 years ago
focused widgets give no visual cue in Dialogs
Categories
(SeaMonkey :: UI Design, defect, P3)
SeaMonkey
UI Design
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: cmaximus, Assigned: bugs)
Details
Overview Description:
I encountered this while verifying bug 18444. In the Open Web Location dialog there is no visual indication of which widget has
focus except for the text box. When you switch focus by tabbing through the elements you have no way of knowing which one is
focused until you tab back around to the text box.
Steps to Reproduce:
1) Select File|Open Web Location.
2) Click in the text field to set initial focus.
3) Hit tab 14 times noting the effects each time.
Actual Results:
Tabbing actually switches the focus as it should. The first time through the tab order the radio buttons do reflect their focus.
The Cancel and Open buttons do not. When you get back to the text field you see the flashing caret. When you continue to tab
through (second trip around) the radio buttons no longer show their focused state either. For every trip thereafter none of the
elements show any focus (except the text field, it always shows the caret when focused).
The reason I know the widgets recieve ocus but do not show is because it takes 7 tabs (the number of elements in the dialog) to
return to the text field AND if you press return after the 4th and 5th tabs the Cancel and open buttons fire off as appropriate.
Expected Results:
each widget should give some visual indication when it is focused.
Build Date & Platform Bug Found:
This bug exists on ALL platforms with at least the 2000020108 builds.
Additional Information:
I've assigned this to ben for now becuase I believe he did some work on that dialog, cc'ing law.
| Assignee | ||
Comment 1•26 years ago
|
||
claudius, do you notice this in all dialogs? if so, I suggest changing the
summary to "focussed widgets give no visual clue" or similar. I think hangas is
eager to land some widget fixes that may cure this problem.. stay tuned.
Status: NEW → ASSIGNED
| Reporter | ||
Comment 2•26 years ago
|
||
I've looked at some of the wallet dialogs and they exhibit the same symptoms so I've expanded the summary to be more
general. cc'ing hangas
Summary: focused widgets give no visual cue in Open Web Location Dialog → focused widgets give no visual cue in Dialogs
| Assignee | ||
Updated•26 years ago
|
Target Milestone: M16
| Assignee | ||
Comment 3•26 years ago
|
||
the new widgets that hyatt and I are working on will provide a solution of sorts
to this problem. more to come soon...
Updated•26 years ago
|
QA Contact: paulmac → jrgm
Comment 4•26 years ago
|
||
changing qa contact to jrgm@netscape.com on some random bugs
| Reporter | ||
Comment 6•26 years ago
|
||
looks like a dupe to me, they have different assignee's though so we should figure out who is the right person. I'll leave that to
jrgm :-)
Comment 7•26 years ago
|
||
Sure, claudius : when in doubt, punt!
Effectively these are the same bug, and I believe the correct owner is ben.
So, ben ... is this the definitive bug for "focus feedback" in XUL widgets.
Do we need some testcases for all the various widgets?
[By the way, I noticed that for checkbox, there is a selector that includes
:focus, it only applies to the <html> label, and is only triggered after five
TABs --
i.e., focus goes to checkbox,
then to checkbox > box,
then checkbox > box > box,
then checkbox > box > box > image,
and finally to checkbox > box > html).
Updated•26 years ago
|
Target Milestone: M16 → M17
| Assignee | ||
Comment 9•25 years ago
|
||
I do not know what focus feedback was to be provided for Modern, however, with
the exception of bug 25459, I think the focus feedback model used in Classic is
correct (Mac widgets other than textfield and tree do not receive focus, Windows
widgets receive focus except for button (see 25459)
Closing...
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Updated•21 years ago
|
Product: Core → Mozilla Application Suite
You need to log in
before you can comment on or make changes to this bug.
Description
•