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
Last revisionBoth sides next revision
spec:css3-values [2012/04/23 13:00] – whiteboard fantasaispec:css3-values [2012/04/23 14:23] – [attr()] fantasai
Line 6: Line 6:
 ===== WG Resolution Whiteboard ===== ===== WG Resolution Whiteboard =====
  
-== calc() returning <integer> ==+==== CSS2.1 Dependency ==== 
 + 
 +^Summary^Values and Units depends on CSS2.1 NUMBER token which is wrong| 
 +^DoC|http://dev.w3.org/csswg/css3-values/issues-lc-2012#issue-20| 
 +^Action|Resolve on 2.1 issue and either update CSS2.1 errata or update Values and Units| 
 + 
 +==== calc() ==== 
 + 
 +See [[http://lists.w3.org/Archives/Public/www-style/2012Apr/0531.html|Tab's summary email]]
  
 ^Summary^calc() should be able to return an <integer>| ^Summary^calc() should be able to return an <integer>|
 ^DoC|http://dev.w3.org/csswg/css3-values/issues-lc-2012#issue-10| ^DoC|http://dev.w3.org/csswg/css3-values/issues-lc-2012#issue-10|
 ^Action|WG needs to decide whether this is ok. We propose yes.| ^Action|WG needs to decide whether this is ok. We propose yes.|
- 
-== calc() accepting attr() == 
- 
 ^Summary^calc() should accept <length>/<number> instead of DIMENSION/NUMBER| ^Summary^calc() should accept <length>/<number> instead of DIMENSION/NUMBER|
 ^DoC|http://dev.w3.org/csswg/css3-values/issues-lc-2012#issue-11| ^DoC|http://dev.w3.org/csswg/css3-values/issues-lc-2012#issue-11|
-^Action|WG needs to decide whether to accept or reject.| 
 ^Note|Divisors still need to be restricted to DIMENSION/NUMBER to prevent divide-by-zero.| ^Note|Divisors still need to be restricted to DIMENSION/NUMBER to prevent divide-by-zero.|
 ^Note|At this point in time, the only effective change is allowing attr() inside calc().| ^Note|At this point in time, the only effective change is allowing attr() inside calc().|
 ^Note|This change can also be deferred to a later level; rejecting now doesn't mean we can't fix later.| ^Note|This change can also be deferred to a later level; rejecting now doesn't mean we can't fix later.|
 +^Action|WG needs to decide whether to accept or reject.|
  
-== Defer cycle() to Level 4 ==+==== cycle() ====
  
 ^Summary^Multiple design-level issues with cycle()| ^Summary^Multiple design-level issues with cycle()|
Line 28: Line 33:
 ^Action|WG needs to decide whether to defer, accept the limitations, or work on issues. We propose to defer.| ^Action|WG needs to decide whether to defer, accept the limitations, or work on issues. We propose to defer.|
  
-== Referencing URL specs ==+==== URLs ====
  
 ^Summary^What spec should we refer to to define URL validity/parsing?| ^Summary^What spec should we refer to to define URL validity/parsing?|
 ^DoC|http://dev.w3.org/csswg/css3-values/issues-lc-2012#issue-17| ^DoC|http://dev.w3.org/csswg/css3-values/issues-lc-2012#issue-17|
-^Action|WG needs to decide whether to reference abarth's spec, what's currently referenced, or something else.| +^Action|WG needs to advise on whether to reference abarth's spec, what's currently referenced, or something else.|
- +
-== Default URL returned by attr(foo url) == +
 ^Summary^Define an always-invalid url for the attr(foo url) default, like "about:invalid" or something| ^Summary^Define an always-invalid url for the attr(foo url) default, like "about:invalid" or something|
 ^DoC|http://dev.w3.org/csswg/css3-values/issues-lc-2012#issue-18| ^DoC|http://dev.w3.org/csswg/css3-values/issues-lc-2012#issue-18|
-^Action|WG needs to decide whether to spec this, and if so, what it is.|+^Action|WG needs to decide whether to define this, and if so, what it is.|
  
-== Restricting attr() fallbacks ==+==== attr() ====
  
-^Summary^ Restrict attr() so that declared type and fallback's type match when it'used as a component.|+^Summary^ Combinatorial validity checks when attr() used as component value with fallback of different type.|
 ^DoC|http://dev.w3.org/csswg/css3-values/issues-lc-2012#issue-21| ^DoC|http://dev.w3.org/csswg/css3-values/issues-lc-2012#issue-21|
-^Note|See ?? for explanation+^Note|Restricted attr() so that declared type and fallback type must match when it's used as a component value. See [[http://dev.w3.org/csswg/css3-values/#attr-notation|edits]] ("The attr() expression is only valid if"
-^Action|WG needs to decide whether to spec this, and if so, what it is.|+^Action|WG needs to approve this, or decide on something else|
  
-== Numeric Limits Revisited ==+==== Numeric Limits Revisited ====
  
 ^Summary^ Change component multiplier minimum from 30 to 20| ^Summary^ Change component multiplier minimum from 30 to 20|
 ^DoC|http://dev.w3.org/csswg/css3-values/issues-lc-2012#issue-22| ^DoC|http://dev.w3.org/csswg/css3-values/issues-lc-2012#issue-22|
 ^Action|Needs WG resolution to accept.| ^Action|Needs WG resolution to accept.|
- 
 ^Summary^ Define minimum precision as 3 decimal points| ^Summary^ Define minimum precision as 3 decimal points|
 ^DoC|http://dev.w3.org/csswg/css3-values/issues-lc-2012#issue-25| ^DoC|http://dev.w3.org/csswg/css3-values/issues-lc-2012#issue-25|
 ^Action|Needs WG resolution to accept.| ^Action|Needs WG resolution to accept.|
 +
 +==== Value Syntax Notation ====
 +
 +^Summary^ Add order-sensitive component combinator|
 +^DoC|http://dev.w3.org/csswg/css3-values/issues-lc-2012#issue-27|
 +^Action|Decide whether to accept, reject, or defer. This is editorial.|
  
 
spec/css3-values.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