CSS WG Blog Minutes Paris F2F 2015-08-27 Part II: Sele…

Minutes Paris F2F 2015-08-27 Part II: Selectors, will-change, Scroll Snap

Selectors

• Resolved: Put a SHOULD recommendation in for authors to use the double-colon not the single-colon pseudo-element syntax.
• Resolved: Keep section 3.6.3. (Pseudo-classing Pseudo-elements) overall. Add guidance to people developing new pseudo-elements on when to specify if they accept user action pseudo-classes. Remove the statement from :hover that it applies to all pseudo-elements: pseudo-elements must individually enable pseudo-classes they need.
• Resolved: Pseudo-element and pseudo-class combinations are invalid unless defined to be a valid thing that could potentially match something (for pseudo-classes on pseudo-elements)
• Resolved: :matches() and :not() are allowed on pseudo-elements. They are only valid when they contain only pseudo-classes that are valid in that context.
• Resolved: If any simple selector accepts a given type of selector it must also accept :not() and :matches(). If it accepts a combinator after it it also must accept :has().
• Resolved: Behavior defined for combinators after pseudo-elements as written in the pseudo spec is okay.
• Resolved: Close issue on naming :any-link because there’s no better ideas
• Resolved: Rename :user-error to :user-invalid
• Resolved: Add :user-valid, mark :user-valid and :user-invalid as at-risk
• Resolved: Drop :blank
• Resolved: Change the spec so :empty will trigger on white space- waiting on compat data to confirm this is an okay change.
• Resolved: Keep :drop(), mark at-risk.
• Resolved: Keep :nth-child(An+B of selector) where selector is limited to a compound selector containing only feature selectors. Absolutely no nesting :nth-child().
• :nth-child(An+B of selector), :nth-last-column(), :nth-column(), :drop, and :focus-within will be marked as at-risk.
• :has, :placeholder, :read-write and :read-only will stay in this level.
• :column() will be deferred to level 5.
• Resolved: drop >>
• Publication will wait until the interested parties have come to a conclusion about the algorithm describing how to evaluate a selector.

Full Minutes || Spec Referenced

will-change

• The will-change property will still be applied even if it doesn’t change. Though it may cause the page to slow down, that is because authors didn’t design their pages well, not a problem with the property.
• will-change with animations will still create a stacking context.

Full Minutes || Spec Referenced

Scroll Snap

• Mozilla expressed a concern about the changes discussed yesterday: they were worried that they would make the changes but no other browser would.
• A timeline was established to make the changes discussed so that browsers hopefully should have time to make the changes necessary to converge on implementation of the better behavior.

Full Minutes || Snap Points Spec, Snap Points Proposal

« Previous article Next article »