Edit ACTION-355: Look at seamless iframes and reconcile it with what we have in the spec. We should add the security consideration into iframe paragraph.

Title:

State:

Person:

Due Date:

(accepts formats such as "2005-05-17", "+1 week", "14 August 2005" and "next Thursday")

Associated Issue:

Or Associated Product:

Add notes (no markup allowed, URIs get automatically hyperlinked):

Related emails:

  1. [CSSWG] Minutes and Resolutions Seattle F2F 2011-07-25 AM: CSSOM, Regions, Floats/Exclusions (from fantasai.lists@inkedblade.net on 2011-08-02) (from fantasai.lists@inkedblade.net on 2011-08-02)

Related notes:

Seamless iframes were investigated but it is not the right solution for named flow from iframe, at least the way seamless iframes are defined now.

Seamless iframes work as if they were directly in the parent document DOM, which is not the behavior wanted from iframe-based named flow.

Seamless iframe *could* work if it had an option to integrate with layout but not be transparent for styles and DOM. Not sure if that is achievable, will propose as an option.

Alex Mogilevsky, 27 Jan 2012, 02:42:13


Peter Linss <peter.linss@hp.com>, Daniel Glazman <daniel.glazman@disruptive-innovations.com>, Chairs, Chris Lilley <chris@w3.org>, Bert Bos <bert@w3.org>, Staff Contacts
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: index.php,v 1.323 2013-12-19 14:47:09 dom Exp $