Re: [csswg-drafts] [selectors-4] :valid-within / :invalid-within pseudo-classes

The CSS Working Group just discussed `:valid-within / :invalid-within pseudo-classes`.

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: :valid-within / :invalid-within pseudo-classes<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/3072<br>
&lt;dael> fantasai: Proposal to add valid-within and invalid-within pseudo classes. Seemed reasonable. Want to know if WG thought we should add<br>
&lt;dael> astearns: Anyone with a ready opinion?<br>
&lt;dael> fantasai: not urgent<br>
&lt;dael> astearns: Let's take this as a call for review and add comments in github<br>
&lt;dael> emilio: I can add comment to issue. Alternative is you have a pseudo class on the form and not just any arbitrary ancestor<br>
&lt;emilio> s/emilio/heycam<br>
&lt;dael> fantasai: I think that's what we do, but I'll check. If it's not we can make it work on form<br>
&lt;dael> fantasai: I think that would solve the use case. If it works on forms and fieldsets maybe.<br>
&lt;dael> fantasai: Looks like they're using at a smaller level for a segment of a form. Don't know if that solves the use case.<br>
&lt;dael> fantasai: We can continue that conversation in issue<br>
&lt;dael> astearns: Thanks for bringing it to attention. Please comment on the issue and we can see if we should take or modify this<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3072#issuecomment-430697499 using your GitHub account

Received on Wednesday, 17 October 2018 16:29:34 UTC