Quote
WasiFH
KM76RC2 when unchecked, load this page perfectly.
KM76RC2 when checked, DOES NOT load this page perfectly, only headings.
also when Unchecked, google search behaves strangely; It prohibits "greasify" and "stylish" extensions to work on it. No problem on any other site as far as I checked.
When I checked what is the user agent with "Firefox compatible" checked and unchecked, the result as shown by google is:
with Firefox compat checked: Mozilla/5.0 (Windows NT 5.1; rv:38.0) Gecko/20100101 Firefox/38.0 K-Meleon/38.7.1esrpre
with ,, unchecked: Mozilla/5.0 (Windows NT 5.1; rv:38.0) Gecko/20100101 Firefox/38.0 K-Meleon/38.7.1esrpre
that is, the user agent string is the same? any suggestion?
Something wrong with your checking. Why ask Google to check the current UA? Google will only show you the string you send to google, not the string you send to paraz.
And google uses lots of other domains too, which could have a site-UA too.
Use instead the macro for checking, directly on the SITE you want to test:
menu Tools > Useragent > View current useragent
(this returns what javascript delivers for "navigator.userAgent", in useragents2018 macro, or Johns 7X macro, or another older one, but not the infamous multiswitcher addon hardcoded in the Pro Versions....
Oh! something dawns... you mentioned stylish and greasify?
At the moment not sure which one exactly, but have recently discovered, slightly shocked as usual, that a kmext extensions for something of that type contains the UA multiswitcher addon too - all secretly. That can mess all native UA switching attempts, but usually requires also the belonging macro to create the pref for activating it. That macro was NOT contained there. But who knows...
Anway, not sure if it affects you at all, but as a simple test, look into about:config if it contains that pref:
kmeleon.privacy.useragent.Count If existing, set it to ZERO to make sure the addon is disabled at least.
Then try again with a normal macro.