Explore the possibility of implementing the CSS Region interface.

Source/core/dom/NamedFlow.h

Index: Source/core/dom/NamedFlow.h
diff --git a/Source/core/dom/NamedFlow.h b/Source/core/dom/NamedFlow.h
index 75f2bd5765ac6fa530ed3699271b2fea1803cff8..102a7adc86620c705c63b81ccff44ddd96aa65e1 100644
--- a/Source/core/dom/NamedFlow.h
+++ b/Source/core/dom/NamedFlow.h
@@ -43,6 +43,7 @@ class NamedFlowCollection;
 class Node;
 class NodeList;
 class RenderNamedFlowThread;
+class RenderRegion;

[abarth-chromium, 2013/11/14 07:55:15]

These seem like bad dependencies.  The DOM shouldn't really have any direct
dependencies on the render tree, but that's a topic for another day.

[abucur, 2013/11/15 07:15:14]

I had in mind creating a DOM equivalent for region a while back but I didn't get
the chance. Maybe it's something we should do before exposing the Region
interface.

 class ExecutionContext;
 
 class NamedFlow : public RefCounted<NamedFlow>, public ScriptWrappable, public EventTargetWithInlineData {
@@ -55,8 +56,8 @@ public:
     const AtomicString& name() const;
     bool overset() const;
     int firstEmptyRegionIndex() const;
-    PassRefPtr<NodeList> getRegionsByContent(Node*);
-    PassRefPtr<NodeList> getRegions();
+    Vector<const RenderRegion*> getRegionsByContent(Node*);
+    Vector<const RenderRegion*> getRegions();
     PassRefPtr<NodeList> getContent();
 
     virtual const AtomicString& interfaceName() const OVERRIDE;