Bug 131389
| Summary: | Web Inspector: Preference to "always display focus ring" overriding site styles | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | James Craig <jcraig> |
| Component: | Web Inspector | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Enhancement | CC: | graouts, inspector-bugzilla-changes, jcraig, mike, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
James Craig
Web Inspector: ER: preference to "always display focus ring" overriding site styles. This can probably just be implemented as a user style sheet injection that adds a *:focus {} block using the !important directive.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/16556319>
Timothy Hatcher
What would this be used for?
James Craig
Many web sites and web apps have a proliferation of outline: 0, because designers dislike focus styles and misguided developers disable the outline entirely rather than implementing an alternative.
This allows an engineer to clearly see what the event target for keyboard events will be, even if the style is modified to not display focus on anything, or display as if focus is on an ancestor or descendant node. For example, some implementations of grouped widgets like tabs leave focus on each tab, and some leave focus on the tab list container. Some even ignore focus and change styles based on body element event delegation. SproutCore used to be this way, and the control libraries still hide focus outlines sometimes.
Related to bug 127998.