- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Mon, 05 Feb 2024 20:56:36 +0000
- To: public-css-archive@w3.org
OK, I pushed some edits for this. There's actually two approaches we can take for `match-parent`:
- Compute to a set of strings, inherit as such.
- Essentially compute to "`auto`, but for _this language_", and inherit as such. Like alternatively you could implement as "look up the tree until we find a non-`match-parent` value and grab the content language from that element", but it's probably easier to just inherit it as a package deal. Idk if I should note that trick in the spec or not...
Anyway, I took the latter because it's more consistent with how `auto` works. But would appreciate WG review. https://github.com/w3c/csswg-drafts/commit/8b2623c9568a69939e7fc854c1148a263ac17b0a
@r12a Currently `auto` resolves on each element it's used, it's just now changed to look at the parent instead of the element itself. To get the behavior you have in the last example (Mais Lucy répondit: «Give George my love and tell him, ‹Muddle›».) you'd need to spec `q q { quotes: match-parent; }`. Do you think we should do this by default or is e.g. (Mais Lucy répondit: «Give George my love and tell him, “Muddle”».) a reasonable default?
--
GitHub Notification of comment by fantasai
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5478#issuecomment-1928079761 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 5 February 2024 20:56:38 UTC