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

[Bug 16062] New: Behavior for out-of-range values needs to be defined

From: <bugzilla@jessica.w3.org>
Date: Tue, 21 Feb 2012 17:15:45 +0000
To: public-css-bugzilla@w3.org
Message-ID: <bug-16062-5148@http.www.w3.org/Bugs/Public/>

           Summary: Behavior for out-of-range values needs to be defined
           Product: CSS
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Transitions
        AssignedTo: dino@apple.com
        ReportedBy: ayg@aryeh.name
         QAContact: public-css-bugzilla@w3.org
                CC: cmarrin@apple.com, eoconnor@apple.com, smfr@me.com

This is currently issue 7 in the spec, but I'm filing a bug so I can get
notified when it's fixed:

Issue: Need to describe handling of out-of-range values that can result from
cubic-bezier(). Clamping values to the allowed range is probably the best

For example, if you have something like cubic-bezier(0.25, -2, 0.75, 1), on a
property like border-bottom-width that doesn't accept negative values, the
computed value should be clamped to 0px at points where it would be negative.

Gecko seems to do this correctly.  WebKit seems not to clamp anything, and
instead either allows the negative value, or has a large positive value like
134217660px, or falls back to a default value like "normal".  IE and Opera
clamp some properties correctly but not others.

(I hit this issue while porting Gecko's test_transitions_per_property.html. 
Non-Gecko browsers fail a lot of the clamping tests, but the spec isn't clear
that Gecko is right.)

Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 21 February 2012 17:15:50 UTC

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