Bug 8705 - REGRESSION: readonly text fields shouldn't get a focus ring
Summary: REGRESSION: readonly text fields shouldn't get a focus ring
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Forms (show other bugs)
Version: 420+
Hardware: Mac OS X 10.4
: P2 Normal
Assignee: Dave Hyatt
URL:
Keywords: Regression
: 11536 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-05-02 15:04 PDT by Adele Peterson
Modified: 2018-08-28 17:11 PDT (History)
3 users (show)

See Also:


Attachments
Add rule to html4.css and add readonly as a special case attr for style sharing. (3.29 KB, patch)
2007-01-11 23:00 PST, Dave Hyatt
mrowe: review+
Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Adele Peterson 2006-05-02 15:04:34 PDT
readonly text fields shouldn't get a focus ring
Comment 1 Karl Schramm 2006-06-27 20:57:15 PDT
This seems to be fixed in ToT.
Comment 2 Adele Peterson 2006-07-06 19:26:27 PDT
I still see this problem on TOT.  If you click in a readonly field, I see a focus ring.
Comment 3 Matt Lilek 2006-11-06 18:14:06 PST
*** Bug 11536 has been marked as a duplicate of this bug. ***
Comment 4 Dave Hyatt 2007-01-11 23:00:59 PST
Created attachment 12378 [details]
Add rule to html4.css and add readonly as a special case attr for style sharing.

There is talk of a read-only pseudoclass, but hot debate about what it should apply to.  That's why I decided not to add a new pseudoclass for this yet.
Comment 5 Dave Hyatt 2007-01-11 23:03:29 PST
Fixed in r18798.
Comment 6 Alan Cutter 2018-08-28 17:11:43 PDT
This bug was referenced in a Chromium bug: https://bugs.chromium.org/p/chromium/issues/detail?id=870062
It's not clear why readonly text fields had their focus ring removed given they can still be tab focused. Do you know the backstory to this change?