Skip to content

Core: Resolve csslint issues with the IE filter property #1939

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 15, 2020

Conversation

mgol
Copy link
Member

@mgol mgol commented Oct 15, 2020

IE filter property violates standard CSS parsing rules. Because of that, IE 8
added -ms-filter which accepts the same values but quoted:
https://web.archive.org/web/20101112132308/http://blogs.msdn.com/b/ie/archive/2008/09/08/microsoft-css-vendor-extensions.aspx
Both filter & -ms-filter serialize to the same filter property in
currentStyle.

This commit switches to that new property to resolve csslint issues.

IE filter property violates standard CSS parsing rules. Because of that, IE 8
added `-ms-filter` which accepts the same values but quoted:
https://web.archive.org/web/20101112132308/http://blogs.msdn.com/b/ie/archive/2008/09/08/microsoft-css-vendor-extensions.aspx
Both `filter` & `-ms-filter` serialize to the same `filter` property in
`currentStyle`.

This commit switches to that new property to resolve csslint issues.
@mgol mgol added this to the 1.13 milestone Oct 15, 2020
@mgol mgol requested review from fnagel and arschmitz October 15, 2020 07:48
@mgol mgol self-assigned this Oct 15, 2020
@mgol mgol merged commit b15e45a into jquery:master Oct 15, 2020
@mgol mgol deleted the ms-filter branch October 15, 2020 12:33
@dharitdesai
Copy link

@mgol @fnagel Hi Guys, do we have any release eta on this 1.13 milestone ? Only reason for asking this question is, that we are having issues with jQuery Migrate and 1.12.1 doesn't have the fixes which master has.
Thanks!

@mgol
Copy link
Member Author

mgol commented Jan 11, 2021

@dharitdesai There's no concrete release date, we need to fix all the tests & make a few other changes, then prepare a blog post & do a release. I cannot predict when exactly I'll have time to work on the remaining pieces or how long they'll take. That said, I feel we're closer to the end than to the beginning when I started submitting these patches (which was a bit more than a year ago).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants