W3C home > Mailing lists > Public > public-css-bugzilla@w3.org > November 2012

[Bug 19739] Investigate whether attr() needs "invalid at computed-value time" concept

From: <bugzilla@jessica.w3.org>
Date: Mon, 26 Nov 2012 19:30:03 +0000
To: public-css-bugzilla@w3.org
Message-ID: <bug-19739-5148-Y29f03AbGP@http.www.w3.org/Bugs/Public/>

fantasai <fantasai.bugs@inkedblade.net> changed:

           What    |Removed                     |Added
             Status|NEW                         |RESOLVED
         Resolution|---                         |INVALID

--- Comment #1 from fantasai <fantasai.bugs@inkedblade.net> ---
You don't know at parse time whether it's even a number, nevermind a positive
number. This is already handled; that's why attr() takes a fallback.

  # The optional <fallback> argument represents a fallback value, which is used
  # if the named attribute is missing, or its value cannot be parsed into the
  # given type or is invalid/out-of-range for the property. If it's absent, the
  # default value for the given <type-or-unit> (from the list below) is

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 26 November 2012 19:30:05 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:36:40 UTC