Bug 117080 - [CSS Regions] <iframes> are not fragmented between regions, but instead they are treated as monolithic elements
Summary: [CSS Regions] <iframes> are not fragmented between regions, but instead they ...
Alias: None
Product: WebKit
Classification: Unclassified
Component: CSS (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
Depends on:
Blocks: 57312
  Show dependency treegraph
Reported: 2013-05-31 08:53 PDT by Mihai Balan
Modified: 2014-04-01 05:45 PDT (History)
3 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Mihai Balan 2013-05-31 08:53:07 PDT
<iframe>-s are not fragmented between regions, but instead they're treated as monolithic elements and they get sliced. This happens for both seamless and "normal" iframes.

Note that this breaks compatibility with the Regions implementation in IE10.
Comment 1 Alan Stearns 2013-05-31 14:02:00 PDT
The regions implementation in IE10 takes the *content* of the iframe and puts it into the named flow. So this behavior by itself may not be an incompatibility. An entire iframe might be monolithic - I haven't seen a specification that says one way or another.
Comment 2 Mihai Balan 2013-06-06 05:59:09 PDT
It actually seems that seamless iframes are *NOT* enabled in WebKit nightlies, so the initial comment only applies to normal iframes. And in this scenario I agree with you Alan that this is not a bug.

However, what should be behavior for seamless iframes? These do behave quite differently from normal iframes.
Comment 3 Mihnea Ovidenie 2014-04-01 05:45:45 PDT
Iframes should not be fragmented across regions, they should be treated like monolithic elements. Seamless iframes support was removed from WK.