monster.ca: breakage

[prestr]

uBlock Origin blocks Monster.ca search results when a "Privacy" filter is enabled in Firefox.
If used in Edge it works fine but I'd rather not use Edge.

The Privacy filters I'm using are "EasyPrivacy" and "AdGuard Tracking Protection". Just disabling one or the other doesn't resolve the issue, it only resolves if both are disabled, so they much have something in common causing the issue in Firefox.

Basically in Firefox, when I do a job search it says "Sorry, no jobs found for that search." but in Edge I get the results shown to me.

[Yuki2718]

Please report in https://github.com/uBlockOrigin/uAssets/issues with required steps. The discussion is not to bypass issue-reporting.

[gorhill]

@prestr Reporting filter issues by using the chat icon in the popup panel is the best way to have filter issues looked at and fixed. Had you reported the issue through the chat tool, it probably would have been fixed within hours if not minutes.

Anyway, I can reproduce the issue in Firefox, but not in Chromium. The problematic filter appears to be EasyPrivacy's ||datadome.co^$3p, but for unknown reasons, only with Firefox.

---

More specifically, the site requires https://js.datadome.co/tags.js.

[Yuki2718]

@gorhill Are you logged in?

[gorhill]

No, I don't have an account on this site.

[Yuki2718]

Okay, I could reproduce only on Firefox as well.

[Yuki2718]

Fixed by easylist/easylist@a42ff35

[prestr]

@prestr Reporting filter issues by using the chat icon in the popup panel is the best way to have filter issues looked at and fixed. Had you reported the issue through the chat tool, it probably would have been fixed within hours if not minutes.

Anyway, I can reproduce the issue in Firefox, but not in Chromium. The problematic filter appears to be EasyPrivacy's ||datadome.co^$3p, but for unknown reasons, only with Firefox.

More specifically, the site requires https://js.datadome.co/tags.js.

@gorhill Sorry about that, I wasn't sure what to do. Going forward I'll make sure to do that.

@Yuki2718 Thanks for the fix!