Skip to content
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

Remove the filter instead of suppressing it. #17

Closed
wants to merge 5 commits into from

Conversation

mookman288
Copy link

There are issues in Chrome that arise when the filter is set to 0px, as opposed to none. In addition to this pull request, this change should resolve those Chrome bugs.

adihimself and others added 5 commits February 18, 2015 15:08
Adding css-filter support for current Firefox
Update for the firefox support
* Fix IE filter detection by forcing IE to manual.
* Adjust elements to be returned to their previous locations after dismissal.
@mookman288
Copy link
Author

After some deeper use of 9123064, I discovered that (at least) IE10 through Edge represented that it could properly handle the filter declaration. This is not true. As a result, 55a5efe implements a small patch specific to IE, Trident (11,) and Edge. It also implements a solution to the foggy wrapper and relative DOM elements being added, and then the DOM not being returned to its previous state when foggy is disabled.

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

Successfully merging this pull request may close these issues.

None yet

2 participants