W3C home > Mailing lists > Public > www-style@w3.org > April 2012

Re: [css3-regions] Suggestions for CSS OM Changes

From: Alan Stearns <stearns@adobe.com>
Date: Tue, 10 Apr 2012 12:40:46 -0700
To: "www-style@w3.org Style" <www-style@w3.org>
Message-ID: <CBA9DA74.AE61%stearns@adobe.com>
We have made significant changes to the "CSSOM view and CSS regions"
section based on this thread and other discussions. Some of the discussion
and decisions were captured on the Regions OM wiki page [1]. If you have
interest in or concerns about the object model for CSS Regions please take
a look at the updated section in the editor's draft [2]. One bit of
feedback still outstanding is whether to expose named flows on the
document as a collection or a map. I've emailed public-webapps for their
opinion [3].

The improved interfaces are listed below.

partial interface Document {
  readonly attribute NamedFlowCollection namedFlows;
  NamedFlow? getFlowByName(DOMString name);
}; 

interface NamedFlowCollection {
  readonly attribute unsigned long length;
  getter NamedFlow? item (unsigned long index);
};

interface NamedFlow implements EventTarget {
  readonly attribute DOMString name;
  readonly attribute boolean overset;
  sequence<Region> getRegions();
  readonly attribute integer firstEmptyRegionIndex;
  NodeList getContent();
  sequence<Region> getRegionsByContent(Node node);
};

interface Region {
  readonly attribute DOMString regionOverset;
  readonly attribute DOMString flowFrom;
  sequence<Range>? getRegionFlowRanges();
};               

[1] http://wiki.csswg.org/spec/css3-regions/css-om
[2] http://dev.w3.org/csswg/css3-regions/#cssom_view_and_css_regions
[3] http://lists.w3.org/Archives/Public/public-webapps/2012AprJun/0101.html
Received on Tuesday, 10 April 2012 19:41:18 GMT

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