How can I enable API for a domain only.

[Iz-zzzzz]

I want to enable Navigator API for google.* only but if I don't check main API checkbox

the site specific value will no work even it's checked.

So I try some workaround like this

This workaround seems work. However, there is a problem when I want to add new site specific value. (in this case is example3.com)

I want to be protect on example3.com site but it looks like example3.com site matches * rule(disable API) before example3.com rule(enable API).

To fix this, I have to remove * then add it again EVERY TIME to make sure * rule must be used in the last order.

Is there a method or approach that might achieve this task more effectively than the one I've proposed? Thank you 😊

I think it might be more convenient if this rule works even main checkbox is uncheck.

[kkapsner]

Why do you only want to enable it for google.*?

[Iz-zzzzz]

When using the original value of the user agent in Firefox mobile, Google displays a very old version of the Google Search UI, which some features do not function properly and even loss some features.

without Navigator API (Firefox Mobile)

with Navigator API spoof as Chrome Android 124.0.0.0

[spodermenpls]

Ah, the functionality usually brought by the "Google Search Fixer" extension of Firefox devs Rob Wu and Thomas Wisniewski. Makes sense to do it with a custom setting in CanvasBlocker, without having to install an extra extension.

[spodermenpls]

I had the same question 5 years ago (for twitter.com: #321 (comment)), you have to use a negative site-specific setting (RegEx), something like ^(?!.*google).*$ , while removing the checkmark behind it.

[Iz-zzzzz]

This approach appears to be the most promising. I will follow this approach. Thank you 😊

Edited 2:

Grey site specific value (which its value was set by other APIs not the current one) doesn't spoof the specific site if it also match other rules like ^(?!.*google).*$

Edited:

I just notice that the grey site specific value (which its value was set by other APIs not the current one)
Attached image
will follow the main API checkbox state, so I have to uncheck it every time when adding new site specific value to other APIs.

[spodermenpls]

@Iz-zzzzz Is the Navigator API-spoofing actually active though for the URLs with grayed-out checkmarks, when the aformentioned negative RegEx is being added? But even if, maybe excluding the Navigator API from the "show the URL on all site-specific API settings once it is added somewhere" feature is a sensible idea (also vice versa, not showing URLs added to the Navigator API site-specific values elsewhere), since it is the furthest removed from "ordinary" API protection, and has usually only very specific (sensible) use cases that don't correlate with e.g. Canvas or DOMRect spoofing. @kkapsner

[Iz-zzzzz]

Is the Navigator API-spoofing actually active though for the URLs with grayed-out checkmarks, when the aformentioned negative RegEx is being added?

No, I just tested again. Perhaps I made a mistake in my previous test. I apologize for bothering you.

[spodermenpls]

@Iz-zzzzz How would this bother me, that was a totally legitimate question to ask. 😄 I haven't used the Navigator API protection in years (ever since my use case didn't work on Twitter anymore), therefore having very little experience with it myself (or RegEx, for that matter), I was just going off of distant memories on that one (took me a while to find that old thread as well). This is a good occasion/nudge to isolate the Navigator API from the other site-specific settings elsewhere to avoid visual confusion, so if anything, you are helping make CanvasBlocker better. 😀