Changes:

uMatrix will now also report in the logger cookies which are externally deleted, i.e. cookies deleted through Firefox's UI or other extensions.

Closed as fixed:

Core

• Add a "settings" icon to the menu
• Adding visual cue indicating that a temp rule will be deleted if clicked by @WyohKnott
• "Delete blocked cookies" seems to be broken
• L10n for Dutch AMO description by @TonnesM
• 'Delete blocked cookies' function deletes multifox cookies which are still in use (and were never blocked)

Closed as fixed:

Chrome/OSX

• Cropped uMatrix popup in Chrome

Firefox

• uMatrix icon only available in one browser window when auto-restoring multi-window session
• uMatrix loses current site scope when opening links in new tabs

Changes:

Removal of the ability to spoof Origin header for the time being (which was a new behavior added to 0.9.3.0), as per issue #358.

Notes:

uMatrix has now been marked as "fully reviewed" on AMO.

So there is now a development version of uMatrix on AMO -- scroll to the bottom, expand Development Channel. You can install the latest dev build from there, my understanding is that the package is signed, hence it can be used in latest Firefox without Firefox warning that it is an unsigned extension. Also, you will be automatically updated when I release a new dev build.

New:

Cloud storage support code was imported from uBlock Origin: it works just the same way, so uBlock Origin's documentation regarding cloud storage support is relevant to uMatrix. Currently, only the My rules pane is hooked up to cloud storage.

Closed as fixed:

Firefox

• TypeError: LocationChangeListener is not a constructor
• Global uBlock installation on Ubuntu
  • Issue was affecting uMatrix as well: fix imported from uBlock Origin.
• Pass sameZoneAs to sandbox constructor to make GCs cheaper
• Referer leak
  • There is a related pending issue on Firefox.
• tabBrowser.tabs is undefined (vapi-background.js:1056)

Core

• Warn user about User Agent leaking
• Modernize CSP-injection code
• CIDR/Address range support

Closed as fixed:

Firefox

• Popup UI bug with latest release (regression)

New:

• Bengali translation by Leemon2010.

Changes:

Firefox compatibility is now version 24+ (previosuly was version 35+). I also added Pale Moon GUID to install.rdf.

Can import whitelist directives from NoScript export file. These will translate into * [hostname] script allow rules.

The popup UI has been slightly re-worked to remove the need for the right-most dropdown menu. There is now a title bar -- just like in uBlock -- to access the dashboard.

Closed as fixed:

Firefox

• Cookie not being counted
• Chrome and about url wrongly identified
  • This also fixes issue 262
• Import fix to uBlock issue 266
  • This was about re-factoring tab management code in uBlock to avoid performance issues when dealing with hundreds of tabs.
• All requests classified as behind-the-scene
• Support for pre-australis firefox 28.0 / palemoon

Pale Moon

• Altering menu filters causes UI flicker

Core

• Does not treat LAN hostnames (without suffix) as 1st-party domain
• Can Import NoScript's WhiteList Export File?

Closed as fixed:

Chromium:

• [Chrom*] connections not being blocked after reload (from uMatrix)
  • uMatrix now requires a new permission, "Change your privacy-related settings": for uMatrix to be able to disable the setting "Prefetch resources to load pages more quickly".
  • This will ensure no TCP connection is opened at all for blocked requests: It's for your own protection privacy-wise.
  • Prefetching is under Privacy for good reasons: using prefetching has has negative implications privacy-wise.
  • For pages with lots for blocked requests, this will actually remove overhead from page load (if you did not have the setting already disabled).
  • When uMatrix blocks a network request, the expectation is that it blocks completely the connection, hence the new permission is necessary for uMatrix to do truthfully what it says it does.

uMatrix's primary purpose is to block network connections, not just data transfer. Not blocking the connection while just blocking the data transfer would mean uMatrix is lying to users. So this permission will stay, and sorry for those who do not understand that it actually allows uMatrix to do its intended job more thoroughly. A blocker which does not thoroughly prevent connections is not a real blocker.

Privacy Badger also requires exactly the same permissions. uMatrix to also serve privacy-minded users first.

If prefetching had been disabled by default, this new permission would not be needed, but prefetching is unfortunately enabled by default, and under Privacy heading, which is itself hidden by default under "advanced settings".

Also, the benefits of prefetching are probably marginal, and in the context of a blocker, the benefits could be negative, since a lot of useless connections would be made, just to be discarded after the browser find out the requests won't be made anyway. So do not fall for the "lost of major performance boost" claim I read elsewhere, this is just an silly and baseless claim.

More about the required permissions.

Firefox:

• Logger tab selector titles not updating
• Fixed bad wrapper around setTimeout

Core

• Various fixes imported from uBlock: gorhill/uBlock#257, gorhill/uBlock#247.

Fix

• Spotted by my-password-is-password: Stray µb in code ported from uBlock