On Wednesday 2015-08-19 13:33 -0700, fantasai wrote: > (A) So far we already have on the standards track > > :-moz-read-only as :read-only ?? > :-moz-read-write as :read-write ?? > http://www.w3.org/TR/selectors4/#rw-pseudos > These were pushed to CR in > http://www.w3.org/TR/2004/CR-css3-ui-20040511/#pseudo-ro-rw > along with the other form-state pseudos, > so I'm not sure why they're still prefixed. > Are there issues with these selectors that we need to sort out?
Unprefixing bug: https://bugzilla.mozilla.org/show_bug.cgi?id=313111 which depends on: https://bugzilla.mozilla.org/show_bug.cgi?id=312971 which may or may not need more work done. > :-moz-placeholder sortof as :placeholder-shown > http://www.w3.org/TR/selectors4/#placeholder > due to requests for ::placeholder as a pseudo-elements It's actually ::-moz-placeholder, but we used to have :placeholder. https://bugzilla.mozilla.org/show_bug.cgi?id=1069015 covers restoring it. > (D) Things I can't tell whether they're things we should standardize: > > :-moz-first-node > :-moz-last-node These are what developers usually want :first-child and :last-child to be (maybe modulo whitespace?). > :-moz-full-screen > :-moz-full-screen-ancestor https://fullscreen.spec.whatwg.org/ has the former. > :-moz-focusring > > :-moz-broken > :-moz-user-disabled > :-moz-suppressed > :-moz-loading > :-moz-type-unsupported > :-moz-type-unsupported-platform Agree these are probably worth standardizing, although maybe not all of the last chunk. -David -- 𝄞 L. David Baron http://dbaron.org/ 𝄂 𝄢 Mozilla https://www.mozilla.org/ 𝄂 Before I built a wall I'd ask to know What I was walling in or walling out, And to whom I was like to give offense. - Robert Frost, Mending Wall (1914)
signature.asc
Description: Digital signature
_______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
