![]() ![]() Side Panel API In Chrome 116 you can use sidepanel.open() to open the extension side panel programmatically in response to a user gesture, such as a context menu click.For example, you can check if there's an active offscreen document. Runtime API: Starting in Chrome 116, you can use runtime.getContexts() to retrieve information about active contexts.In Chrome 118, extensions will not be allowed to navigate to file:// URLs using the chrome.tabs and chrome.windows APIs unless the “Allow access to file URLs” option is enabled on the extension’s details page. For a deep dive, see Bringing Safety Check to the chrome://extensions page. This can happen if the developer unpublishes the extension, it's taken down for policy violations, or it's identified as malware. In Chrome 117, users will receive proactive notifications on the Chrome Extensions page if an extension they've installed is no longer available on the Chrome Web Store. In Chrome 117, we expanded the number of supported chrome:// URLs, and the Javascript URL blocking now also applies to all extension API methods. ![]() Also, tabs.update() couldn't open a Javascript URL. Previously, navigating to some chrome:// URLs using tabs.update(), tabs.create, and windows.create() emitted an error or would crash Chrome. If your users still encounter service worker-related stability issues in Chrome versions after 119, please let us know. From Chrome 118 onward, a service worker will stay alive during an active Debugger API session.Ĭheck out our updated Service Worker guidance for more details. In Chrome 116, we added strong keep-alives to extension APIs that display a user prompt and improved support for WebSockets (see the Using WebSockets in extensions tutorial). Service worker-related stability issues have been resolved. Check out the updated known issues page for more details. All features are currently available in Chrome 120 Canary, except fileHandler support for ChromeOS Lacros, and the userScripts API which will land later this month. In Chrome 120, we will have finished addressing all our prioritized platform gaps and closed all critical bugs that are documented on the known issues page. Chrome 116 launched many improvements that helped us make significant progress toward closing the feature gap between Manifest V2 and V3. The extension team has been actively working to resolve Manifest V3 stability issues. See the chromium release schedule for details. All launches are currently available in the latest Beta release. In this section, we share some significant API launches, briefly review other API improvements, and share upcoming releases. section for new extension features you can start looking forward to □. Let's get started! Note: If you’d like a TL DR, feel free to jump to the Coming soon. Welcome to the October edition! In this post, we'll look at some of the changes the Chrome extension team has made in the past few months, as well as some new features that'll come out later this year. Thanks to your valuable feedback and our ongoing collaboration with fellow browser vendors in the WebExtensions Community Group, we continue to enhance extension APIs and work towards greater consistency across browsers. ![]() Back in July, we launched a new blog series to keep you up-to-date on extension developments. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |