- From: Chris Harrelson via GitHub <sysbot+gh@w3.org>
- Date: Tue, 09 Feb 2021 21:55:32 +0000
- To: public-css-archive@w3.org
> > hidden-matching adds a new level of ambiguity about what content is "visible" Maybe I'm being pedantic, but I don't think "ambiguity" is the right word here. There is definitely a new state to consider, but it's not ambiguous what it means. > That's true. I think that's a useful distinction to make though, because I can't find another way to achieve this. Maybe we should work on examples of use cases though, I feel this discussion was not rooted in concrete cases, which tends to yield more questions than answers. Maybe there's something obvious that already would solve this and we didn't notice. Re: "I feel this discussion was not rooted in concrete cases": what do you mean exactly? There are real-world examples in the explainer and in this issue. Likewise multiple additional ones were mentioned in the discussion today. -- GitHub Notification of comment by chrishtr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5595#issuecomment-776269801 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 9 February 2021 21:55:35 UTC