Differences

This shows you the differences between two versions of the page.

--- spec:css3-regions:regions-scope [2012/01/23 16:48] – [Markup Clutter] astearns
+++ spec:css3-regions:regions-scope [2012/01/24 18:45] – [Overset Text] astearns
@@ Line 5: / Line 5: @@
 The issue of using region divs in HTML markup has been around since the initial presentation to the CSS WG ([[http://lists.w3.org/Archives/Public/www-style/2011Mar/0189.html|early feedback]]). Everyone seems to agree that there should be additional mechanisms to create stylable boxes in the render tree from CSS itself ([[http://wiki.csswg.org/ideas/pseudo-elements|pseudo-elements]]). Regions is not the only specification that could benefit from this addition to CSS.
 The question is whether Regions can progress before settling on a new box or slot generation mechanism.
-As it is, Regions can be used effectively with JavaScript. Perhaps the regions spec should use JavaScript instead of HTML markup to provide better examples of use?
 === Decision on Generating Regions ===
-  - Is a new box-generation mechanism required for css3-regions to progress?
+  - Is a new box-generation mechanism required for css3-regions to progress? If so, does it belong
-    - If yes, does it belong
+    - in css3-regions, or
-      - in css3-regions, or
+    - a separate specification that css3-regions must reference?
-      - a separate specification that css3-regions must reference?
-    - If no, how should css3-regions examples create regions?
-      - Keep the current div-based examples
-      - Change examples to use JavaScript
 ===== Overset Text =====
 The css3-regions spec currently does not do enough to address the problem of having more content than will fit in a region chain. While the last region in a chain can display overflow, that is not sufficient. What needs to be added to the regions spec to deal with this issue?
-As above, overflow can be addressed effectively with JavaScript. The spec intentionally provides enough OM for a script to detect overflow and either resize regions or create sets of regions from a page template.
+Overflow can be addressed effectively with JavaScript. The spec intentionally provides enough OM for a script to detect overflow and either resize regions or create sets of regions from a page template.
-Several solutions or improvements have been suggested to allow a region chain to fit flow content without resorting to scripting or the region-overflow property.
+Several solutions or improvements have been suggested to allow a region chain to fit flow content without resorting to scripting or overflow.
 A. Supporting height:auto on regions. Designs with no other region-generating mechanism can end with an height:auto region and be assured that all of the content will display. (This has been investigated before and issues with circular height calculations have been raised - [[http://www.w3.org/Style/CSS/Tracker/actions/351|Action-351]])