4 ms·
First of all, thanks for InboxSDK! Looking at it now, it's actually mostly InboxSDK extensions that are conflicting with Gmelius and some other custom extensio
by timvdalen 10y ago
First of all, thanks for InboxSDK!
Looking at it now, it's actually mostly InboxSDK extensions that are conflicting with Gmelius and some other custom extensions.
Having 10+ extensions all trying to modify the DOM of one site at the same time is bound to give some problems :).
Curious to see if Streak will switch to this new official way, although it seems that a lot of the stuff you're doing won't be available to Add-ons.
- alooPotato 10y agoGmelius is actually using parts of the SDK. But they are really aggressive and do some DOM manipulation. In general we hope that users of the InboxSDK never need to actually touch the DOM ever. The SDK handles coordination across extensions. Ofcourse extension don't have to abide by this and hence the conflicts. As for Streak, we're planning on a mixed approach. The add-ons from Google support very few UI entry points (at least for now). Streak's entire UI only lives in Gmail so we need a lot more integrations. We'll use the Google sanctioned way when possible and fall back on the extension as we currently have now for the other cases.
- siva_narayanan 10y agoFirst of all, big shoutout to InboxSDK / Streak folks. Our extension, Fyle (http://www.fyle.in http://www.fyle.in) would've been ridiculously more difficult without it. We're having an issue with Gmelius interacting badly with our extension. Basically, we never enter our messageViewHandler code when Gmelius finds a tracker. Have reached out to them as well.