In some cases, installation may be blocked until browser restart.Use add-on store or links in release description on GitHub releases page when they are available (basically - they will be add-on store links).Do not use links from release page "Assets" section - these are not signed.Visit GitHub releases page for more information.Įxtension will be auto-updated after browser restart! (when available for your platform) Remove unmaintained urlhaus PUP filter list.Support restoring backups from application/json file.Add filtering expressions for logger output.Consider My filters an untrusted source by default ( scriptlets with trusted- in the name and urltransform option is blocked).Add warning against adding custom filters from untrusted sources.Ignore assets older than cached version when fetching from CDNs.Add ability to update lists through links with specifically crafted URLs.Bring header= filter option out of experimental status.Add new static network filter option: urltransform.Reduce race conditions in scriptlet injection on Firefox.Add stackToMatch vararg to json-prune-related scriptlets.Use safe versions of Math.floor/ Math.random in scriptlets.Fix overzealous matching in (remove|replace)-node-text scriptlets.Add more values to set-cookie (by Support quoting scriptlet parameters with backticks.Fine tune set-local-storage-item as per feedback.Add dontOverwrite vararg to (trusted-)set-cookie scriptlets.Match type exactly in prevent-addEventListener scriptlet. Add scriptlet aliases for compatibility with AdGuard lists.Support AdGuard's (trusted-)set-cookie-reload scriptlets.Improve google-ima shim script (by Add trusted-prune-inbound-object scriptlet.This release exists only as an attempt to unstuck publishing of 1.53.0 in Microsoft Edge Addons store. Bugfix for "crashing" when opening pdf files. Trusted sites directive syntaxįurther details about the supported syntax for trusted site directives can be found at "How to mark a web site as trusted". After 1.19.3b7 removed predefined trusted site directives are commented out automatically. This way you do not have to remember which predefined trusted site directive you removed, it will be just a matter of removing the # prefix if ever you want to restore an entry. To comment out an entry, just prefix it with #. If despite this warning you still want to remove one or more of the predefined trusted site directives, I strongly suggest to comment out an entry rather than outright delete it. This is especially true for the behind-the-scene trusted site directive on Firefox Legacy platform. Removing the predefined trusted site directives without understanding the consequences could cause your browser to malfunction. You should not remove these predefined trusted site directives, unless you know exactly the consequences of doing so. There are predefined trusted site directives when you first install uBO:įor Firefox Legacy platform, behind-the-scene is also in this predefined trusted sites list. The Trusted sites pane allows you to review or edit the existing trusted site directives, or to manually add new ones. The easiest way to create a trusted site directive is by toggling the large "power" button in uBO's popup panel - this will cause a site-wide trusted site directive for the current site to be automatically created and added to the Trusted sites pane. When there is a match, uBO will be disabled for that page. When you visit a web page, uBO will try to match the URL of the page in the address bar against the existing trusted site directives. When uBO is disabled for a site, its toolbar icon will be grayed, and the large blue "power" button in the popup panel is dimmed. When uBO is disabled on a page, there will be no filtering applied to that page. The purpose of a trusted site directive is to tell on which page uBlock Origin (uBO) should disable itself completely. The Trusted sites pane lists all the trusted site directives.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |