- From: Lea Verou via GitHub <sysbot+gh@w3.org>
- Date: Sun, 01 Sep 2024 03:50:56 +0000
- To: public-css-archive@w3.org
If we’re talking purely ergonomics, the answer seems simple: the em highlight uses red, unless some of it spans outside the `<em>` in which case that part only uses green, essentially treating `::highlight` the same as a child encompassing the element content in terms of inheritance. If that’s not possible to implement we can talk about how to reduce requirements from there to make it implementable, but I don't think disallowing custom properties from `::highlight` altogether is a good compromise. I suspect folks had not realized the full implications of the Mar 7 resolution when they resolved that way. Ironically, I had sent regrets for that call saying: > I would really like to be there for 9909, but I also don't want to delay it further and end up with web compat forcing our hand. :/ Is it too late to revisit? If we can implement what I’m proposing in the first paragraph there should be no webcompat issue since custom properties are currently dropped entirely. -- GitHub Notification of comment by LeaVerou Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9909#issuecomment-2323151486 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 1 September 2024 03:50:57 UTC