15811 2012-01-31 13:47:12 +0000 Creating a named flow from external resource 2012-10-12 22:33:10 +0000 1 1 1 Unclassified CSS Regions unspecified PC All RESOLVED FIXED http://wiki.csswg.org/spec/css3-regions?&#issue-24creating-a-named-flow-from-external-resource model P2 normal --- 1 vhardy alexmog eoconnor stearns vhardy oldest_to_newest 63400 0 vhardy 2012-01-31 13:47:12 +0000 See: http://www.w3.org/Style/CSS/Tracker/actions/376 66140 1 stearns 2012-03-27 19:45:24 +0000 alexmog: we are not proposing to flow content from external resources at the moment alexmog: providing flow from external resources could be out of scope, or the Regions spec shouldn't restrict the origin of a resource ChrisL: I don't think it should be out of scope since the alternative would be to write script to pull in content alexmog: out of scope may be the wrong term alexmog: can regions assume that every element or node comes from the same origin? alexmog: I think it's useful to assume it but it is limiting * Bert thinks flowing <iframe seamless data="foo.html"> into a chain of regions would be cool... dbaron: given the seamless iframes feature of HTLM5, I'm not sure how much this matters dbaron: if you assume you have seamless iframes then you don't need features in CSS <ChrisL> is there a benefit to assuming that all the nodes are in the same document? * Bert put suspects that <iframe> will be a rectangle, like other replaced elements. <ChrisL> alex: yes, you can determine element order alexmog: but we want to allow indirection into a different document without changing the style of this document alexmog: seamless iframes does not have that option alexmog: I have a options on the wiki but I am not yet ready to commit to any of them http://wiki.csswg.org/spec/css3-regions#issue-24creating-a-named-flow-from-external-resource <dbaron> TabAtkins: there are security concerns with integrating iframes and, e.g., determining the height of the contents, without using the mechanisms in seamless iframes alexmog: one option involves using an iframe element; another uses a separate property; a third uses a flow rule. we can discuss these but work remains to evaluate the solutions as well as understand seamless iframes tabatkins: this should be discussed on www-style as there are issues with it alexmog: the Regions spec should note that the content of a named flow may come from another document vincent: should we retitle the bug? vincent: we can note in the spec that the current version assumes the content comes from the same document pointing to an issue to resolve it later Bert: this is not really a Regions issue but a general question of whether we can have replaced elements that are reflowing vincent: how do we deal with this issue? bert: put it on the agenda ACTION: alexmog to rework 15811 as a general issue of replaced content and flow 76185 2 stearns 2012-10-12 22:33:10 +0000 Options for a mechanism were added to the wiki, but we've decided to defer this feature to level 4. I've added a link to the level 4 wiki page http://wiki.csswg.org/spec/css-regions-4 and added a note to the current draft that this is a future feature: https://dvcs.w3.org/hg/csswg/rev/09b933bd65e2