Re: [w3ctag/design-reviews] CSS Selectors 4 (#219)

@slightlyoff Responses:
  * Added ellipses as requested.
  * `:something()` can be added to shield part or all of any compound selector, not just the last one. There were some comments on whether to e.g. use bare parentheses to allow any part of the selector to be eliminated from the specificity count without affecting the structure of the selector, see https://github.com/w3c/csswg-drafts/issues/2143#issuecomment-358124504, but there wasn't much traction. If you think this is an alternative worth pursuing, please comment to that effect in the bug and/or file a new one? (I think the parsing issue in Tab's reply is solveable by having two forms, `:()` within a compound selector and `()` for higher-level annotation.)
  * Filed https://github.com/w3c/csswg-drafts/issues/2267
  * Tab and I believe that content that explains a feature belongs in the spec, not a separate document; in other words that the spec should be written understandable on its own, without auxiliary information, both to implementers and to authors. If there is insufficient context to understand the feature in the spec, then the spec should be improved (e.g. by adding examples, as you requested above). If you would like an archaeological record of the decisions made so that you can analyze whether they were good decisions or not, please let me know how detailed you want them and I will set aside the necessary time. A quick overview from memory should take a day or so. A disposition of comments since 2011 will probably take weeks.
* `::part` is for styling _parts_ of an input control, that is why it's a pseudo-element. The Input Pseudo-classes are for selecting _state_ of an input control, which is why they're pseudo-classes. In any case, these are quite old (they first appeared in the CSS UI draft ~2002, were published as CR in 2004, and were moved to Selectors much later) and most have been implemented and deployed already.
  * Do you have a suggested alternative? :) If you feel strongly about it, file an issue for bikeshedding~ ^_^


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/219#issuecomment-362756335