Closed
Bug 494887
Opened 16 years ago
Closed 16 years ago
.inline-link cannot be selected with the keyboard
Categories
(Firefox :: Settings UI, defect)
Firefox
Settings UI
Tracking
()
VERIFIED
FIXED
Firefox 3.6a1
People
(Reporter: spitfire.kuden, Assigned: ehsan.akhgari)
References
Details
(Keywords: access, verified1.9.1)
Attachments
(2 files, 1 obsolete file)
(deleted),
image/png
|
Details | |
(deleted),
patch
|
dao
:
review+
|
Details | Diff | Splinter Review |
1. Tools -> Options -> Privacy -> History
2. set "Minefield will: Remember history" or "Minefield will: Never remember history"
3. presss Tab key some time
Actual Results:
.inline-link cannot be selected with the keyboard.
Expected Results:
.inline-link can be selected with the keyboard.
Comment 1•16 years ago
|
||
Yeah, this needs to block as it's the only way to clear cookies now. David Bolter said that he'd look into it.
Assignee: nobody → david.bolter
Flags: blocking-firefox3.5? → blocking-firefox3.5+
Comment 2•16 years ago
|
||
The easiest way to fix this is probably to add href="#" and "return false" to the onclick attribute.
Comment 3•16 years ago
|
||
(In reply to comment #2)
> The easiest way to fix this is probably to add href="#" and "return false" to
> the onclick attribute.
Is the absence of an onclick making them unfocusable? I was tracking down:
http://mxr.mozilla.org/mozilla-central/source/browser/components/preferences/privacy.xul#153
It looks like the links are inside a XUL <description> which I'm guessing is not expected to have focusable children.
I was also thinking of adding moz-user-focus: normal to the inline-link class:
http://mxr.mozilla.org/mozilla-central/source/browser/themes/winstripe/browser/preferences/preferences.css#115
Dão, your knowledge and insight is welcome here. Thoughts?
Assignee | ||
Comment 4•16 years ago
|
||
Dão's suggestion in comment 2 works. I can prepare a patch shortly if you want me to.
Comment 5•16 years ago
|
||
(In reply to comment #4)
> Dão's suggestion in comment 2 works. I can prepare a patch shortly if you want
> me to.
Ehsan, please go ahead! :)
Assignee | ||
Comment 6•16 years ago
|
||
Attachment #379694 -
Flags: review?
Assignee | ||
Comment 7•16 years ago
|
||
Comment on attachment 379694 [details] [diff] [review]
Patch (v1)
I also went ahead and removed the redness from the links as well.
Attachment #379694 -
Flags: review? → review?(gavin.sharp)
Assignee | ||
Updated•16 years ago
|
Assignee: david.bolter → ehsan.akhgari
Status: NEW → ASSIGNED
Comment 8•16 years ago
|
||
Comment on attachment 379694 [details] [diff] [review]
Patch (v1)
> cursor: pointer;
Are you sure that's needed?
>+.inline-link:focus {
>+ outline: 1px dotted;
> }
And that?
Comment 9•16 years ago
|
||
I'm guessing here, but it seems that inline-link was created because text-link was undesirable? Here is text-link:focus (from global.css):
.text-link:focus {
border: 1px dotted -moz-DialogText;
}
What is the desired UI here?
Comment 10•16 years ago
|
||
Comment on attachment 379694 [details] [diff] [review]
Patch (v1)
From an accessibility standpoint, thumbs up.
Assignee | ||
Comment 11•16 years ago
|
||
(In reply to comment #8)
> (From update of attachment 379694 [details] [diff] [review])
> > cursor: pointer;
>
> Are you sure that's needed?
Actually not, a ua.css rule (*|*:-moz-any-link) seems to cover that.
> >+.inline-link:focus {
> >+ outline: 1px dotted;
> > }
>
> And that?
Yes, without that the ua.css rule (*|*:-moz-any-link:focus) gets overridden by the .inline-link rule.
(In reply to comment #9)
> I'm guessing here, but it seems that inline-link was created because text-link
> was undesirable? Here is text-link:focus (from global.css):
>
> .text-link:focus {
> border: 1px dotted -moz-DialogText;
> }
>
> What is the desired UI here?
I'm not really sure. Dão pointed out that outline is preferred over border... Dão, could you please weigh in?
Comment 12•16 years ago
|
||
(In reply to comment #11)
> > >+.inline-link:focus {
> > >+ outline: 1px dotted;
> > > }
> >
> > And that?
>
> Yes, without that the ua.css rule (*|*:-moz-any-link:focus) gets overridden by
> the .inline-link rule.
So for the default outline, another option would be to use .inline-link:not(:focus) instead of .inline-link.
> (In reply to comment #9)
> > I'm guessing here, but it seems that inline-link was created because text-link
> > was undesirable? Here is text-link:focus (from global.css):
> >
> > .text-link:focus {
> > border: 1px dotted -moz-DialogText;
> > }
> >
> > What is the desired UI here?
>
> I'm not really sure. Dão pointed out that outline is preferred over border...
> Dão, could you please weigh in?
Yes, outline is the right tool here (except that messes with layout incorrectly), and at some point text-link should use that too. As for the color, I don't think we really care whether it's -moz-DialogText or the actual text color (i.e. -moz-nativehyperlinktext).
Updated•16 years ago
|
Whiteboard: [has patch][needs review gavin]
Assignee | ||
Comment 13•16 years ago
|
||
Updated based on Dão's suggestions.
Attachment #379694 -
Attachment is obsolete: true
Attachment #379718 -
Flags: review?(gavin.sharp)
Attachment #379694 -
Flags: review?(gavin.sharp)
Updated•16 years ago
|
Attachment #379718 -
Flags: review?(gavin.sharp) → review?(dao)
Updated•16 years ago
|
Attachment #379718 -
Flags: review?(dao) → review+
Updated•16 years ago
|
Whiteboard: [has patch][needs review gavin] → [has patch][has review dao][needs landing]
Comment 14•16 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Whiteboard: [has patch][has review dao][needs landing] → [has patch][has review dao]
Comment 15•16 years ago
|
||
Keywords: fixed1.9.1
Assignee | ||
Updated•16 years ago
|
Whiteboard: [has patch][has review dao]
Comment 16•15 years ago
|
||
Verified fixed on trunk and 1.9.1 on all platforms with builds like;
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2a1pre) Gecko/20090529 Minefield/3.6a1pre ID:20090529031523
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1pre) Gecko/20090531 Shiretoko/3.5pre ID:20090531031205
Status: RESOLVED → VERIFIED
Keywords: fixed1.9.1 → verified1.9.1
Target Milestone: --- → Firefox 3.6a1
Comment 17•6 years ago
|
||
Keywords: sec508
You need to log in
before you can comment on or make changes to this bug.
Description
•