-
Notifications
You must be signed in to change notification settings - Fork 20.6k
Remove jQuery.fx.interval #4018
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
Comments
What caniuse.com entry? https://caniuse.com/#feat=pagevisibility shows full IE 10+ support, the MDN entry also claims IE 10 supports it. It seems that support is identical to |
When I go into the console debugger in IE11 I see |
You're right. It seems both MDN & Can I Use are out of date here. |
The problem seems to be that this is "Page Visibility 2" which had a first draft in March 2016. The previous "Page Visibility" is what IE10/11 use. The references don't seem to distinguish the two. The MDN page mentions |
Yeah, I think I might have considered
If we do consider it, we should be really careful and like do some extensive testing I would suggest. I.e. just to see our test suite pass is not enough I think. Since I remember our experience with https://bugs.jquery.com/ticket/10067, don't wanna see that again, haha |
Ha, I do see |
Oh duh, I got the property wrong! Nevermind. |
Simplified this ticket and just made it about privatizing our use of |
I missed it but we already removed |
Migrate has to make some shaky assumptions about the implementation of core's animations in order to warn about
jQuery.fx.interval
. It would be simpler if we used a private value for the interval value (basically just hard-code the default13
) so that any use ofjQuery.fx.interval
could be indentified as deprecated. There is a slight risk that someone might be changing that value but it seems unlikely since we are already ignoring it except for two rare-ish cases: 1) IE9 always, 2) browsers when the document is hidden.In addition, per some discussion on jquery/jquery-migrate#298 we may want to change from
document.hidden
todocument.visibilityState
since the standard has changed. From looking at caniuse.com it seems like IE10/IE11 supportrAF
anddocument.hidden
but notdocument.visibilityState
so I am not sure that is possible until we drop their support.The text was updated successfully, but these errors were encountered: