-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compatibility with other Gmail extensions #554
Comments
Added support for RightInbox today. Will go out with v2.4.3. |
Look into supporting MightyText for Gmail |
Improved some minor visual details with Vocal in v2.5.4 |
Added warning for Dark Reader (they do not play nicely together but you can disable Dark Reader for just mail.google.com -- no need to uninstall entirely) |
Found some issues with Wordtune. Will see if I can address it and will warn users of incompatibility if I can't. |
@leggett I noticed that MailTrack is listed to work, but I'm having an issue where all the messages are being bundled together. This is whether or not they're the same email thread... The label generated by mailtrack is: label:mailtrack.io-clicks |
@topperge this list applies to Simplify v2. Your millage will vary with the v3 beta. I don't have a ton of love for helping track other people opening email. That says, I am working on a way to exclude labels from bundling (one of many musts to get out of beta). Can you hide the label from messages or does that make it less useful? |
I'm struggling to find a way to use Gmail with Simplify's dark/night theme. I'm on Linux, where Chrome appears to ignore the GTK theme [1]. One option to solve this is to use the flag Unfortunately, as you've mentioned - Dark Reader and Simplify don't play nice, but disabling Dark Reader just leaves me with a glaringly bright Gmail while the rest of my tabs are nicely adjusted. Do you think there might be some other way to achieve this? Perhaps a manual toggle for Simplify's own dark theme? Or perhaps enabling it based on Dark Reader's settings? [1] https://bugs.chromium.org/p/chromium/issues/detail?id=998903 |
@ben-foxmoore I have plans to revamp dark mode so I can auto-switch with the OS and improve other things. When I dig into this, I plan to also see if I can just detect Dark Reader and play nicely with it. I'll track this work on #562 but I won't start until I've finished bundles. |
I'm adding support for Salesforce and Bananatag |
Adding support for Hippo Video in v2.5.16 |
Added support for Loom and MailTracker (different from MailTrack) in v3.0.42 (still need to bring it to v2 or just launch v3 already) |
Added support for Trimbox |
Advice on using extensions with Gmail
Ironic as it may be given Simplify Gmail is an extension, I recommend using as few extensions as possible. I also prefer to use extensions that, like Simplify, do NOT require full API access to my email.
You can audit which extensions have access to Gmail by opening the extensions menu (screenshot below) while on Gmail and you can review what has access to your Gmail data under myaccount.google.com/permissions.
Reporting an issue with another extension
If you use an extension and it conflicts with Simplify, please report a new issue from Gmail via (Alt+I / Option+I or the Simplify menu > Report issue). More info at simpl.fyi/support. This will include a system report that will help me in trying to reproduce the issue.
Please include:
This is the Extension menu.
If you open it while on Gmail, it will highlight all the extensions that have some kind of access to Gmail.
Compatibility with other Gmail extensions:
Works as is (yay)
Simplify does something so it works (it may still have minor issues)
Not compatible (I don't block them, but I pop up a warning every time you load Gmail that says you should disable SImplify or the other extension)
Maybe ok together, ish? (I do something to sort of support them but still don't think it is a great experience – I need either more testing from someone who uses the extension or some way to let people "use at their own risk")
The text was updated successfully, but these errors were encountered: