InboxSDK
Dealing with Gmail breaking changes without remote code loading (MV3)
With Chrome MV3, we can't remote-load code, which removes our previous way of quickly reacting to Gmail changes that break InboxSDK compatibility. This is an issue tracking some of our plans to work on making InboxSDK resilient in the face of future Gmail changes that might surprise us and break certain functionality.
- Fallbacks for navmenu, custom views, thread sidebar, etc, so if we fail to find the elements to inject these features into, we have a less-integrated but dependable alternative implementation (for navmenu/sidebar, a position:fixed toggleable pop-in available at the side of the screen, and for custom views a position:fixed modal).
- Remote-loaded config that includes:
- CSS selectors to use to find elements (and page-parser-tree configurations)
- object paths in request interception for email send events
- whether to force fallbacks (possibly conditional on specified CSS selectors matching)
- selectors to log censorHTMLTree() results on to help debug unseen Gmail HTML structure
- console logging messages to developers when they're using a critically outdated InboxSDK version
The remote-loaded config will be something hosted by us. We can add options to allow this config to be disabled or fetched from an alternative URL in case some extension developers want to be able to manage it on their own.
Really interesting. It's so cool you decided to maintain a server that would help us all. 🙏🏻
This is a great change. @Macil do you have any etas for when it'll be available?
@Macil Any updates on this one? We would like to move to V3 ASAP (even with Google Postponing sunset) and this feature can be great help!
do we have any info on this? Im deploying an app but afraid that it is gonna break on jan 2024
Sorry, I was confused by the comments on this issue originally. The InboxSDK is already available with Chrome MV3 support with its npm release. Existing MV2 extensions will need to update from the original "inboxsdk.js" version to using the npm release. Please open a new issue if you have questions or run into problems with that.
Is there a documentation for it?
On Fri, Apr 28, 2023, 1:08 AM Chris Cowan @.***> wrote:
Sorry, I was confused by the comments on this issue originally. The InboxSDK is already available with Chrome MV3 support with its npm release. Existing MV2 extensions will need to update from the original "inboxsdk.js" version to using the npm release. Please open a new issue if you have questions or run into problems with that.
— Reply to this email directly, view it on GitHub https://github.com/InboxSDK/InboxSDK/issues/798#issuecomment-1526958225, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAOMOSQJOFA74AYESO3CKUTXDM7CVANCNFSM6AAAAAARJYMFSM . You are receiving this because you commented.Message ID: @.***>