On 2015-08-19 4:33 PM, fantasai wrote:
(A) So far we already have on the standards track
:-moz-only-whitespace as :blank
http://www.w3.org/TR/selectors4/#the-blank-pseudo
**Please, if you all have better name suggestions, we welcome them.**
[ :blank imho sounds like a blank form element, which we might want
a selector for in the future. :/ ]
How about :whitespace-only? :-)
:-moz-dir() as :dir()
http://www.w3.org/TR/selectors4/#the-dir-pseudo
Unprefixing bug: https://bugzilla.mozilla.org/show_bug.cgi?id=859301
Do you know how similar :-moz-dir() and :dir() are? Based on a cursory
look, it seems like they're fairly similar...
:-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?
What does "user alterable" mean in the spec? Is <input type=checkbox>
user alterable? What about <input type=text readonly>? What about
<input disabled>? And so on... (I'd also ask about <input readonly
contenteditable> too but I don't think there's agreement on what that
even means...)
Also, I can't tell whether these are supposed to be opposites in the
spec. They are, in our implementation, I think.
:-moz-placeholder sortof as :placeholder-shown
http://www.w3.org/TR/selectors4/#placeholder
due to requests for ::placeholder as a pseudo-elements
According to the spec, this only applies to input, which is weird since
textareas can also have a placeholder, and IIRC :-moz-placeholder does
support that.
(D) Things I can't tell whether they're things we should standardize:
:-moz-first-node
:-moz-last-node
Why not? These sound useful to me...
:-moz-focusring
This seems useful as well.
Cheers,
Ehsan
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
