mhalachev commented on issue #6601: URL: https://github.com/apache/netbeans/issues/6601#issuecomment-2025546108
Indeed, it would be advisable to upgrade the extension to Manifest V3, preferably along with the next NB release, as Manifest V2 extensions are likely to be phased-out in the not-so-distant future. https://developer.chrome.com/blog/resuming-the-transition-to-mv3 TL;DR > We will begin disabling Manifest V2 extensions in [pre-stable versions of Chrome](https://developer.chrome.com/docs/web-platform/chrome-release-channels) (Dev, Canary, and Beta) as early as June 2024 […] Users [...] will see Manifest V2 extensions automatically disabled in their browser and will no longer be able to install Manifest V2 extensions from the Chrome Web Store. […] We expect it will take at least a month […] before expanding the rollout to stable channel Chrome. The process will require rewiring some internals while replacing the background page with a service worker. @mbien Would it be appropriate to get in touch with Jan Stola regarding the extension refactoring? @viero To date, the extension still functions, with some workarounds. First, the extension shall be manually enabled. Then, When Run Project is selected, NetBeans presents a message “Browser refused to debug this tab…”. However, if “Debug in NetBeans” is clicked from the extension’s menu right away, it performs as expected. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
