- From: Chris Rebert <csswg@chrisrebert.com>
- Date: Sat, 07 May 2016 23:11:42 -0700
- To: CSS WG <www-style@w3.org>, fantasai <fantasai.lists@inkedblade.net>, "Tab Atkins Jr." <jackalmage@gmail.com>
- Cc: Simon Pieters <simonp@opera.com>
On Tue, Apr 19, 2016, at 12:58 AM, Simon Pieters wrote: > In this pull request: > > https://github.com/w3c/web-platform-tests/pull/2843 > > we discussed whether the definition of :read-only pseudo-class makes > sense. > > WebKit follows the spec; Chromium and Edge don't; Gecko doesn't yet > support these. > > :read-only is defined as being :not(:read-write). As an example, a <div> > or an <input type=button> should match :read-only. Chris Rebert notes > that > he thinks this is unintuitive, and Francois Remy also questioned the > correctness of the MS Edge issue. Given contenteditable it's possible to > argue that any element can become writeable, though. > > Benjamin says he does not intend to change WebKit; meanwhile the Edge > issue appears to be closed as "By design". I don't care which way we go > here but someone needs to change their mind if we want interop here. :-) > > Chromium and Edge bugs about :read-only not matching the spec: > https://bugs.chromium.org/p/chromium/issues/detail?id=604154 > https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/7229941/ > > WebKit bug to update these selectors (fixed in 2014): > https://bugs.webkit.org/show_bug.cgi?id=136566 > > Gecko bug to implement :read-only and :read-write: > https://bugzilla.mozilla.org/show_bug.cgi?id=312971 Looks like Hixie asked the spec editors ~3 years ago in https://www.w3.org/Bugs/Public/show_bug.cgi?id=17812#c24 whether :read-only & :read-write could be removed from the spec altogether, but he never got a reply. So, Tab & fantasai, what are your thoughts on the possibility of dropping these? Cheers, Chris -- http://chrisrebert.com Browser 🐛 of the day: http://bugzil.la/1264125
Received on Sunday, 8 May 2016 06:12:05 UTC