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

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

From: <bugzilla@jessica.w3.org>
Date: Tue, 21 Feb 2012 18:28:50 +0000
To: public-css-bugzilla@w3.org
Message-Id: <E1RzuSI-0000LC-Ux@jessica.w3.org>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16062

--- Comment #2 from Aryeh Gregor <ayg@aryeh.name> 2012-02-21 18:28:50 UTC ---
Nope.  The current spec explicitly allows the y-coordinates of cubic-bezier()
(i.e., second and fourth arguments) to be out of the range [0, 1].  This allows
property values to "bounce" beyond the start/end values.  Try this:

data:text/html,<!doctype html>
<div style="text-indent:0px;
-ms-transition:2s cubic-bezier(0.25, -0.5, 0.75, 1);
-moz-transition:2s cubic-bezier(0.25, -0.5, 0.75, 1);
-webkit-transition:2s cubic-bezier(0.25, -0.5, 0.75, 1);
-o-transition:2s cubic-bezier(0.25, -0.5, 0.75, 1);">
Some text</div>
<script>
setTimeout(function(){document.querySelector("div").style.textIndent =
"100px";}, 1000);
</script>

This causes the indentation to become briefly negative before it rises to
100px.  This is good, and we want to allow it.  But for properties where
negative values are prohibited, it has to be clamped.  I'm seeing
getComputedStyle().fontSize == "-67px" in WebKit right now, for instance.  This
also needs to apply to the upper end, for properties that are clamped from
above (like opacity).

-- 
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 18:28:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 21 February 2012 18:28:57 GMT