Re: [selectors4] Features to Defer

On Tue, Jul 21, 2015 at 4:30 PM, fantasai <fantasai.lists@inkedblade.net> wrote:
> Prompted by plh, Tab and I just went over the Selectors 4 spec,
> to figure out what's ready to polish up and send to CR and what
> looks like it should stay in WD. Here's a list of what we propose
> to keep and defer:
>
> Keep:
>   * Everything in Level 3, obviously
>   * case-insensitive attribute selectors
>   * :matches(), :not()
>   * :dir(), :lang()
>   * :any-link, :current, :past, :future
>   * CSS UI selectors, possibly other than :read-only / :read-write (see
> below)
>   * :user-error
>
> Defer to L5 or Need More Info to Decide
>
>   ? :has()
>       Propose to defer.
>   ? :focus-within
>       Will keep if there's impl interest
>
>   ? :drop and :drop()
>       No idea, need info on impl status / interop
>   ? :read-only and :read-write
>       Vaguely recall someone wanting to drop this...
>   ? :placeholder-shown
>       Need to check impl status
>
>   ? :blank
>       Need to check impl status, would prefer a new name
>       (that doesn't evoke empty input fields)
>   ? :nth-child( An+B of <selector> )
>       Want to double-check satisfaction with syntax, impl interest
>   ? >> descendant selector
>       Bias towards dropping, want to check with implementers
>
>   ? Column combinator
>       Want to double-check satisfaction with syntax, impl interest
>   ? :nth-column() pseudo-class
>       Biased to at-risk
>
> Please send your thoughts on this list. :)
>
> ~fantasai
>


Why postpone :has again?  it's already been booted from like 1999 to
selectors 3, then 4, then "only for static profile" and now we want to
move it to 5?  why?  in the static profile this isn't hard and jQuery
has had it since, I think day one.

-- 
Brian Kardell :: @briankardell :: hitchjs.com

Received on Tuesday, 21 July 2015 21:44:10 UTC