Automatically applying components based on crash stacktrace and information from OWNERS files.
If this is incorrect, please apply the Test-Predator-Wrong-Components label.
Maybe not a security issue, but it does seem like a correctness problem: there is now a discontinuity when the opacity overflows int. E.g. it's weird for this to not render: <rect width="100" height="100" fill="green" fill-opacity="2147483647"/>
Per spec [1], "Any values outside the range 0.0 (fully transparent) to 1.0 (fully opaque) will be clamped to this range. "
[1] https://www.w3.org/TR/SVG11/masking.html#OpacityProperty
Sure, in theory we could deal with it and feel free to fix it if it's easy. I just do not want to encourage us to add code to detect overflow if it slows down everything else.
ClusterFuzz testcase 5687112184365056 is verified as fixed, so closing issue as verified.
If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
Comment 1 by ClusterFuzz
, Apr 25 2018Labels: Test-Predator-Auto-Components