[Webkit-unassigned] [Bug 191939] New: *-opacity computed values should clamp between 0 and 1

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=191939

            Bug ID: 191939
           Summary: *-opacity computed values should clamp between 0 and 1
           Product: WebKit
           Version: Safari 12
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: CSS
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: ericwilligers at chromium.org

When the specified value is outside the range [0,1], Blink and Safari are currently not clamping the computed value of fill-opacity, flood-opacity, stop-opacity, stroke-opacity.

Edge and Firefox (and spec) are clamping the computed value to [0,1]

https://svgwg.org/svg2-draft/painting.html#FillOpacity
https://svgwg.org/svg2-draft/painting.html#StrokeOpacity
https://drafts.fxtf.org/filter-effects/#FloodOpacityProperty
Computed value: the specified value converted to a number, clamped to the range [0,1]

https://svgwg.org/svg2-draft/single-page.html#pservers-StopOpacityProperty
Any values outside the range 0.0 (fully transparent) to 1.0 (fully opaque) must be clamped to this range.

Blink bug: https://bugs.chromium.org/p/chromium/issues/detail?id=908058

All browsers are clamping the computed value of opacity and shape-image-threshold.
http://jsfiddle.net/ericwilligers/zmgy8735/

(Blink and Safari and Firefox have different behavior when animating: https://github.com/w3c/csswg-drafts/issues/3340 )

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20181124/57b6c24c/attachment-0001.html>