Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
spec:cssom [2011/07/25 09:56] – add requests from WHATWG wiki annespec:cssom [2014/12/09 15:48] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +====== CSS Object Model ======
 +
 +Editor's draft: http://dev.w3.org/csswg/cssom/
 +
 +===== General To Do =====
   * CSSOM needs to define how Link:, <?xml-stylesheet?>, <link rel=stylesheet>, and <style> interact with the fetching algorithm, the event loop, and the parsers from HTML5.   * CSSOM needs to define how Link:, <?xml-stylesheet?>, <link rel=stylesheet>, and <style> interact with the fetching algorithm, the event loop, and the parsers from HTML5.
   * <?xml-stylesheet?> could do with a rewrite for integration with CSSOM; do 'load' and 'error' events fire on it?   * <?xml-stylesheet?> could do with a rewrite for integration with CSSOM; do 'load' and 'error' events fire on it?
Line 6: Line 11:
     * Add a pair of events that fire when an element is scrolled into and out of the view     * Add a pair of events that fire when an element is scrolled into and out of the view
  
 +===== Changes =====
 Transition scenarios the CSSOM has to cope with somehow: Transition scenarios the CSSOM has to cope with somehow:
  
Line 13: Line 18:
   * Property value changes into accepting multiple component values. E.g. the 'cursor' property now takes <x> and <y> in addition to <uri>. 'overflow' now takes two values rather than one.   * Property value changes into accepting multiple component values. E.g. the 'cursor' property now takes <x> and <y> in addition to <uri>. 'overflow' now takes two values rather than one.
   * Property component value changes. E.g. <uri> becomes <image>.   * Property component value changes. E.g. <uri> becomes <image>.
 +
 +===== Author Requests =====
 +==== new value based om ====
 +Per #css 2011-11-01: 
 +
 +Tab Atkins: "I know that there is demand for a new value based om that wouldn't be string-based. It's a popular author request that is currently done through libs like jQuery ... we know that there is a use-case in that area."
 +
 +David Baron: "Yes, i've seen author demand for this..."
 +
 +==== variants of computed style ====
 +Per #css 2011-11-01:
 +
 +David Baron: "... as well as for variants of computed style ..."
 +
 +==== set of matched rules for an element ====
 +Per #css 2011-11-01:
 +
 +David Baron: "... as well as some author demand for the set of matched rules for an element."
 
spec/cssom.txt · Last modified: 2014/12/09 15:48 by 127.0.0.1
Recent changes RSS feed Valid XHTML 1.0 Valid CSS Driven by DokuWiki