W3C home > Mailing lists > Public > www-style@w3.org > October 2013

RE: [css-regions] Named Flows, Elements and Box Generation

From: François REMY <francois.remy.dev@outlook.com>
Date: Sun, 27 Oct 2013 14:47:56 +0100
Message-ID: <DUB401-EAS105B378FBACCCD012514B30A50F0@phx.gbl>
To: "'Alan Stearns'" <stearns@adobe.com>, 'Håkon Wium Lie' <howcome@opera.com>, "'Johannes Wilm'" <johannes@fiduswriter.org>
CC: <www-style@w3.org>
± I believe this is the correct next step towards the end point you're after,
± Håkon. First, explain fragmentation via named flows and region chains.
± Provide scripting access so that people like Johannes do not have to wait for
± browsers to implement more 'first class citizens' of CSS. Then see what
± cowpaths we should pave from actual use on-screen in browsers.

Another way to state that:

- CSS Regions is the angular stone of distributed content. If you take CSS Regions and JavaScript, you can obtain the same result as any other proposal because it remains generic enough to solve all use cases.

- Experimentation will prove that some patterns are not /adequately/ solved by raw CSS Regions only. Those patterns will therefore get attention and new, specialized procedures will be put in place to cover them more adequately. 

We've seen this with "overflow: fragments" and we will continue to see this with page templates and another techniques in the future. I'm confident the "content" property will evolve dramatically in the process to make sure all layouts, even the most complex ones, can still be achieved in CSS without relying on dummy elements.

I do not believe "overflow: fragments" or "gcpm" alone or even combined can solve all the use cases for which we need content flows. And they don't have to. Bear in mind, implementation interest comes as use surges, and use cannot surge in an environment that's not favorable to experiments. Implementing CSS Regions in browsers will open the door to this experimentation. 


I think implementing CSS Regions is the right move right now, at least if we follow the Extensible Web Manifesto principles:

• Focus on adding new low-level capabilities to the web platform that are secure and efficient.
• Expose low-level capabilities that explain existing features, such as HTML and CSS, allowing authors to understand and replicate them.
• Develop, describe and test new high-level features in JavaScript, and allow web developers to iterate on them before they become standardized. This creates a virtuous cycle between standards and developers.
Received on Sunday, 27 October 2013 13:48:35 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:36 UTC