Softpedia >Windows >Internet >Internet Applications Addons >Chrome Extensions >uMatrix for Chrome >  Changelog

uMatrix for Chrome Changelog

What's new in uMatrix for Chrome 1.4.4

Jul 20, 2021
  • Fixes:
  • Fix exception thrown when a stock asset is removed
  • Remove obsolete assets

New in uMatrix for Chrome 1.4.3 Beta 0 (Jul 19, 2021)

  • New:
  • Ability to reveal the canonical names of aliased hostnames. This is a per-scope setting.
  • The corresponding switch-based rule is:
  • cname-reveal: [scope] true
  • By default, the rule cname-reveal: * true is created in new installations of uMatrix. For existing installations, you will have to add it yourself if you want canonical names to be reported in the matrix everywhere by default. This new feature is supported only in Firefox.

New in uMatrix for Chrome 1.4.1 Beta 6 (Feb 25, 2020)

  • New:
  • Ability to reveal the canonical names of aliased hostnames.
  • The corresponding switch-based rule is:
  • cname-reveal: [scope] true
  • By default, the rule cname-reveal: * true is created in new installations of uMatrix. For existing installations, you will have to add it yourself if you want canonical names to be reported in the matrix everywhere by default. This new feature is supported only in Firefox.

New in uMatrix for Chrome 1.4.1 Beta 5 (Jan 13, 2020)

  • New:
  • Ability to reveal the canonical names of aliased hostnames. This is a per-scope setting:
  • The corresponding switch-based rule is:
  • cname-reveal: [scope] true
  • By default, the rule cname-reveal: * true is created in new installations of uMatrix. For existing installations, you will have to add it yourself if you want canonical names to be reported in the matrix everywhere by default. This new feature is supported only in Firefox.

New in uMatrix for Chrome 1.4.0 (Sep 5, 2019)

  • A new raw setting has been added: suspendTabsUntilReady. The purpose is exactly the same as the same setting in uBlock Origin, so you can refer to uBO's documentation. That setting is taken into account only with Chromium-based browsers, as Firefox is properly equipped to deal with network requests fired before uMatrix is ready.
  • Closed as fixed:
  • Cookies missing on very first request if website has service worker with fetch event handler
  • Incorrect display of hostnames with numbers in the logger
  • Custom recipe does not appear
  • Requests bypass uMatrix on Firefox start

New in uMatrix for Chrome 1.3.17 RC4 (May 29, 2019)

  • Chromium 72+:
  • Cookies leaking temporarily
  • Core:
  • Cookies missing on very first request if website has service worker with fetch event handler
  • Incorrect display of hostnames with numbers in the logger
  • Custom recipe does not appear
  • Requests bypass uMatrix on Firefox start

New in uMatrix for Chrome 1.3.17 RC3 (May 27, 2019)

  • Closed as fixed:
  • Chromium 72+:
  • Cookies leaking temporarily
  • Core:
  • Cookies missing on very first request if website has service worker with fetch event handler
  • Incorrect display of hostnames with numbers in the logger
  • Custom recipe does not appear
  • Requests bypass uMatrix on Firefox start

New in uMatrix for Chrome 1.3.17 RC2 (May 22, 2019)

  • Closed as fixed:
  • Chromium 72+:
  • Cookies leaking temporarily
  • Core:
  • Cookies missing on very first request if website has service worker with fetch event handler
  • Incorrect display of hostnames with numbers in the logger
  • Custom recipe does not appear
  • Requests bypass uMatrix on Firefox start
  • Pull requests:
  • Show placeholder for blocked frame elements by xofe
  • More unused code cleaning by rhendric
  • Cleaning by rhendric
  • Minor fixes by xofe

New in uMatrix for Chrome 1.3.17 RC 1 (May 21, 2019)

  • Changes:
  • A new raw setting has been added: suspendTabsUntilReady. The purpose is exactly the same as the same setting in uBlock Origin, so you can refer to uBO's documentation. That setting is taken into account only with Chromium-based browsers, as Firefox is properly equipped to deal with network requests fired before uMatrix is ready.
  • Closed as fixed:
  • Chromium 72+
  • Cookies leaking temporarily
  • Core:
  • Cookies missing on very first request if website has service worker with fetch event handler
  • Incorrect display of hostnames with numbers in the logger
  • Custom recipe does not appear
  • Requests bypass uMatrix on Firefox start

