![]() ![]() Add elements vararg to prevent-addEventListener scriptlet.Do not prevent applying changes when lists are updating.Shield some code paths against potentially tampered global properties (in scriptlets).Do not exceed rate-limited calls to handlerBehaviorChanged().Add support to toggle no-scripting switch with keyboard shortcut.Empty query parameters must still use =.Provide visual feedback when applying changes in "Filter lists" pane.Prevent access to picker when "My filters" is not enabled.Mark procedural filters with pseudo-elements selector as invalid.Fix improperly assembled !#include sublists.Remember presentation state of "My rules" pane.Allow uritransform to process the hash part of a URL.Unregister all scriptlets when disabling uBO on a specific site.Remove minimum height constraint from "My filters" pane.Add support for extraMatch in trusted-click-element scriptlet.Fix decompiling of scriptlet parameters.Ignore event handler-related attributes in set-attr scriptlet (suggested by Fix potential exfiltration of browsing history by a rogue list author through csp= (reported by Output scriptlet logging information to the logger.Fix Chartbeat flicker control div's (by Fix potential exfiltration of browsing history by a rogue list author through permissions=.Improve prevent-addEventListener scriptlet. ![]() Fix improper invalidation of valid uritransform exception filters.Fix incorrect built-in filtering expression in logger.Mind that multiple uritransform may apply to a single request.The Microsoft Store version of uBO is published by Nicole Rolls Chromium: Install from the Chrome store:.In particular, we’d like to thank members of the WECG for their engagement, including AdGuard for sharing a significant amount of the data that drove this work, and all browser vendors who have all been a major part of designing this API. We are committed to continuing to invest in the declarativeNetRequest API so we can support as many use cases as possible, and look forward to continuing to work with the community. As a result, the team has decided to raise a previously imposed limit and ease certain safety-related restrictions. Regarding ad blockers, Google has acknowledged the persuasive evidence presented by extension developers. Enhanced content filtering support with more generous limits in the declarativeNetRequest API for static and dynamic rules.A new User Scripts API, enabling safer user script management for extensions.Simplified control over service worker lifetimes for extensions performing long-term tasks like receiving events.Offscreen Documents, which grant DOM access for extensions to use in scenarios like audio playback.Originally scheduled for 2023, the transition to Manifest V3 was pushed back as Google focused on closing the functionality gap between the two versions with several key updates. The exact timing may vary depending on the data collected, and during this time, we will keep you informed about our progress. We expect it will take at least a month to observe and stabilize the changes in pre-stable before expanding the rollout to stable channel Chrome, where it will also gradually roll out over time. This change will be rolled out gradually, with Google taking into account user feedback and data to ensure that Chrome users understand the update and have the option to find alternative, up-to-date extensions. To ensure a smooth transition, developers are encouraged to update and migrate their extensions before the deadline. Starting June 2024 (Chrome 127+), Google will automatically disable Manifest V2 extensions in Chrome Dev, Canary, and Beta.Īdditionally, Chrome Web Store installs will no longer be possible. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |