- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Thu, 21 Aug 2025 14:38:53 +0000
- To: public-css-archive@w3.org
The Houdini Task Force just discussed `[css-writing-modes] body propagation of writing-mode/direction/text-orientation and computed vs used styles`. <details><summary>The full IRC log of that discussion</summary> <alisonmaher> fantasai: we have in writing mode spec, prop writing mode from body to IMCB and root<br> <alisonmaher> ...for compat reasons<br> <emilio> q+<br> <alisonmaher> ...we resolved that changing comp value is hard. Should change used was proposed by emilio<br> <alisonmaher> ...we resolved to say computed value on root doesn't change, but used does for correct layout<br> <alisonmaher> ...problem is webkit has opposite problem<br> <alisonmaher> ...it is more work to change computed value instead of used<br> <alisonmaher> emilio: you can't change computed style<br> <alisonmaher> ...you need to add storage for this for the root case<br> <alisonmaher> ...changing writing mode implies ??<br> <iank_> i'm going to drop - but likely need Rune for this.<br> <alisonmaher> ...I assume you are saying it is convenient to change without affecting any side effects<br> <alisonmaher> ...you are proposing to not change how inheritance works after<br> <alisonmaher> florian: writing mode is inherited. If you change val of root based on body, only thing that inherits is body<br> <alisonmaher> emilio: no other things inherit from root<br> <alisonmaher> florian: you're right<br> <emilio> s/no //<br> <alisonmaher> fantasai: you want it to inherit to view transitions<br> <alisonmaher> emilio: no you don't want that<br> <alisonmaher> florian: that's why we have prop in first place<br> <alisonmaher> emilio: if you set on root, you can run into circularities<br> <alisonmaher> ...if you use container queries??<br> <alisonmaher> ...you don't need to set containment for style container queries<br> <emilio> @container style(writing-mode: vertical-lr) { body { writing-mode: horizontal-tb } }<br> <alisonmaher> florian: this affects enough things we can't do the better thing<br> <alisonmaher> emilio: assume elika's proposal doesn't change how logical properties behave<br> <alisonmaher> florian: from body down it wouldn't but other cases will<br> <alisonmaher> emilio: we get into weird state with writing modes resolving in different cases<br> <alisonmaher> ...this changes things<br> <alisonmaher> florian: can we just emit warnings when setting body instead of root<br> <alisonmaher> fantasai: prob won't help<br> <alisonmaher> emilio: you need to add extra storage for this<br> <alisonmaher> ....same problem with tables<br> <alisonmaher> ...either special case root to look at body at used value or add storage at box construction time<br> <alisonmaher> ...ugly either way<br> <alisonmaher> ...only sound approach<br> <alisonmaher> fantasai: take back to webkit<br> <alisonmaher> emilio: happy to help with questions<br> <alisonmaher> ...other approach is add a field to comp style like used vs original display<br> <alisonmaher> ...that would be easier for webkit<br> <alisonmaher> ....add used writing mode field that lives in comp that isn't exposed, set that instead<br> <alisonmaher> fantasai: will need to chat with team<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12586#issuecomment-3210886011 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 21 August 2025 14:38:54 UTC