Closed ghost closed 6 years ago
The global languages can be set on about:preferences
.
Match patterns are directly passed to the browser's API: wildcard can only be the beginning and followed by a dot, so *.*
won't work.
I didn't consider the scenario when rules are overlapping. Did you try change the order of rules?
My point of using this extension is to escape browser sniffing with the NavigatorLanguage.language API This API is overriding the header and thus I hope that with the other browser extension the API can be stopped and the header becoming the sole source of language information.
Hence I was looking for a global setting and then to cascade localized settings whenever needed.
Yes, tested the order of rules but *
takes always precedence, whether top or bottom of the order. I had hoped for a logic of weighing the specifics of the domain declaration, e.g. *.uk
is more specific than *
and thus *.uk
takes precedence over *
I see. It's possible but requires change the extension to intercept all requests and implement rule matching by ourself. I will look into it later.
Just a quick thank you for the instant patch! Love it and rated it already 5* at AMO
Thank you for this extension!
I was trying to set a global approach with the wildcard but either way I tried it did not work.
1 host
*
(global) / a-l FR (as an example) 2 host*.uk
(localized) / a-l GBIn this scenario (1) takes precedence over everything and (2) is not applied. Alternatively tried
1 host
*.*
(global) / a-l FR 2 host*.uk
(localized) / a-l GBIn this scenario (1) is not applied at any domain/host but only (2)