- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Wed, 17 Apr 2019 23:31:52 +0000
- To: public-css-archive@w3.org
There were proposals to handle this in css-scoping, see https://www.w3.org/TR/2014/WD-css-scoping-1-20140403/#fragment-scoping ... however, this is really hard! See the issues against ::first-line style resolution as an idea. It gets even worse with layout-affecting things like floats and margins, basically tossing in a large chunk of the layout complexity of overflow fragments https://www.w3.org/TR/css-overflow-4/#fragment-overflow or regions.. Bottom line, we'd like to do it, but it's super complicated, so it's not happening in the near future! But it **is** on the to-do list? Fwiw, pathway to getting there is 1. Fix ::first-line style resolution to be precise, understandable, interoperable, and usable -- we will reuse this model for per-page styles. 2. Allow some inheritable properties (like color) to be scoped per-page -- this gets us per-fragment style resolution. 3. Get overflow fragments specced and implemented, including variable-width fragmentation (see https://www.w3.org/TR/css-break-3/ ) -- this gets us per-fragment box layout. 4. Relax restrictions on what can be scoped per-page now that we can do per-fragment inheritance and style resolution and per-fragment layout! Unfortunately, each of these steps is a major project, implementation-wise. And not particularly easy to spec, either. I guess, follow along with ::first-letter fixes, each one is one step closer to per-page styling? :) -- GitHub Notification of comment by fantasai Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3780#issuecomment-484299261 using your GitHub account
Received on Wednesday, 17 April 2019 23:31:55 UTC