New in uMatrix for Chrome 1.3.17 RC 0 (Apr 24, 2019)

  • Changes:
  • A new raw setting has been added: suspendTabsUntilReady. The purpose is exactly the same as the same setting in uBlock Origin, so you can refer to uBO's documentation. That setting is taken into account only with Chromium-based browsers, as Firefox is properly equipped to deal with network requests fired before uMatrix is ready.
  • Closed as fixed:
  • Chromium 72+
  • Cookies leaking temporarily
  • Core:
  • Incorrect display of hostnames with numbers in the logger
  • Custom recipe does not appear
  • Requests bypass uMatrix on Firefox start

New in uMatrix for Chrome 1.3.17 Beta 2 (Apr 9, 2019)

  • Changes:
  • A new raw setting has been added: suspendTabsUntilReady. The purpose is exactly the same as the same setting in uBlock Origin, so you can refer to uBO's documentation. That setting is taken into account only with Chromium-based browsers, as Firefox is properly equipped to deal with network requests fired before uMatrix is ready.
  • Closed as fixed:
  • Chromium 72+
  • Cookies leaking temporarily
  • Core:
  • Custom recipe does not appear
  • Requests bypass uMatrix on Firefox start

New in uMatrix for Chrome 1.3.17 Beta 1 (Jan 3, 2019)

  • Chromium 72+:
  • Cookies leaking temporarily
  • Core:
  • Custom recipe does not appear
  • Requests bypass uMatrix on Firefox start
  • Pull request by @rhendric: Cleaning
  • Pull request by @xofe: Minor fixes

New in uMatrix for Chrome 1.3.15 RC2 (Dec 26, 2018)

  • Changes:
  • Icons:
  • Little by little I will be migrating from font-based icons toward SVG-based icons. See uBlockOrigin/uMatrix-issues#68
  • Logger
  • The popup panel is now tab selector-bound (rather than logger entry-bound), i.e. it is associated with the tab currently selected.
  • There is a new UI to allow setting rules on a per logger entry basis (click the 3rd column): it is similar in look and use to the matrix UI, but it is minimalist: rules which are relevant only for the current entry in the logger are shown.
  • Two columns have been added:
  • a column to provide the scope in which network requests are made;
  • a column to provide visual hint for the third-partiness of requests.
  • The visual to represent tabless network requests has been modified. Tabless network requests will now be represented with "curtains" in the 3rd column.
  • Closed as fixed:
  • Firefox
  • "Corrupted Content Error"
  • Logger not working in sidebar
  • When pasting multiple lines into the rules editor they are joined together in a single line
  • Is there a way to disable javascript in local file:// for firefox?
  • The idea for the fix has been borrowed from NoScript: use a DOM-based <meta http-equiv=...> tag to inject CSP directives. This will apply only to documents fetched using file: scheme.
  • The fix requires the API browser.contentScripts, which only Firefox supports.
  • Core
  • Migrate icons to FontAwesome svg files (from the font file)
  • Race condition potentially causing auto-update to be disregarded at launch time
  • Behind-the-scene broken at gmail
  • Images, videos opened directly in a tab are bypassing respective block rules
  • Multiple Redirects Fail
  • Some entries are only briefly shown in uMatrix

New in uMatrix for Chrome 1.3.15 RC0 (Oct 8, 2018)

  • Changes:
  • Icons:
  • Little by little I will be migrating from font-based icons toward SVG-based icons. See uBlockOrigin/uMatrix-issues#68. Some of the icons in the latest FontAwesome package -- which now ships with SVG version of all icons -- have been redesigned by the author, so expect some of the icons may look different.
  • Logger:
  • The popup panel is now tab selector-bound (rather than logger entry-bound), i.e. it is associated with the tab currently selected.
  • There is a new UI to allow setting rules on a per logger entry basis (click the 3rd column): it is similar in look and use to the matrix UI, but it is minimalist: rules which are relevant only for the current entry in the logger are shown.
  • Two columns have been added:
  • a column to provide the scope in which network requests are made;
  • a column to provide visual hint for the third-partiness of requests.

