-
Notifications
You must be signed in to change notification settings - Fork 83
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
requestAnimationFrame-if and prefixed parameter #981
Comments
I should change I can't find instance of |
There's one filter in uBO Annoyances list for |
@gorhill so are you going to revise it soon? or not soon? |
For sure for next release, but I need to think of how to make the change while keeping compatibility for the currently used version since it turns out it's being used after all. |
Related issue: - uBlockOrigin/uBlock-issues#981 To be consistent with no-setTimeout-if.js. requestAnimationFrame-if.js is deprecated and must no longer be used, it will be removed in the near future when it's no longer in use in default filter lists. no-requestAnimationFrame-if.js is aliased to norafif.js.
Related issue: - uBlockOrigin/uBlock-issues#981 To be consistent with no-setTimeout-if.js. requestAnimationFrame-if.js is deprecated and must no longer be used, it will be removed in the near future when it's no longer in use in default filter lists. no-requestAnimationFrame-if.js is aliased to norafif.js.
logic of requestAnimationFrame-if and no-setInterval-if are different —
prefix
!
is needed for mathing in first case and NOT matching in secondfor what reason it has been done? and is there any chance to make a behaviour of the prefix
!
equal for raf-if.js, nosiif.js/nostif.js?(as for me, it's better to use
!
for not matching)The text was updated successfully, but these errors were encountered: