Bug 143601 – Unprefixed transition: filter is accepted by Safari but does not work

• Status: RESOLVED
• Resolution: CONFIGURATION CHANGED
• Component: CSS

[Tom]

Example URL:
http://jsbin.com/zabusuhese/1/edit?html,css,output

Steps to reproduce the problem:
1. create a div, apply the CSS: filter: brightness(100%); transition:filter;
2. set the hover state to filter:brightness(120%);
3. follow the above steps, replacing filter with -webkit-filter

What is the expected behavior?
both divs behave the same

What went wrong?
the unprefixed transition: filter did not work

Does it occur on multiple sites: N/A

Is it a problem with a plugin? N/A 

Did this work before? N/A 

Does this work in other browsers? works in Firefox

[Simon Fraser (smfr)]

Dean, with this:

transition: -webkit-filter 0.3s;
transition: filter 0.3s;

should we be smart enough to ignore the second rule with the invalid transitioned property name?

[Tom]

It seems the solution is to use a comma separated list of transitions, instead of expecting the supported transition property to overwrite successfully:

https://code.google.com/p/chromium/issues/detail?id=475865

[Brent Fulgham]

Safari and Chrome agree on rendering for this test case. I don't believe there is any remaining compatibility issue.