New in uMatrix for Chrome 1.3.15 Beta 7 (Oct 1, 2018)

  • Logger:
  • The popup panel is now tab selector-bound (rather than logger entry-bound), i.e. it is associated with the tab currently selected.
  • There is a new UI to allow setting rules on a per logger entry basis (click the 3rd column): it is similar in look and use to the matrix UI, but it is minimalist: rules which are relevant only for the current entry in the logger are shown.
  • Two columns have been added:
  • A column to provide the scope in which network requests are made;
  • A column to provide visual hint for the third-partiness of requests.
  • Core:
  • Behind-the-scene broken at gmail
  • Race condition potentially causing auto-update to be disregarded at launch time
  • Multiple Redirects Fail
  • Some entries are only briefly shown in uMatrix

New in uMatrix for Chrome 1.3.15 Beta 4 (Sep 26, 2018)

  • Core:
  • Race condition potentially causing auto-update to be disregarded at launch time
  • Multiple Redirects Fail

New in uMatrix for Chrome 1.3.15 Beta 3 (Sep 26, 2018)

  • Race condition potentially causing auto-update to be disregarded at launch time
  • Multiple Redirects Fail

New in uMatrix for Chrome 1.3.15 Beta 2 (Sep 17, 2018)

  • Multiple Redirects Fail

New in uMatrix for Chrome 1.3.15 Beta (Sep 14, 2018)

  • Multiple Redirects Fail

New in uMatrix for Chrome 1.3.14 (Aug 27, 2018)

  • Core:
  • My rules tab hangs with cloud storage support

New in uMatrix for Chrome 1.3.13 Beta 1 (Aug 26, 2018)

  • Closed as fixed:
  • Firefox:
  • uMatrix uses the false domain 1.wyciwyg-scheme instead of the real one
  • uMatrix reports what the Firefox API reports to it: Firefox should be fixed to report seamlessly wyciwyg:// URLs so as to avoid forcing extensions to deal with such URLs, which should be strictly for internal consumption by Firefox.
  • Until the issue is fixed in Firefox (if ever), a workaround in uMatrix has been implemented in order to deal with such URLs in a seamless manner in its UI.
  • Those URLs still cause quirks however: for example forcing a reload won't work. This is not a uMatrix issue, even Firefox's reload button does not work in such case. The workaround is to click the address bar as if to edit the current URL and press Enter to force a reload.
  • Core:
  • My rules tab hangs with cloud storage support

New in uMatrix for Chrome 1.3.11 RC 1 (Jul 6, 2018)

  • Closed as fixed:
  • Placeholder iframe not shown on particular site using Firefox

New in uMatrix for Chrome 1.3.11 RC0 (Jul 6, 2018)

  • Closed as fixed:
  • Placeholder iframe not shown on particular site using Firefox

New in uMatrix for Chrome 1.3.11 Beta 0 (Jun 18, 2018)

  • New revision for dev build

New in uMatrix for Chrome 1.3.9 Beta 1 (May 15, 2018)

  • Fixed:
  • Custom recipes don't show up when visiting corresponding host

New in uMatrix for Chrome 1.3.8 (Apr 25, 2018)

  • Ruleset pane size miscalculated
  • Placeholder in logger "Network error" message is not replaced
  • Shared Workers

New in uMatrix for Chrome 1.3.7 RC (Apr 20, 2018)

  • Ruleset pane size miscalculated
  • Placeholder in logger "Network error" message is not replaced
  • Shared Workers

New in uMatrix for Chrome 1.3.7 Beta 4 (Apr 15, 2018)

  • Closed as fixed:
  • Ruleset pane size miscalculated
  • Placeholder in logger "Network error" message is not replaced
  • Shared Workers

New in uMatrix for Chrome 1.3.7 Beta 3 (Apr 14, 2018)

  • Closed as fixed:
  • Ruleset pane size miscalculated

New in uMatrix for Chrome 1.3.7 Beta 1 (Apr 10, 2018)

  • Closed as fixed:
  • Ruleset pane size miscalculated

New in uMatrix for Chrome 1.3.6 (Apr 10, 2018)

  • Improved the visuals and behavior of Recipes icon (the puzzle icon) in popup panel.

New in uMatrix for Chrome 1.3.5 Beta 3 (Mar 27, 2018)

  • CodeMirror's MergeView has been integrated into the "My rules" pane, this should make it easier to manage your ruleset.

New in uMatrix for Chrome 1.3.5 Beta 2 (Mar 25, 2018)

  • Changes:
  • CodeMirror's MergeView has been integrated into the "My rules" pane, this should make it easier to manage your ruleset.
  • Closed as fixed:
  • CSP error notification -> Conflicting with uBlock Origin?

