- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Wed, 05 Mar 2025 05:38:26 +0000
- To: public-css-archive@w3.org
Reviewed the questions with @jensimmons and @cookiecrook today... - 1a) Yes, we think `reading-order` should work even if you don't use `reading-flow` to reorder everything visually. An author may want to use `reading-order` to adjust the order of a few items without changing the order of everything else, so this ability should not require switching everything into visual order. - 1b) Yes, we think `reading-order` should work even without a second opt-in from the container. Authors will expect it to Just Work, and forgetting to set `reading-flow` on the container is likely to be a source of mistakes that don't get caught. - 1c) To address this forwards-compat concern, we think we should define `reading-order` to work on block-level boxes right now; and to work on inlines never. Use cases for block-level reordering include fixup of image-over-headline source order, and also fixup of weird source order choices due to desired float rendering. -- GitHub Notification of comment by fantasai Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11208#issuecomment-2699909338 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 5 March 2025 05:38:27 UTC