Support :read-only and :read-write pseudoclasses (unprefix)
Categories
(Core :: CSS Parsing and Computation, defect)
Tracking
()
People
(Reporter: allan, Assigned: emilio)
References
(Blocks 3 open bugs, )
Details
(8 keywords, Whiteboard: [lang=c++][wpt-triaged])
Attachments
(3 files)
![]() |
||
Comment 4•15 years ago
|
||
![]() |
||
Comment 7•15 years ago
|
||
![]() |
||
Comment 9•15 years ago
|
||
![]() |
||
Comment 10•15 years ago
|
||
Comment 11•15 years ago
|
||
![]() |
||
Comment 12•15 years ago
|
||
Comment 13•15 years ago
|
||
Comment 14•15 years ago
|
||
Comment 15•15 years ago
|
||
![]() |
||
Comment 16•15 years ago
|
||
![]() |
||
Comment 17•15 years ago
|
||
![]() |
||
Comment 20•15 years ago
|
||
Comment 22•15 years ago
|
||
Comment 23•15 years ago
|
||
![]() |
||
Comment 24•15 years ago
|
||
![]() |
||
Comment 26•15 years ago
|
||
Comment 27•15 years ago
|
||
![]() |
||
Comment 28•15 years ago
|
||
Updated•15 years ago
|
![]() |
||
Updated•10 years ago
|
Comment 29•10 years ago
|
||
![]() |
||
Comment 30•10 years ago
|
||
Comment 31•10 years ago
|
||
Comment 33•10 years ago
|
||
![]() |
||
Comment 34•10 years ago
|
||
Comment 35•10 years ago
|
||
![]() |
||
Comment 36•10 years ago
|
||
Updated•8 years ago
|
Comment 37•8 years ago
|
||
![]() |
||
Updated•7 years ago
|
![]() |
||
Comment 38•7 years ago
|
||
Updated•6 years ago
|
Comment 39•6 years ago
|
||
I just came across this when working on bug 1577457, I assumed we supported this since all other browsers now support the unprefixed version.
Is there still a blocker to do this ?
Assignee | ||
Comment 40•6 years ago
|
||
Assuming we match the spec and the issues raised here don't affect our implementation we could give that a shot, IMO, but somebody needs to do the work of reviewing the implementation against the spec and fix any issue that comes up.
The change of unprefixing itself is trivial of course.
![]() |
||
Comment 41•6 years ago
|
||
Also, note that this bug definitely has open "depends on" bugs that would presumably need to be resolved.
But yes, the main problem is sorting out the spec-compliance angle.
Updated•6 years ago
|
![]() |
||
Updated•5 years ago
|
Updated•5 years ago
|
Assignee | ||
Comment 42•5 years ago
|
||
And remove some duplicated tests from WPT.
Depends on D75230
Updated•5 years ago
|
Comment 43•5 years ago
|
||
Emilio, could you update https://github.com/whatwg/html/issues/3501 and https://github.com/w3c/csswg-drafts/issues/127 as appropriate? I'm guessing they would be WONTFIX and we file a bug against Chrome? Assuming the information there isn't dated.
There's also a form-associated custom elements angle here, but this should probably not block on resolving that, see https://github.com/whatwg/html/issues/5016#issuecomment-544027904 if you want to read more on that.
Assignee | ||
Comment 44•5 years ago
|
||
(In reply to Anne (:annevk) from comment #43)
Done!
Comment 45•5 years ago
|
||
Updated•5 years ago
|
![]() |
||
Comment 46•5 years ago
|
||
bugherder |
Comment 47•5 years ago
|
||
Is there / should there be a bug for removing support of the prefixed version in some future?
Comment 48•5 years ago
•
|
||
Posted a site compatibility note for this. Also updated our compatibility checker to inform the deprecation.
Assignee | ||
Comment 49•5 years ago
|
||
(In reply to j.j. from comment #47)
Is there / should there be a bug for removing support of the prefixed version in some future?
Yes, there should be.
Comment 50•5 years ago
|
||
I've updated the documentation to cover this; see https://github.com/mdn/sprints/issues/3282#issuecomment-638970670 for the details.
Let me know if you need anything else. Thanks!
Description
•