New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 664866 link

Starred by 2 users
Status: WontFix
Owner:
senorblanco@chromium.org
Closed: Dec 3
Cc:
█ sureshkumari@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug



Sign in to add a comment

empty value in filter:sepia() function differs from sepia(0) in CSS filter

Reported by asc...@mozilla.com, Nov 14 2016 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:51.0) Gecko/20100101 Firefox/51.0

Example URL:
https://jsfiddle.net/muavjbvs/7/

Steps to reproduce the problem:
Go to https://jsfiddle.net/muavjbvs/7/ 

What is the expected behavior?
According to spec[1], sepia() should be equal to sepia(0) and take no effect on target element.

[1] https://drafts.fxtf.org/filters/#funcdef-filter-sepia

What went wrong?
From the spec, sepia() means sepia(0), so it seems Blink doesn't follow the spec.

Ref on Mozilla MDN: https://developer.mozilla.org/en-US/docs/Web/CSS/filter#sepia()_2

Does it occur on multiple sites: N/A

Is it a problem with a plugin? No 

Did this work before? No 

Does this work in other browsers? Yes

Chrome version: 56.0.2918.0  Channel: canary
OS Version: OS X 10.12
Flash Version: Shockwave Flash 23.0 r0

Comment 1 by sureshkumari@chromium.org, Nov 14 2016

Cc: sureshkumari@chromium.org
Labels: -Pri-2 -Type-Compat M-56 hasbisect OS-Linux OS-Windows Pri-1 Type-Bug-Regression
Owner: jbroman@chromium.org
Status: Assigned (was: Unconfirmed)
Able to reproduce the issue on windows-7, Mac-10.11.6 and Linux Ubuntu-14.04 using chrome stable version 54.0.2840.99 and canary 56.0.2918.0

This is regression issue broken in M53.Please find the Manual bisect information as below

Narrow Bisect::
===============
Good :53.0.2759.0 --   (build revision 397936)
Bad:: 53.0.2760.0 --   (build revision 397956)

ChangeLog: 
================
https://chromium.googlesource.com/chromium/src/+log/53.0.2759.0..53.0.2760.0?pretty=fuller&n=10000

Possible suspect
==================
97c974e3f6f4c4a08a39032dd50b71a78e0351ca
	

Review URL: https://codereview.chromium.org/2038133002

jbroman@ could you please look into this issue if it is related to your change,else please help us in finding the appropriate owner for this issue.

Thanks.

Comment 2 by jbroman@chromium.org, Nov 14 2016

Components: Blink>CSS>Filters
Labels: -OS-Linux -OS-Windows -Pri-1 -hasbisect -M-56 -Type-Bug-Regression -OS-Mac OS-All Pri-2 Type-Bug
Owner: senorblanco@chromium.org
This is not restricted to the regression range shown. AFAICT, it predates us unprefixing the "filter" property and probably goes back well into the -webkit-filter days, so I'm going to remove the regression label.

This can probably just be a simple change to how we parse this CSS filter, assuming that we believe changing it to be web-compatible. Assigning to senorblanco@.

Comment 3 by suzyh@chromium.org, Apr 5 2017

Components: -Blink>CSS>Filters Blink>Compositing>Filters

Comment 4 by f...@opera.com, Dec 3

Status: WontFix (was: Assigned)
The link above (https://drafts.fxtf.org/filters/#funcdef-filter-sepia) now says:

> Default value when omitted is 1.
►

Sign in to add a comment