Skip to content

Commit edbdb6e

Browse files
committed
spec/css3-regions: [Issue 24: Creating a named flow from external resource]
1 parent 18615a8 commit edbdb6e

1 file changed

Lines changed: 10 additions & 1 deletion

File tree

spec/css3-regions.txt

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -220,7 +220,16 @@ See Issue 1 below.
220220
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.
221221

222222
ISSUE: what will OM for programmatic flow source control look like?
223-
;Option 4 : <link> element
223+
;Option 4 : seamless iframe
224+
<iframe seamless style="flow-into:flow1" src="article1.html">
225+
226+
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.
227+
228+
It may be possible to add another attribute to HTML5 iframe for style boundaries.
229+
230+
Also, seamless iframe status is uncertain.
231+
232+
;Option 5 : <link> element
224233
<code>
225234
<link rel="namedflow" type="text/html-sandboxed" title="flow1" href="article1.html" />
226235
</code>

0 commit comments

Comments
 (0)