There was a problem with Waterfox/FirefoxESR. This has been fixed. Please write a new review if that is not what you meant.

Возникла проблема с Waterfox/FirefoxESR. Это было исправлено. Пожалуйста, напишите новый отзыв, если это не то, что вы имели в виду.

> The huge size of the drop-down menu.

This was added a couple of days ago to compensate for people with high-res monitors where the popup ended up being tiny. I guess it will become another option in settings…

UPDATE: Reverted to the previous behaviour, the new behaviour is now available as a disabled-by-default checkbox in the extension options.

> The huge size of the extension itself.

Since this is a recurring question I've added an FAQ entry to the extension's description. Please kindly refer to that for an answer.

> Access to browser activity during navigation.

Used to switch the extension's icon color and tooltip when you navigate from/to pages that have an override set. I could do without that permission but this way it is more reliable and easier to implement (note that extension will be able to see all sites you visit regardless of this permission, it's just more convenient to do it this way in this particular case).

Sorry for the inconvience caused by the recent changes. Version 1.3.4 should now stop the remaining breakage from occuring. If you still observe issues please send some examples of broken sites and what is wrong with them so that I may take a look. Thanks!

While I will not comment on the content of the websites you mentioned, I've fixed several issues on these sites with 1.3.4 that at least made Twitchy & Breitbart work. The Hill I could not test as their page is deploying a security policy that prevents access to all external resources (including Disqus) and hence is broken either way.

Thank you for your review! As mentioned before the 3MiB+ extra data shipped with the extension is used to generate sensible values for the other `navigator.*` browser identification values. Reading information like operating system, CPU type, device type, … from the User-Agent string is quite a hard thing to do as there are no standards at all – one just has to guess based on the COMMENT parts of the User-Agent string. Fortunately the BrowsCap project has maintained a list of matching patterns for figuring out this information since 1997 that is extremely reliable. As such, I will continue using it even if it means bloating the extension size by about 3MiB. The fact that it allows everything to just work out-of-the-box with just a single input value (the User-Agent string itself) in my opinion definitely outweighs that, by comparison small, price.

Sorry for the trouble! Should be fixed in v1.3.1 now!