|
| 1 | + |
| 2 | +===== Resolutions ===== |
| 3 | + |
| 4 | +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. |
| 5 | + |
| 6 | +==== Paris F2F February 2012 ==== |
| 7 | + |
| 8 | +[[http://lists.w3.org/Archives/Public/www-style/2012Feb/0325.html|Paris FTF February 2012 Monday]] |
| 9 | +[[http://lists.w3.org/Archives/Public/www-style/2012Feb/0526.html|Paris FTF February 2012 Tuesday]] |
| 10 | + |
| 11 | + * ✔ Resolved: Bug 15159 for adding use cases to Regions spec is closed. |
| 12 | + |
| 13 | +==== TPAC October 2011 ==== |
| 14 | + |
| 15 | +[[http://lists.w3.org/Archives/Public/www-style/2011Nov/0713.html|TPAC October 2011, Sunday]] |
| 16 | + |
| 17 | + * ✔ Resolved: regionLayoutUpdate is an asynchronous event (Issue 10) |
| 18 | + * ✔ Resolved: close open issue on whether flow-from turns an element into a region, reopen if needed later (Issue 18) |
| 19 | + * ✔ Resolved: If content computes to normal, then the element takes the flow. (Issue 22) |
| 20 | + |
| 21 | +==== Seattle F2F July 2011 ==== |
| 22 | + |
| 23 | +[[http://krijnhoetmer.nl/irc-logs/css/20110725|Seattle F2F July 2011, Monday]] |
| 24 | + |
| 25 | + * ✔ RESOLVED: Copying Flow Content is not something we are looking at right now. |
| 26 | + * ✔ RESOLVED: Change the grid to integrate with CSS regions content through regular elements |
| 27 | + * ✔ RESOLVED: Stick to content property and content: from-flow(<flow-name>) |
| 28 | + * ✔ RESOLVED: change flow to flow-smthing |
| 29 | + * ✔ RESOLVED: rename content: from-flow to content: flow-from |
| 30 | + * ✔ RESOLVED: for this version [initial version of CSS Regions] we are limiting regions to be block containers |
| 31 | + * ✔ (no changes needed) RESOLVED: we need breaks that are specific to containers they are part of. |
| 32 | + |
| 33 | +==== Kyoto F2F, June 2011, Saturday ==== |
| 34 | + |
| 35 | +[[http://lists.w3.org/Archives/Public/www-style/2011Jun/0329.html|Kyoto F2F June 2011, Saturday]] |
| 36 | + |
| 37 | + * ✔ RESOLVED: Switch content-order to take <integer> |
| 38 | + * <html><span style="color:gray">Discussed syntax for pushing to/pulling from named flows.</span></html> |
| 39 | + * <html><span style="color:gray">Briefly discussed integration of regions with multicol and grid layout.</span></html> |
| 40 | + |
| 41 | +[[http://lists.w3.org/Archives/Public/www-style/2011Jun/0336.html|Kyoto F2F June 2011, Saturday, Vincent's notes]], [[http://lists.w3.org/Archives/Public/www-style/2011Jun/0413.html|WG Conference Call, [CSSWG] Minutes and Resolutions 2011-06-15]] |
| 42 | + |
| 43 | + * ✔ use ident for flow names in CSS Regions |
| 44 | + * <html><span color="gray">Disagreement on whether CSS Regions should use the 'content' property or have separate 'flow-from' property that overloads 'content: normal'.</span></html> |
| 45 | + * ✔ content selection should not be mentioned in the spec. It is a UI issue. |
| 46 | + * ✔ confirmed that the event propagation model should not be modified. |
| 47 | + * ✔ make the section on DOM events model informative. |
| 48 | + * ✔ CSS OM View: |
| 49 | + * ✔ confirmed the current proposal (NamedFlow + Element interface extension) |
| 50 | + * ✔ agreed to add event on changes to regionOverflow and flowRanges |
0 commit comments