- From: Nigel Megitt via GitHub <sysbot+gh@w3.org>
- Date: Wed, 04 Oct 2023 09:47:25 +0000
- To: public-css-archive@w3.org
(b) seems like an elegant solution, in principle, though I wonder if we can implement it so that it is clear to authors how to get the behaviour they want. Are we really looking at word break opportunities, and their prioritisation? I'm willing to be persuaded either way, from a semantic viewpoint. From an implementer perspective, is it okay to have a potentially complex interaction between multiple properties that all affect the same layout process? I guess there are already other inputs to the process, like font size, so in principle this is not a new idea, but the two things seem _so_ closely related that I'm not sure. Perhaps there's a (c) add a new property value `grammatical-balance` that could address both these questions? -- GitHub Notification of comment by nigelmegitt Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8640#issuecomment-1746521984 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 4 October 2023 09:47:26 UTC