Open
Bug 1514375
Opened 6 years ago
Updated 2 years ago
[CSS Filter effects] Firefox only web platform test failures
Categories
(Core :: Layout, defect, P3)
Core
Layout
Tracking
()
NEW
People
(Reporter: automatedtester, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: parity-chrome, parity-safari)
The following web platform tests are failing only in firefox as documented in https://foolip.github.io/ad-hoc-wpt-results-analysis/firefox-lone-failures.html
/css/filter-effects/filter-external-001-test.html
/css/filter-effects/filtered-html-is-not-container.html
/css/filter-effects/parsing/filter-computed.html
/css/filter-effects/parsing/filter-parsing-valid.html
/css/filter-effects/svgfeblendelement-mode-001.html
Comment 1•6 years ago
|
||
(In reply to David Burns :automatedtester from comment #0)
> /css/filter-effects/filter-external-001-test.html
This is only off-by-one in the color value. The filter produces rgb(0, 119, 1) in Firefox, and the reference uses rgb(0, 120, 1).
All the other test failures are true failures:
> /css/filter-effects/filtered-html-is-not-container.html
This is bug 1423746.
> /css/filter-effects/parsing/filter-computed.html
> /css/filter-effects/parsing/filter-parsing-valid.html
CSS filter functions blur(), brightness(), contrast(), grayscale(), hue-rotate(), invert(), opacity(), saturate() and sepia() are treated as invalid when used without arguments.
> /css/filter-effects/svgfeblendelement-mode-001.html
1. feBlendElement.setAttribute("mode", "not-a-valid-value") causes feBlendElement.mode.baseVal to change from 1 to 0 instead of staying at 1.
2. Setting feBlendElement.mode.baseVal to 1 doesn't change its mode attribute to "normal" (?)
Updated•6 years ago
|
Priority: -- → P3
Comment 2•6 years ago
|
||
(In reply to Markus Stange [:mstange] from comment #1)
/css/filter-effects/parsing/filter-computed.html
/css/filter-effects/parsing/filter-parsing-valid.htmlCSS filter functions blur(), brightness(), contrast(), grayscale(),
hue-rotate(), invert(), opacity(), saturate() and sepia() are treated as
invalid when used without arguments.
This may be the easiest thing to be fixed. It's acceptable if we don't use argument in this function (based on the current draft spec). I can file another bug to fix them.
Reporter | ||
Updated•6 years ago
|
Keywords: parity-chrome,
parity-safari
Reporter | ||
Updated•6 years ago
|
No longer blocks: wpt.fyi-firefox-fails
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•