@siria
Open that file from mozilla-esr38 on same server.
It includes 'media' and has 18 types in the list of permissions.

@siria
Deleted all permissions.default.* preferences before testing.
Plus sign is set for 'Image' of forum host in ExExceptions.
It doesn't block the image.

Example:

Quote
anonymous
Deleted all permissions.default.* preferences before testing.
Plus sign is set for 'Image' of forum host in ExExceptions.
It doesn't block the image.

Example:

So you have no default permission => show ALL images
And the exception for kmeleonbrowser means => do not show images FROM kmeleonbrowser on OTHER sites.
1+2 => correct as expected, kmeleonbrowser-domain shows the external image.

Mozilla just has this crazy inverted exception method, the urlbar has nothing to do with exceptions, only the SRC of the single elements, very gewöhnungsbedürftig.

That's why I find the default permissions all the more important, because those at least act how one expects it intuitively: If default for images is Site-only, the foreign image in your post vanishes. It will also vanish when you add an exception for the image-source-domain and set that one to Site-only.

That's also why I find it so sad that almost all default permissions do not show up anywhere in KM, since so many years. No GUI (unless counting about:permissions, which shows a few, but isn't in the menus either), and even hidden from about:config, because they aren't added yet to the default js-files (last time I looked)



Edited 3 time(s). Last edit at 04/04/2018 01:15AM by siria.

@siria
It only confirms that the 'site' value in ExExceptions is not valid in Gecko versions we tested.

People prefer tools that show what was blocked.

Quote
anonymous
It only confirms that the 'site' value in ExExceptions is not valid in Gecko versions we tested.

In the contrary, it confirms that this tiny editor addon behaves perfectly valid.
Because all it does is edit Mozillas native file permissions.sqlite, in exactly the way Mozilla has it defined. No more, no less: just adding domains to a list.

The content blocking itself is up to the engine only. If that behaves intentionally upside-down, due to decisions of the Mozilla/Firefox devs, it's not the fault of a file editor what the engine does with its own native domain list. It's the responsibility of Mozilla chiefs who want this behavior (user-friendly as they are, as always, haha.)

So, if anything, one could say that the Gecko engine isn't handling content blocking in a valid way. Which of course is a matter of opinions - in user view sure completely un-intuitive to put it mildly.
The only tiny thing that ExExceptions-addon could improve is the description text in the editor, to make users more aware of this upside-down policy of the engine devs.

Quote
anonymous
People prefer tools that show what was blocked.

Of course. But blame the culprits who want it otherwise, not innocents.

Quote
siria
That's also why I find it so sad that almost all default permissions do not show up anywhere in KM, since so many years.

To what browser version should they be added and where? Started with 'Tools/Privacy/Block Images Third Party'.

New version v16!

Added checks for KM74-Goanna (PaleMoon26.5 engine from 2016 for Win2000/??98SE??). It needs a new pref for gecko-compatibility, and fiddled a bit with descriptions again.



Edited 2 time(s). Last edit at 05/11/2018 01:18PM by siria.

New version v17!

Added some more prefs (for messageChannel, formfill, autoplay-variations, ABPrime adblocker, flashblock, toolbar info, etc.)

And it detects now the version of brandnew KM-Goanna 76.1