W3C home > Mailing lists > Public > www-style@w3.org > December 2011

RE: [css3-regions] auto-generation, pagination, and code examples

From: Alex Mogilevsky <alexmog@microsoft.com>
Date: Sat, 10 Dec 2011 03:17:58 +0000
To: Håkon Wium Lie <howcome@opera.com>, W3C style mailing list <www-style@w3.org>
Message-ID: <D51C9E849DDD0D4EA38C2E539856928412D8023C@TK5EX14MBXC218.redmond.corp.microsoft.com>
± From: Håkon Wium Lie [mailto:howcome@opera.com] 
± Sent: Thursday, December 08, 2011 6:17 AM
± It seems that the current regions model create a fixed set of regions.

I have started a wiki page to collect ideas on generating pages with regions (and possibly templates) [1]. 

It is initially a cleaned up version of my email from right after TPAC [2].

It should include really simple ways to create page view too - like overflow:paged

± Are there other alternatives? I believe that the multicol module [3] offers an 
± alternative. Columns are generated as needed, and content flows from one to the 
± next -- just like for regions. If we added a way toBin select and style individual 
± columns, we could size and position them. They could escape the rigid framework 
± that multicol currently provides, and fly like angels. Angelic columns. 
± For example, to turn the first columnn of an article into something special, we 
± could write:
±   article { columns: 14em; }
±   article::column(1) { 
±      position: absolute; 
±      font-size: 1.2em;
±      visibility: collapse; /* makes space available others to use */
±      ...
±   }
± For now, this is just a strawman proposal. But it shows that it's possible to have 
± stylable regions that naturally combine auto-generation.

I would like to suggest taking a step back and look separately at the capability of fragmenting content (which in any sensible implementation should be shared between column, pages and regions), and then try to find the best language constructs to generate and format the fragment.

It is interesting to be able to extend columns like you suggest. It may be confusing too... my initial feeling is that using a new term for columns that move around will be easier to understand, yet for implementation it probably won't make much difference.


[1] http://wiki.csswg.org/spec/css3-region-templates 
[2] http://lists.w3.org/Archives/Public/www-style/2011Nov/0123.html 
Received on Saturday, 10 December 2011 03:18:31 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:50:11 UTC