This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
spec:css3-regions [2013/05/23 16:50] – [CSS Regions Page] astearns | spec:css3-regions [2014/03/06 13:58] – [Archive Links] astearns | ||
---|---|---|---|
Line 47: | Line 47: | ||
* How does the transform property (and transform-origin) work for content split across multiple containers? | * How does the transform property (and transform-origin) work for content split across multiple containers? | ||
- | ===== Resolutions ===== | ||
- | This section keeps track of the CSS WG resolutions regarding the CSS Regions specification. A checkmark indicates that the resolution has been integrated at least in the latest editor draft. | + | ===== Archive Links ===== |
- | ==== Paris F2F February 2012 ==== | + | This page used to track resolutions and issues, but that was discontinued. The old tracking data can be found on these archive pages: |
- | [[http:// | + | [[spec:css3-regions:archived-resolutions|Archived Resolutions]] |
- | [[http:// | + | |
- | * ✔ Resolved: Bug 15159 for adding use cases to Regions spec is closed. | + | [[spec: |
- | + | ||
- | ==== TPAC October 2011 ==== | + | |
- | + | ||
- | [[http:// | + | |
- | + | ||
- | * ✔ Resolved: regionLayoutUpdate is an asynchronous event (Issue 10) | + | |
- | * ✔ Resolved: close open issue on whether flow-from turns an element into a region, reopen if needed later (Issue 18) | + | |
- | * ✔ Resolved: If content computes to normal, then the element takes the flow. (Issue 22) | + | |
- | + | ||
- | ==== Seattle F2F July 2011 ==== | + | |
- | + | ||
- | [[http:// | + | |
- | + | ||
- | * ✔ RESOLVED: Copying Flow Content is not something we are looking at right now. | + | |
- | * ✔ RESOLVED: Change the grid to integrate with CSS regions content through regular elements | + | |
- | * ✔ RESOLVED: Stick to content property and content: from-flow(< | + | |
- | * ✔ RESOLVED: change flow to flow-smthing | + | |
- | * ✔ RESOLVED: rename content: from-flow to content: flow-from | + | |
- | * ✔ RESOLVED: for this version [initial version of CSS Regions] we are limiting regions to be block containers | + | |
- | * ✔ (no changes needed) RESOLVED: we need breaks that are specific to containers they are part of. | + | |
- | + | ||
- | ==== Kyoto F2F, June 2011, Saturday ==== | + | |
- | + | ||
- | [[http:// | + | |
- | + | ||
- | * ✔ RESOLVED: Switch content-order to take < | + | |
- | * < | + | |
- | * < | + | |
- | + | ||
- | [[http:// | + | |
- | + | ||
- | * ✔ use ident for flow names in CSS Regions | + | |
- | * < | + | |
- | * ✔ content selection should not be mentioned in the spec. It is a UI issue. | + | |
- | * ✔ confirmed that the event propagation model should not be modified. | + | |
- | * ✔ make the section on DOM events model informative. | + | |
- | * ✔ CSS OM View: | + | |
- | * ✔ confirmed the current proposal (NamedFlow + Element interface extension) | + | |
- | * ✔ agreed to add event on changes to regionOverflow and flowRanges | + | |
- | ===== Action Items ===== | + | |
- | + | ||
- | [[http:// | + | |
- | * < | + | |
- | + | ||
- | ===== Completed or Duplicated Actions ===== | + | |
- | + | ||
- | + | ||
- | [[http:// | + | |
- | * < | + | |
- | + | ||
- | Done: http:// | + | |
- | + | ||
- | + | ||
- | L-Action-7 | + | |
- | * < | + | |
- | + | ||
- | **Feedback: | + | |
- | + | ||
- | (as noted in http:// | + | |
- | + | ||
- | [[http:// | + | |
- | + | ||
- | [[http:// | + | |
- | * < | + | |
- | * Added comment to original | + | |
- | * height:auto based on the content as usual. Add a note that this is inconsistent (between width and height) and that implementation feedback will be needed to finalize the best behavior). | + | |
- | * Done in 09/30/2011 CVS update to editor draft. | + | |
- | + | ||
- | + | ||
- | L-Action-9 | + | |
- | * < | + | |
- | * Done in 09/30/2011 CVS update to editor draft. | + | |
- | + | ||
- | + | ||
- | L-Action-10 | + | |
- | * < | + | |
- | * Proposal from David Hyatt to align with display: | + | |
- | * Done in 09/30/2011 CVS update to editor draft. | + | |
- | + | ||
- | + | ||
- | L-Action-15 | + | |
- | * < | + | |
- | * There has been a discussion about this with Alan Stearns, David Hyatt, Alex and Rossen. Do we have a resolution? How does this need to show in the spec. | + | |
- | * Meeting w/ Rossen and Alex, 09/27/2011: this issue should be dealt with in the pagination spec. | + | |
- | + | ||
- | L-Action-5 | + | |
- | * < | + | |
- | * This issue is closed because of ACTION 351 where we decided that width:auto resolves to 0. | + | |
- | + | ||
- | L-Action-17 | + | |
- | + | ||
- | * < | + | |
- | + | ||
- | + | ||
- | [[http:// | + | |
- | * < | + | |
- | + | ||
- | + | ||
- | L-Action-8 | + | |
- | * < | + | |
- | + | ||
- | L-Action-11 | + | |
- | * < | + | |
- | + | ||
- | L-Action-12 | + | |
- | * < | + | |
- | + | ||
- | L-Action-13 | + | |
- | * < | + | |
- | + | ||
- | L-Action-14 | + | |
- | * < | + | |
- | + | ||
- | L-Action-16 | + | |
- | * < | + | |
- | + | ||
- | + | ||
- | L-Action-6 | + | |
- | * < | + | |
- | + | ||
- | L-Action-1 | + | |
- | * ✔ < | + | |
- | + | ||
- | L-Action-2 | + | |
- | * ✔ < | + | |
- | + | ||
- | L-Action-3 | + | |
- | * ✔ < | + | |
- | + | ||
- | L-Action-4 | + | |
- | * ✔ < | + | |
- | + | ||
- | [[http:// | + | |
- | * ✔ < | + | |
- | + | ||
- | + | ||
- | [[http:// | + | |
- | * ✔ < | + | |
- | + | ||
- | See: [[http:// | + | |
- | See: [[http:// | + | |
- | + | ||
- | ✔ < | + | |
- | See Issue 1 below. | + | |
- | + | ||
- | ===== Open Issues | + | |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | ==== Issue 23: should regions be non-breakable ==== | + | |
- | ;URL : https:// | + | |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | ==== Issue 20: List of region style properties ==== | + | |
- | + | ||
- | ;URL : https:// | + | |
- | + | ||
- | + | ||
- | ==== Issue 24: Creating a named flow from external resource ==== | + | |
- | + | ||
- | ;URL : http:// | + | |
- | ; | + | |
- | ; | + | |
- | < | + | |
- | <iframe style=" | + | |
- | <iframe style=" | + | |
- | </ | + | |
- | + | ||
- | ISSUE: that would apply to all elements, sometimes useful, but potentially with more special cases to deal with. | + | |
- | ; | + | |
- | < | + | |
- | <iframe style=" | + | |
- | <iframe style=" | + | |
- | </ | + | |
- | ; | + | |
- | @flow flow1 " | + | |
- | @flow flow2 url(" | + | |
- | + | ||
- | ISSUE: what will OM for programmatic flow source control look like? | + | |
- | ; | + | |
- | <iframe seamless style=" | + | |
- | + | ||
- | This would almost work, but the definition of seamless iframe includes being transparent for DOM and styles, which is not what is expected from external flow. | + | |
- | + | ||
- | It will work *if* HTML5 iframe adds an option to isolate its DOM (a new attribute - ' | + | |
- | ; | + | |
- | < | + | |
- | <link rel=" | + | |
- | </ | + | |
- | The effect of loading the document via link and then sending content into a named flow should be identical to loading in an iframe and sending iframe content into a named flow with name specified in ' | + | |
- | + | ||
- | Concatenating multiple external documents in one named flow is difficult or impossible, so external flow should allow only one document per named flow. If multiple flow links have same title, the first one should be used. | + | |
- | + | ||
- | ISSUE: requires a change in HTML5 | + | |
- | ; | + | |
- | CSS3 generated content already has a way to include a file: | + | |
- | #source1 { content: | + | |
- | There is no requirement that HTML is supported as supported format in generated content (and there is no perecent either), but syntax would allow it. | + | |
- | Of course this is equivalent to iether iframe or seamless iframe (depends on how it is defined), but options to control the behavior of included content are entirely in scope of CSS | + | |
- | ; | + | |
- | ; | + | |
- | + | ||
- | ===== Issues Resolved by Editors ===== | + | |
- | + | ||
- | ==== Issue 21: When does a flow get created? ==== | + | |
- | + | ||
- | ;URL : none | + | |
- | ; | + | |
- | + | ||
- | < | + | |
- | < | + | |
- | .article{ | + | |
- | flow-into: thread; | + | |
- | } | + | |
- | .region{ | + | |
- | flow-from: thread; | + | |
- | } | + | |
- | </ | + | |
- | < | + | |
- | < | + | |
- | <div class=region> | + | |
- | </ | + | |
- | </ | + | |
- | </ | + | |
- | + | ||
- | ; | + | |
- | + | ||
- | ==== Issue 14: :: | + | |
- | + | ||
- | REPLACED BY ISSUE 20. THERE IS NO MORE :: | + | |
- | + | ||
- | ;URL : http:// | + | |
- | ; | + | |
- | ; | + | |
- | + | ||
- | + | ||
- | ==== Issue 2 : Auto-sizing of regions ==== | + | |
- | ;URL : http:// | + | |
- | ;Summary : Define intrinsic size of regions (currently zero, but there isn't a consensus that it's the best choice) | + | |
- | + | ||
- | There are different options for behavior of regions of undefined size, with different pros and cons. | + | |
- | + | ||
- | See [[http:// | + | |
- | + | ||
- | ;Proposal : Closed as it is addressed by ACTION-351 | + | |
- | + | ||
- | + | ||
- | + | ||
- | ==== Issue 3 : Regions Break ==== | + | |
- | ;URL : http:// | + | |
- | ;Summary : Should we add a new type of break for content in regions or should we specify which breaks should be honored when flowing content in regions? | + | |
- | ;Discussion : see URL and response from Alex. The general idea is that we should be able to define a region ' | + | |
- | ;Proposal: [[http:// | + | |
- | + | ||
- | ==== Issue 11: Should not allow pseudo-elements to move to a named flow ==== | + | |
- | + | ||
- | ;Summary : The current spec. says that the ' | + | |
- | ;Discussion : Since the ':: | + | |
- | ;Proposal : (latest editor draft as of 08/11/2011) ' | + | |
- | + | ||
- | + | ||
- | + | ||
- | ==== Issue 17: Behavior of broken floats ==== | + | |
- | + | ||
- | ; | + | |
- | ; | + | |
- | ; | + | |
- | + | ||
- | + | ||
- | ==== Issue 7 : CSS Regions Model ==== | + | |
- | + | ||
- | ;URL: http:// | + | |
- | ;Summary : the current model is that any element that has a) a layout it applies to its ' | + | |
- | ;Discussion : the current model allows chaining a block, a table and a flex box, for example, and that seem both complex and not most useful. | + | |
- | ;Proposal : modify the region model as described in the summary. If a flow-from property is set on an element that is not ' | + | |
- | ;Resolution : changed made to the specification (following WG resolution on limiting regions to be block containers http:// | + | |
- | + | ||
- | ==== Issue 13: Should we rename content-order to region-order? | + | |
- | + | ||
- | ;Summary : the current draft uses the ' | + | |
- | ;Proposal : rename the ' | + | |
- | ;Resolution : L-Action-13 to rename. | + | |
- | + | ||
- | ==== Issue 15: Do regions establish a new BFC? ==== | + | |
- | + | ||
- | ;URL : http:// | + | |
- | ; | + | |
- | ; | + | |
- | ; | + | |
- | + | ||
- | ==== Issue 16: Scrolling behavior for split blocks ==== | + | |
- | + | ||
- | ; | + | |
- | ; | + | |
- | ; | + | |
- | ; | + | |
- | + | ||
- | + | ||
- | ==== Issue 9: Absolute Positioning in Regions ==== | + | |
- | + | ||
- | ;Summary : The current spec. says that the containing block for an absolutely positioned element in a flow is the ' | + | |
- | ;Proposal : Modify the definition of containing block for positioned elements in a flow to match what CSS 3 Paged media says in section 3 (http:// | + | |
- | + | ||
- | The edges of the page area on the first page establish the rectangle that is the initial containing block of the document. | + | |
- | + | ||
- | For CSS regions, we should have: | + | |
- | + | ||
- | The edges of first regions in a region chain associated to a named flow establish the rectangle that is the initial containing block of the named flow. | + | |
- | + | ||
- | ; | + | |
- | + | ||
- | + | ||
- | ===== Resolved Issues: San Jose / Santa Clara Meeting, October 2011 ===== | + | |
- | + | ||
- | See: http:// | + | |
- | + | ||
- | ==== Issue 12: Should we allow multi-column elements to be regions? ==== | + | |
- | + | ||
- | Now tracked with https:// | + | |
- | + | ||
- | ;URL : http:// | + | |
- | ;Summary : should we allow the following: a magazine articles with regions galore on the first page, and then it switches to simple multi-column layout from page 2 and onwards | + | |
- | ;Proposal : May be an interesting feature, but should move to next revision of CSS regions for simplicity. | + | |
- | ;Resolution : [[http:// | + | |
- | + | ||
- | + | ||
- | ==== Issue 18: Interplay of flow-from and content ==== | + | |
- | + | ||
- | ;URL : http:// | + | |
- | ; | + | |
- | ; | + | |
- | ; | + | |
- | + | ||
- | + | ||
- | ==== Issue 10: Should the regionLayoutUpdate event by Sync or Async? ==== | + | |
- | + | ||
- | ;Summary : The current spec. says that regionLayoutUpdate event is Sync (see (http:// | + | |
- | ;Discussion : In DOM Level 3 events, all events are Sync. except ' | + | |
- | ;Proposal : Async. (implemented in IE10). | + | |
- | ;Resolution : Async. | + | |
- | + | ||
- | ==== Issue 22: content v.s. flow-from precedence ==== | + | |
- | ;URL : http:// | + | |
- | ; | + | |
- | ; | + | |
- | ; | + | |
- | + | ||
- | + | ||
- | + | ||
- | ==== Issue 19: Special behavior of iframe flow ==== | + | |
- | + | ||
- | ;URL : http:// | + | |
- | ; | + | |
- | ; | + | |
- | < | + | |
- | <iframe style=" | + | |
- | <iframe style=" | + | |
- | </ | + | |
- | ; | + | |
- | < | + | |
- | <iframe style=" | + | |
- | <iframe style=" | + | |
- | </ | + | |
- | ; | + | |
- | @flow flow1 " | + | |
- | @flow flow2 url(" | + | |
- | Note that with this approach, it is not possible to concatenate content from multiple urls in one flow (which may be a good thing, concatenation is not an expected use pattern for flow indirection feature. | + | |
- | + | ||
- | **pro* no special case for iframe | + | |
- | + | ||
- | **con* different OM for programmatic flow source control. | + | |
- | **con* content is provided/ | + | |
- | + | ||
- | ; | + | |
- | + | ||
- | Markup TBD | + | |
- | + | ||
- | + | ||
- | ; | + | |
- | + | ||
- | It is the smallest change and it achieves the goals of content separation; security issues appear to be understoood and require little new work to load/manage the separate content. | + | |
- | + | ||
- | However using a separate, new mechanism for content indirection (e.g. a link) may be cleaner | + | |
- | ; | + | |
- | + | ||
- | + | ||
- | + | ||
- | ===== Resolved Issues: Seattle F2F Meeting, July 2011 ===== | + | |
- | + | ||
- | See: http:// | + | |
- | + | ||
- | ==== Issue 4 : Copying Flow Content ==== | + | |
- | + | ||
- | ;URL : http:// | + | |
- | ;Summary : Should we allow copying content in a flow instead of moving it in the flow? | + | |
- | ;Discussion : this brings complexity and the benefits do not seem to offset that drawback (more complex DOM access, CSS OM View and computed style issues). | + | |
- | ;Proposal : in the first version of CSS Regions, only allows moving content to a flow, not copying. | + | |
- | + | ||
- | ==== Issue 5 : API to find which region displays an element in a named flow ==== | + | |
- | + | ||
- | ;URL : http:// | + | |
- | ; | + | |
- | ; | + | |
- | ; | + | |
- | ; | + | |
- | [supplemental] interface NamedFlow { | + | |
- | ... | + | |
- | Element[] getRegionsContainingElement(Element element); | + | |
- | /*or*/ | + | |
- | NodeList getRegionsByContent(Node contentNode); | + | |
- | } | + | |
- | or document | + | |
- | [supplemental] interface Document { | + | |
- | ... | + | |
- | Element[] getRegionsContainingElement(Element element, string flowName); | + | |
- | } | + | |
- | + | ||
- | + | ||
- | ==== Issue 6 : Compatibility with CSS Grid Layout Module Section 7.2 ==== | + | |
- | + | ||
- | ;URL : http:// | + | |
- | ;Summary : there should be a way to make grid cells regions. If the issue on grid cell is resolved as suggested in the section 7.2 issue, then it will be possible. | + | |
- | ;Proposal : have a RESOLUTION on section 7.2 issue that allows compatibility with CSS Regions. | + | |
- | + | ||
- | ==== Issue 1 : content: from-flow(< | + | |
- | ;URL : [[http:// | + | |
- | ;Summary : content: from-flow(< | + | |
- | ;Proposal : content: from-flow(< | + | |
- | + | ||
- | **cons**: | + | |
- | * collapses two different concepts together. | + | |
- | **pros**: | + | |
- | * clear interaction between ' | + | |
- | + | ||
- | ;Proposal A: flow-from: < | + | |
- | + | ||
- | **cons**: | + | |
- | * Need to define the precedent between the content property and the flow-from property. | + | |
- | * Concerns about the cascade implications of having flow-from: none | + | |
- | + | ||
- | + | ||
- | **pros**: | + | |
- | * Separate concepts (content for content belonging to the element, flow-from for getting a segment of content from the flow) | + | |
- | + | ||
- | + | ||
- | + | ||
- | ; | + | |
- | + | ||
- | This requires no alteration to the definition of ' | + | |
- | + | ||
- | + | ||
- | ==== Issue 8 : flow or flow-into ? ==== | + | |
- | + | ||
- | ;URL : none | + | |
- | ;Summary : the current specification uses the ' | + | |
- | ;Proposal : rename ' | + | |
- | | + | |
| | ||