This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
spec:cssom [2010/08/17 03:32] – two spaces doh not anne | spec:cssom [2014/12/09 15:48] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== CSS Object Model ====== | ||
+ | |||
+ | Editor' | ||
+ | |||
+ | ===== General To Do ===== | ||
+ | * CSSOM needs to define how Link:, <? | ||
+ | * <? | ||
+ | * CSSOM should have a mechanism for taking elements full-screen | ||
+ | * it has been proposed that CSSOM have a mechanism for keeping track of when expensive-to-compute areas of the document (e.g. a canvas) are actually being rendered. | ||
+ | * Add a pair of events that fire when an element is hidden and unhidden | ||
+ | * 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 5: | Line 18: | ||
* Property value changes into accepting multiple component values. E.g. the ' | * Property value changes into accepting multiple component values. E.g. the ' | ||
* Property component value changes. E.g. <uri> becomes < | * Property component value changes. E.g. <uri> becomes < | ||
+ | |||
+ | ===== 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' | ||
+ | |||
+ | 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." |