New in uMatrix for Chrome 1.3.3 Beta 9 (Mar 6, 2018)

  • New:
  • A new button ("puzzle" piece icon) is available in the popup panel: uMatrix will offer you the ability to import community-contributed ruleset recipes which are relevant to the current page (see #30). Hopefully there will be many contributions to populate ruleset recipes ready to be used to unbreak sites.
  • A tooltip has been added to the global scope selector (*) in the popup panel.
  • A new setting has been added in the Settings pane: "Disable tooltips".
  • Changes:
  • The setting "Show the number of distinct requests on the icon" has been changed to "Show the number of blocked resources on the icon": the number of blocked resources is much more useful than the number of distinct resources. This will make it clear now that uMatrix is still blocking stuff even after you think you had configured it to no longer block stuff (example: #938).
  • The icon badge is back to being enabled by default with new installations of uMatrix.
  • Closed as fixed:
  • Report more accurately that resources are being blocked following page load
  • [Performance] Implement ability to snapshot memory to improve load times
  • When first installing uMatrix, the setting "Auto-update hosts files" is disabled by default

New in uMatrix for Chrome 1.3.2 / 1.3.3 Beta 8 (Feb 12, 2018)

  • New:
  • A new button ("puzzle" piece icon) is available in the popup panel: uMatrix will offer you the ability to import community-contributed ruleset recipes which are relevant to the current page (see #30). Hopefully there will be many contributions to populate ruleset recipes ready to be used to unbreak sites.
  • A tooltip has been added to the global scope selector (*) in the popup panel.
  • A new setting has been added in the Settings pane: "Disable tooltips".
  • Changes:
  • The setting "Show the number of distinct requests on the icon" has been changed to "Show the number of blocked resources on the icon": the number of blocked resources is much more useful than the number of distinct resources. This will make it clear now that uMatrix is still blocking stuff even after you think you had configured it to no longer block stuff (example: #938).
  • The icon badge is back to being enabled by default with new installations of uMatrix.
  • Closed as fixed:
  • Report more accurately that resources are being blocked following page load
  • [Performance] Implement ability to snapshot memory to improve load times
  • When first installing uMatrix, the setting "Auto-update hosts files" is disabled by default

New in uMatrix for Chrome 1.3.3 Beta 4 (Feb 4, 2018)

  • import translation work from https://crowdin.com/project/umatrix

New in uMatrix for Chrome 1.3.3 Beta 3 (Feb 2, 2018)

  • new revision for dev build

New in uMatrix for Chrome 1.3.3 Beta 2 (Jan 31, 2018)

  • Import translation work from https://crowdin.com/project/umatrix

New in uMatrix for Chrome 1.3.2 (Jan 23, 2018)

  • Closed as fixed:
  • uMatrix does not report inline styles

New in uMatrix for Chrome 1.3.0 (Jan 22, 2018)

  • noscript tags improperly rendered in XML-based HTML documents

New in uMatrix for Chrome 1.2.1 RC 3 (Jan 21, 2018)

  • Fixed:Fix noscript tags improperly rendered in XML-based HTML documents (report).
  • Closed as fixed:
  • No way to configure advanced settings in uMatrix/webext
  • Pages can detect uMatrix's presence with pure CSS

New in uMatrix for Chrome 1.2.1 RC 2 (Jan 18, 2018)

  • Notes:
  • Regarding the issue "uMatrix is causing iframe data to be mangled in the latest version of chrome":
  • I don't know what causes this -- uMatrix merely just add or modify a response header, as allowed by the extensions API. Until the root cause of the issue is resolved, you can mitigate it by changing the advanced setting disableCSPReportInjection to true in the new "More" dashboard pane.
  • Closed as fixed:
  • No way to configure advanced settings in uMatrix/webext
  • Pages can detect uMatrix's presence with pure CSS

New in uMatrix for Chrome 1.2.1 RC 0 (Jan 12, 2018)

  • Closed as fixed:
  • No way to configure advanced settings in uMatrix/webext
  • Pages can detect uMatrix's presence with pure CSS

New in uMatrix for Chrome 1.2.1 Beta 0 (Jan 8, 2018)

  • No way to configure advanced settings in uMatrix/webext
  • Pages can detect uMatrix's presence with pure CSS

New in uMatrix for Chrome 1.1.21 Beta 6 (Jan 4, 2018)

  • Per-scope switches:
  • New switch: "Forbid web workers"
  • Purpose should be obvious.
  • Note that nuisance coin miners typically use web workers, so forbidding web workers globally might be a good idea, though mind that there are legitimate use for web workers. Keep in mind many of these miners are launched as 1st-party, so the new switch allows you to forbid them even when you allow 1st-party scripts.
  • uMatrix is able to detect when a web worker is being instantiated. However, this does not work for Firefox 57-58, but works fine in Firefox 59 (Nightly). The reason is that SecurityViolationPolicyEvent has been implemented just recently in Nightly.
  • So this means if you are using uMatrix with Firefox 57-58, uMatrix will be unable to report to you whether web workers are used by a page, though you will be able to block these fine with the new per-scope switch. With Nightly, use (or attempt to use) web workers is properly reported in the logger and in the popup panel.
  • Per-scope switches redesigned and renamed:
  • "Strict HTTPS" has been renamed "Forbid mixed content": I see too many instances of people thinking this feature is a replacement for HTTPS Everywhere: it is not.
  • The new visual will now convey whether a switch is relevant for the current document. A dot in the toggle button means that the switch is relevant, i.e. uMatrix may affect the page if the switch is toggled on.
  • Forbid mixed content: a dot means that mixed content has been detected on the page.
  • Forbid web workers: a dot means that web workers have been detected on the page (as mentioned above, the detection does not work for Firefox 57-58).
  • Spoof referer header: a dot means that 3rd-party referrer information has been seen in network traffic.
  • Spoof <noscript> tags: a dot means <noscript> tags have been detected in the current page.
  • I added info links to each per-scope switch: the links are pages from Mozilla Developer Network, so this gives a chance for the page to load in the user locale.
  • Logger:
  • Ability to open the logger in the sidebar. Sidebar API is only available in Firefox and Opera

New in uMatrix for Chrome 1.1.21 Beta 5 (Jan 3, 2018)

  • Appearance:
  • More choices of text size for the matrix UI in the Settings pane (text size dictates the popup panel size).
  • Per-scope switches:
  • New switch: "Forbid web workers"
  • Purpose should be obvious.
  • Note that nuisance coin miners typically use web workers, so forbidding web workers globally might be a good idea, though mind that there are legitimate use for web workers. Keep in mind many of these miners are launched as 1st-party, so the new switch allows you to forbid them even when you allow 1st-party scripts.
  • uMatrix is able to detect when a web worker is being instantiated. However, this does not work for Firefox 57-58, but works fine in Firefox 59 (Nightly). The reason is that SecurityViolationPolicyEvent has been implemented just recently in Nightly.
  • So this means if you are using uMatrix with Firefox 57-58, uMatrix will be unable to report to you whether web workers are used by a page, though you will be able to block these fine with the new per-scope switch. With Nightly, use (or attempt to use) web workers is properly reported in the logger and in the popup panel.
  • Per-scope switches redesigned and renamed:
  • "Strict HTTPS" has been renamed "Forbid mixed content": I see too many instances of people thinking this feature is a replacement for HTTPS Everywhere: it is not.
  • The new visual will now convey whether a switch is relevant for the current document. A dot in the toggle button means that the switch is relevant, i.e. uMatrix may affect the page if the switch is toggled on.
  • Forbid mixed content: a dot means that mixed content has been detected on the page.
  • Forbid web workers: a dot means that web workers have been detected on the page (as mentioned above, does not work for Firefox 57-58).
  • Spoof referer header: a dot means that 3rd-party referrer information has been seen in network traffic.
  • Spoof <noscript> tags: a dot means <noscript> tags have been detected in the current page.
  • I added info links to each per-scope switch: the links are pages from Mozilla Developer Network, so this gives a chance for the page to load in the user locale.

New in uMatrix for Chrome 1.1.21 Beta 2 (Dec 22, 2017)

  • Appearance
  • More choices of text size for the matrix UI in the Settings pane.
  • Per-scope switches
  • "Strict HTTPS" has been renamed "Forbid mixed content": I see too many instances of people thinking this feature is a replacement for HTTPS Everywhere: it is not.
  • The visual of the per-scope switches will now convey whether a switch is relevant for the current document. A dot in the toggle button means that the switch is relevant, i.e. uMatrix may affect the page if the switch is toggled on.
  • Forbid mixed content: a dot means that mixed content has been detected on the page.
  • Spoof referer header: a dot means that 3rd-party referrer information has been seen in network traffic.
  • Spoof <noscript> tags: a dot means <noscript> tags have been detected in the current page.
  • I added info links to each per-scope switch: the links are pages from Mozilla Developer Network, so this gives a chance for a page in the user locale to load.

New in uMatrix for Chrome 1.1.21 Beta 1 (Dec 18, 2017)

  • Changes:
  • More choices of text size for the matrix UI
  • "Strict HTTPS" has been renamed "Forbid mixed content": I see too many instances of people thinking this feature is a replacement for HTTPS Everywhere: It is not
  • I added info links to each per-scope switch
  • The links are pages from Mozilla Developer Network, so this gives a chance for a page in the user locale to load

New in uMatrix for Chrome 1.1.20 (Dec 14, 2017)

  • Settings:
  • A new option in the Settings pane, as requested in #335:
  • Collapse placeholder of blacklisted elements
  • Checked by default.
  • The purpose of this new setting should be obvious: it makes it possible to collapse discriminately elements according to whether they were blocked as a result of a hostname being blacklisted or as a result for a more generic block rule.
  • For example, 3rd-party iframes are blocked by default. But you may not want embedded Youtube videos to be collapsed, while on the other hand you may want embedded ads from some blacklisted origins to be visually collapsed. The new settings allows to distinguish between blocked and blacklisted.
  • Logger:
  • The logger will now inform when uMatrix removes/modifies HTTP headers:
  • As seen above, the uppercase COOKIE entry means that an outgoing Cookie header was removed, and the uppercase REFERER entrie means that an outgoing Referer header was modified from https://news.ycombinator.com/ to https://danluu.com/. These are reported only for network request of type doc, so as to not spam logger output since referrer spoofing and cookie header removal can occur for every single network request.
  • Closed as fixed:
  • Core:
  • Blocked images download but only briefly display when loaded directly
  • Remove Referer instead of spoofing it for non-GET requests
  • SVGs not interact properly if scripts are blocked (though it says 0 scripts in the page)
  • Script not detected on cgit commit page
  • Collapse placeholders for blacklisted hostnames

New in uMatrix for Chrome 1.1.19 RC1 (Dec 12, 2017)

  • Settings:
  • A new option in the Settings pane, as requested in #335:
  • Collapse placeholder of blacklisted elements
  • Checked by default.
  • The purpose of this new setting should be obvious: it makes it possible to collapse discriminately elements according to whether they were blocked as a result of a hostname being blacklisted or as a result for a more generic block rule.
  • For example, 3rd-party iframes are blocked by default. But you may not want embedded Youtube videos to be collapsed, while on the other hand you may want embedded ads from some blacklisted origins to be visually collapsed. The new settings allows to distinguish between blocked and blacklisted.
  • Logger:
  • The logger will now inform when uMatrix removes/modifies HTTP headers:
  • As seen above, the uppercase COOKIE entry means that an outgoing Cookie header was removed, and the uppercase REFERER entrie means that an outgoing Referer header was modified from https://news.ycombinator.com/ to https://danluu.com/. These are reported only for network request of type doc, so as to not spam logger output since referrer spoofing and cookie header removal can occur for every single network request.
  • Accepted pull requests:
  • Fix noscript spoof setting not being saved on change
  • Closed as fixed:
  • Core:
  • Blocked images download but only briefly display when loaded directly
  • Remove Referer instead of spoofing it for non-GET requests
  • SVGs not interact properly if scripts are blocked (though it says 0 scripts in the page)
  • Script not detected on cgit commit page
  • Collapse placeholders for blacklisted hostnames

New in uMatrix for Chrome 1.1.19 Beta 2 (Dec 11, 2017)

  • SettingsL
  • A new option in the Settings pane, as requested in #335:
  • Collapse placeholder of blacklisted elements
  • Checked by default.
  • The purpose of this new setting should be obvious: it makes it possible to collapse discriminately elements according to whether they were blocked as a result of a hostname being blacklisted or as a result for a more generic block rule.
  • For example, 3rd-party iframes are blocked by default. But you may not want embedded Youtube videos to be collapsed, while on the other hand you may want embedded ads from some blacklisted origins to be visually collapsed. The new settings allows to distinguish between blocked and blacklisted.
  • Logger:
  • The logger will now inform when uMatrix removes/modifies HTTP headers:
  • As seen above, the uppercase COOKIE entry means that an outgoing Cookie header was removed, and the uppercase REFERER entrie means that an outgoing Referer header was modified from https://news.ycombinator.com/ to https://danluu.com/. These are reported only for network request of type doc, so as to not spam logger output since referrer spoofing and cookie header removal can occur for every single network request.
  • Closed as fixed:
  • Core:
  • Blocked images download but only briefly display when loaded directly
  • Remove Referer instead of spoofing it for non-GET requests
  • Collapse placeholders for blacklisted hostnames

New in uMatrix for Chrome 1.1.18 (Dec 7, 2017)

  • Changes:
  • Since version 1.1.14, the minimum version for Chromium/Chrome is version 45.
  • Closed as fixed:
  • Core:
  • Completed fix to "<noscript> is ignored when uMatrix blocks JavaScript"
  • Automatic redirect when there is a meta http-equiv="refresh" ...> tag present.

New in uMatrix for Chrome 1.1.17 RC 0 (Dec 6, 2017)

  • Changes:
  • Since version 1.1.14, the minimum version for Chromium/Chrome is version 45.
  • Completed fix to "<noscript> is ignored when uMatrix blocks JavaScript"
  • Automatic redirect when there is a meta http-equiv="refresh" ...> tag present.

New in uMatrix for Chrome 1.1.13 RC 0 (Dec 4, 2017)

  • The Privacy pane has been merged into the Settings pane in the dashboard.
  • Privacy-wise flawed user agent switcher removed
  • User agent spoofing as been removed. This was planned since a long while. The bottom line is that user agent spoofing for privacy purpose is best left to a dedicated extension, and really your best choice privacy-wise is probably to rely on Firefox's recent fingerprinting-resistance feature.
  • <noscript> tags
  • A new global setting has been added in the dashboard: "Spoof <noscript> tags when 1st-party scripts are blocked". Disabled by default so as to not change uMatrix's current behavior.
  • Since spoofing <noscript> is not necessarily always desirable, the global setting can be overridden on a per-scope basis with the "<script> tag spoofing" switch.
  • Note that this might be the long term approach used for enabling <noscript> tags: the approach planned by Firefox is not really suitable to uMatrix, as this would require to completely disable javascript for a site (causing the matrix ruleset to be disregarded), while with the current approach, one can still enable 3rd-party scripts and yet have the <noscript> tags spoofed.
  • I have observed that the feature behave slightly differently on Firefox than on Chromium: Firefox will not react to <meta http-equiv="refresh"> tags, while Chromium does. I do believe this can be fixed, and I will experiment more with this.
  • Blocked root document
  • Ability to parse the URL of blocked document has been imported from uBO
  • Unlike uBO however, the parsed URL information is expanded by default since uMatrix is meant for advanced users (you can collapse it by clicking on the magnifier).
  • Logger
  • Ability to open the logger in its own (popup) window, just as with uBO. If you want the logger to be in its own separate window, press Shift while clicking the logger icon will cause the logger to always be launched as a separate window. You do not need to press the Shift next time, it's only used to toggle between both attached/detached states.

New in uMatrix for Chrome 1.1.12 (Nov 27, 2017)

  • New mini-guides:
  • The popup panel
  • How to block 1st-party scripts everywhere by default
  • How to work in hard 3rd-party default-deny by default
  • How to work with only global rules and all scripts blocked by default
  • How to "allow-all" in uMatrix

New in uMatrix for Chrome 1.1.7 Beta (Nov 22, 2017)

  • You can now set the default scope level in the Settings pane in the dashboard (as requested in #821). The popup panel will always use the selected default scope the first time it is opened (whereas before the last selected scope was used).
  • The scope selector in the popup panel has been revisited as per suggested solution in #821. It works so well compared to the previous way of selecting a scope (dropdown list) that I would like to move this update to stable release as soon as possible. Other virtuous side effects:
  • it puts the ability to work in global scope in full view -- this will probably help dispel the often heard erroneous conclusion that it is not possible to create global rules.
  • it also enables the ability to set to the scope to anything in between full hostname and top-level domain (as per Public Suffix List).

New in uMatrix for Chrome 1.1.6 (Nov 21, 2017)

  • Important: A new default rule has been added following investigation of that issue. The rule will exist for new installations of uMatrix, but will not be imported for existing installations of uMatrix. In such case, I strongly suggest you add it manually in your My rules pane (don't forget to commit):
  • Matrix-off: wyciwyg-scheme true
  • Closed as fixed:
  • Frames still blocked after pressing umatrix reload button
  • Pressing Shift while clicking the reload button will now cause the browser cache to be bypassed, which is sometimes necessary after adding/removing rules.
  • Make placeholders in iframes clickable
  • The placeholders were already clickable, the clickable item has just been made a bit larger.

New in uMatrix for Chrome 1.1.5 RC0 (Nov 20, 2017)

  • Changes
  • Important: A new default rule has been added following investigation of that issue. The rule will exist for new installations of uMatrix, but will not be imported for existing installations of uMatrix. In such case, I strongly suggest you add it manually in your My rules pane (don't forget to commit):
  • matrix-off: wyciwyg-scheme true
  • Closed as fixed:
  • frames still blocked after pressing umatrix reload button
  • Pressing Shift while clicking the reload button will now cause the browser cache to be bypassed, which is sometimes necessary after adding/removing rules.
  • Make placeholders in iframes clickable
  • The placeholders were already clickable, the clickable item has just been made a bit larger.

New in uMatrix for Chrome 1.1.3 Beta (Nov 14, 2017)

  • Cloud storage merge button broken
  • "Preferences" in about:addons should lead to the preferences

New in uMatrix for Chrome 1.1.2 (Nov 12, 2017)

  • Chromium:
  • Removed legacy code (from HTTPSB) related to keyboard shortcuts.

New in uMatrix for Chrome 1.0.1 beta 5 (Aug 11, 2017)

  • Given the announcement that legacy extensions will be disabled tomorrow in the Nightly build, I pushed uMatrix/webext -- the pure WebExtension version -- to dev channel of uMatrix on AMO.
  • If you wish to migrate from 1.0.0 to uMatrix/webext but want to keep all your settings/data, just go through the intermediate step of installing uMatrix/webext-hybrid before installing uMatrix/webext. The most recent uMatrix/webext-hybrid is 1.0.1b4, available in dev channel on AMO.

New in uMatrix for Chrome 1.0.1 beta 3 (Aug 2, 2017)

  • uMatrix is now a uMatrix/webext-legacy extension on AMO's dev channel. Consider uMatrix/legacy unusable for Firefox Nightly

New in uMatrix for Chrome 1.0.0 (Jul 6, 2017)

  • Changes:
  • Media resources are now reported in the image plugin column (to be renamed media), having these reported in the other column does not make much sense. Typically, users of uMatrix would have the click-to-play setting for plug-ins enabled in their browser -- this has always been the recommended settings. Hence this means that if one allow media, this won't necessarily allow plugins, these will still be click-to-play. Plugins are slowly disappearing, and having a column strictly dedicated to plugins is wasteful, thus I decided to merge media and plugins.
  • Websocket connection attempts are reported in the xhr column.
  • There is now a badge on the per-site switches icon, which badge displays the number of switches which are currently turned on. This should help remind user to also check for these switches when trying to un-break a web page.
  • The assets management code has been refactored by importing code from uBlock Origin. Given the amount of work required and given the not-enough-time issue, all the hosts files you may have un-selected will be selected again. You will have to un-selected them again. Sorry, I just do not have the time for backward compatibility.
  • There is now a hybrid webextension version for uMatrix, see uMatrix.webext.zip below. The migration process is exactly the same as with uBlock Origin, see https://github.com/gorhill/uBlock/releases.
  • Closed as fixed:
  • Add Support for WebSocket Connections for Chromium
  • UI glitch
  • Possibly a browser bug as the issue didn't exist until recent Chromium versions (57+). However I do not have time to investigate, the fix is to work around the weird issue observed in Chromium.

New in uMatrix for Chrome 0.9.3.6 (Jul 6, 2017)

  • Closed as fixed - Core:
  • CSP rule breaks site unless 1st party scripts are allowed
  • No number in icon

New in uMatrix for Chrome 0.9.3.4 (Jul 6, 2017)

  • Changes:
  • Added zh_TW translation into the package. The Chinese Traditional translation had been available since a while, but I forgot to modify the script used to import translation from Crowdin.

New in uMatrix for Chrome 0.9.3.3 (Jul 6, 2017)

  • 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)

New in uMatrix for Chrome 0.9.3.2 (Jul 6, 2017)

  • Fixed:
  • Cropped uMatrix popup in Chrome

New in uMatrix for Chrome 0.9.3.1 (Jul 6, 2017)

  • 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.