[css3-regions][css3-pagination] use <TEMPLATES> for overflow generation

For regions, if a region overflows, have it use the HTML5 <TEMPLATES> tags to create new regions as needed.  This would be a  simple way to have auto-generated pages, without using javascript.

<style>
  article {
    flow-into: article-flow;
  }
  #region-1, #region-2, .extraLeftPage, .extraRightPage {
    flow-from: article-flow;
    region-fragment: auto; 
    overflow: visible; /* or hidden */
    overflow-template: overflowTemplate
  }
</style>

<body>
  <article>...</article>
  <div id="region-1"></div>
  <div id="region-2"></div>
  <template id=“overflowTemplate”>
    <div>
      <div class=“extraLeftPage”>
      <div class=“extraRightPage”>
    </div> 
  </template>
</body>

A single named-flow can generate a template into the DOM as needed, with other flows using that new DOM if necessary.

The only real issue seems to be how the templates can’t generate unique IDs when cloned, and have to generate Classes.

Also, I don’t have it use the “overflow” property since that already is specific for painting visibility, instead of document structure.  (I’m not sure if the UA’s require ID properties for regions flow-from?)

Please consider this for the spec.  I think it could be useful way to get the <TEMPLATE> tag used widely.  Also, it’s possible for other fragmenting schemes to use <TEMPLATES>, like CSS3-Pagination.  

I don’t think the CSS3-Paginations use of @slot rules is a good idea. Templates really should be part of the HTML instead of the CSS, as generated boxes are really organization of content (HTML), instead of style of content (CSS).  Also the @slot rules are very primitive and can’t natively generate things like <TR>, <TD>, <INPUT>, etc..

Thank you,

-bobby
---
Bobby Mozumder
Editor-in-Chief
FutureClaw Magazine
mozumder@futureclaw.com
1-240-745-5287
www.futureclaw.com
www.twitter.com/futureclaw

Received on Thursday, 8 May 2014 20:55:40 UTC