requestIdleCallback not supported on ios

ryanbr commented 5 months ago

Prerequisites

[X] I verified that this is not a filter list issue. Report any issues with filter lists or broken website functionality in the uAssets issue tracker.
[X] This is NOT a YouTube, Facebook or Twitch report. These sites MUST be reported by clicking their respective links.
[X] This is not a support issue or a question. For support, questions, or help, visit /r/uBlockOrigin.
[X] I performed a cursory search of the issue tracker to avoid opening a duplicate issue.
[X] The issue is not present after disabling uBO in the browser.
[X] I checked the documentation to understand that the issue I am reporting is not normal behavior.

I tried to reproduce the issue when...

[X] uBO is the only extension.
[X] uBO uses default lists and settings.
[X] using a new, unmodified browser profile.

Description

Not a uBO specific issue, but reaching out;

Filters including remove-class, href-sanitizer,remove-attr are ignored due to the lack of requestIdleCallback . See: https://caniuse.com/requestidlecallback

A specific URL where the issue occurs.

No url attached

Steps to Reproduce

Any filters using remove-class.js, remove-attr.js, remove-class.js being ignored due to lack of requestIdleCallback (see: https://caniuse.com/requestidlecallback )
Just a general query if there is work around, not a specific uBO issue.

Expected behavior

If its possible to timeout or fallback if requestIdleCallback isn't used/detected/available.

Actual behavior

the 3 scriptlets are being ignored on ios currently.

uBO version

Brave IOS

Browser name and version

Brave IOS

Operating System and version

IOS

uBlock-user commented 5 months ago

Just a general query if there is work around

requestAnimationFrame can be used in its place.

uBlock-user commented 5 months ago

remove-attr and remove-class scriptlets are deprecated as per wiki, already, so you should start using procedural operator in its place - https://github.com/uBlockOrigin/uBlock-issues/wiki/Static-filter-syntax#subjectremove-attrarg-subjectremove-classarg

ryanbr commented 5 months ago

Yeah I know it'll be removed due to MV3, just seeing if there is something interium, upstream we could do. Even its just remove-class to be honest, thats the most widely used

uBlock-user commented 5 months ago

due to MV3

No, decision to deprecate has nothing to do with MV3, but due to emergence of :remove-attr() procedural operator.

ryanbr commented 5 months ago

Okay, stand corrected. was under the impression it was MV3

krystian3w commented 5 months ago

Looks duplicate of #3105

uBlockOrigin / uBlock-issues