W3C home > Mailing lists > Public > www-style@w3.org > September 2011

Re: [css3-regions] iframe as content source

From: Robert O'Callahan <robert@ocallahan.org>
Date: Fri, 9 Sep 2011 00:15:10 +1200
Message-ID: <CAOp6jLZD_3crRfMzOiawZJB4vKAJx-17dQs7BAWTKgTqLk_XRg@mail.gmail.com>
To: Alex Mogilevsky <alexmog@microsoft.com>
Cc: David Hyatt <hyatt@apple.com>, Vincent Hardy <vhardy@adobe.com>, "www-style@w3.org" <www-style@w3.org>
On Thu, Sep 8, 2011 at 10:27 PM, Alex Mogilevsky <alexmog@microsoft.com>wrote:

>  Seamless iframe has been suggested, but there is a difference. 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.
>

True. Well, if the content is being flowed into arbitrary container shapes
then it's not necessarily being styled "exactly as the author intended", but
OK.

But it seems that what you want is basically "seamless" minus the first two
CSS features here:
http://www.whatwg.org/specs/web-apps/current-work/complete.html#attr-iframe-seamless
is it not?

If so, then extending or modifying "seamless" with more control over how
styles in the outer document affect the inner document seems like the way to
go.

Rob
-- 
"If we claim to be without sin, we deceive ourselves and the truth is not in
us. If we confess our sins, he is faithful and just and will forgive us our
sins and purify us from all unrighteousness. If we claim we have not sinned,
we make him out to be a liar and his word is not in us." [1 John 1:8-10]
Received on Thursday, 8 September 2011 12:15:40 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:44 GMT