- From: Brian Kardell via GitHub <sysbot+gh@w3.org>
- Date: Tue, 05 Feb 2019 19:16:28 +0000
- To: public-css-archive@w3.org
@SelenIT - I think @alice or @cookiecrook can speak better to how unique that particular example is, but there's definitely additional relationships and complexity which I'm unsure even happens at the right stage right now to be considered in a selector. I believe some roles may actually rely on CSS application in order to determine their computed role, which would be problematic. I'm not suggesting that this isn't a thing that shouldn't be supported, and if we were designing all of the things fresh, this is a thing I would really want to keep in mind - I just wonder if we might not need to think about this a lot more and maybe work on some efforts to detangle - or maybe thinks about revise the ask somehow in a way that could be achievable but not just add confusion for developers about one more hard to understand kind of value? -- GitHub Notification of comment by bkardell Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3596#issuecomment-460766759 using your GitHub account
Received on Tuesday, 5 February 2019 19:16:29 UTC