Action Items
-
Alex
: need new proposal about the behavior of iframe or a different way to create named flow from url
Completed or Duplicated Actions
-
Alex
: to add an api to find out which element is in a named flow
Done: http://lists.w3.org/Archives/Public/www-style/2011Oct/0532.html
L-Action-7
-
Alex
: provide feedback on applicability of seamless frames in CSS regions.
Feedback: Seamless iframes don’t automatically provide the desired behavior. Seamless iframe is actually transparent for styling, it is intended to be equivalent to literally inserting the content into the master document, while what we want for indirect flow is the flow looking and behaving as if it was the document being shown in paged media – styled exactly as author intended for the content, with no interaction with styling of the template.
(as noted in http://lists.w3.org/Archives/Public/www-style/2011Sep/0098.html)
Issue 19 still need a resolution, but seamless iframe is not the answer.
-
Vincent
: rework the issue of resolved sizes for regions and come up with an alt solution for the group along with use cases and examples.
- Added comment to original issues following discussions with Rossen and agreement to stick to width:auto meaning 0.
- 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
-
Vincent
: insert issue markers / pointers in the spec.
- Done in 09/30/2011 CVS update to editor draft.
L-Action-10
-
Vincent
: rework ::region-before and ::region-after. Align with text-overflow.
- Proposal from David Hyatt to align with display:run-in to make :before and :after inline. Add a note saying that run-in on :after is more complex than on before, because you need to back-track.
- Done in 09/30/2011 CVS update to editor draft.
L-Action-15
-
Vincent
: WARNING (ISSUE STILL NOT RESOLVED). Add note that floats and scrolling divs are not breakable (and therefore overflow their region).
- 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
-
Vincent
: pagination region: what happens when flowing between containers of varying width? e..g., <div style="width:auto">…</div> flowing across regions of various widths. Action: Vincent to illustrate the use case (body with text flowing through multiple pages of different width, and width=100%).
- This issue is closed because of ACTION 351 where we decided that width:auto resolves to 0.
L-Action-17
-
Vincent
: Move content to ‘flow-from’ and note issue about concerns about interplay with ‘content’.
-
Vincent
: Come up with a proposal for breaks either a page-break or a general type of break or both and related use cases
L-Action-8
-
Vincent
: make sure circular dependencies are covered in the spec. and that the behavior is consistent with an invalid flow-from reference.
L-Action-11
-
Vincent
: write up new proposal based on Rossen’s ‘option 1’ discussion (see attached
) and raise as issue with the working group.
L-Action-12
-
Vincent
: add a note that the overflow property works as usual on all regions in case there is an overflow (e.g., borders and characters).
L-Action-13
-
Vincent
: rename content-order to region-order.
L-Action-14
-
Vincent
: update the spec. to specify that regions establish a BFC.
L-Action-16
-
Vincent
: Regions initial containing block: 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.
L-Action-6
-
Rossen
: respond to Alex’s email on auto sizing.
L-Action-1
- ✔ <html>Vincent</html>: remove all issues from draft and move to wiki.
L-Action-2
- ✔ <html>Vincent</html>: Remove “Integration with other specifications section”
L-Action-3
- ✔ <html>Vincent</html>: Update Wiki with remaining actions.
L-Action-4
- ✔ <html>Alex</html>: sendemail about content v.s., flow-from to www-style.
- ✔ <html>Vincent</html>: for this version we are limiting regions to be block containers; will add a note that this may be expanded in future levels
- ✔ <html>Vincent (duplicate of ACTION-354)</html>: Regions spec. editors to specify a model for breaking flow content across areas that accounts for regions, columns and pages. Build on paged media and propose behavior for nested flows breaks. See the breaks use cases page.
See: Vincent’s action email
See: Alex’s proposal
✔ <html>Vincent</html>: document the from-flow v.s. content issue and create proposal. See Issue 1 below.
Open Issues
Issue 23: should regions be non-breakable
URL : https://www.w3.org/Bugs/Public/show_bug.cgi?id=15189
Issue 20: List of region style properties
URL : https://www.w3.org/Bugs/Public/show_bug.cgi?id=15190
Issue 24: Creating a named flow from external resource
URL : http://www.w3.org/Style/CSS/Tracker/actions/376
Description : It should be possible to create a named flow directly from content of a separate document. Previously it was defined that <iframe style="flow-into:flowname"> its content into the flow, rather than itself. That special case was deemed inappropriate and removed from the spec with action (Alex) to propose a different syntax.
Option 1 : two ‘flow-into’ properties:
<iframe style="flow-into:flow1"> -- add iframe to flow as a replaced element
<iframe style="flow-content-into:flow1"> -- add content of the iframe to flow
ISSUE: that would apply to all elements, sometimes useful, but potentially with more special cases to deal with.
Option 2 : a separate property to specify what to add to flow, with the same effect:
<iframe style="flow-into:flow1; flow-source-type:element"> -- add iframe to flow as a replaced element
<iframe style="flow-into:flow1; flow-source-type:content"> -- add content of the iframe to flow
Option 3 : use a rule
@flow flow1 “story1.html”; @flow flow2 url(“story1.html”);
ISSUE: what will OM for programmatic flow source control look like?
Option 4 : seamless iframe