-
Notifications
You must be signed in to change notification settings - Fork 22
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
Google Inbox plugin #109
Comments
+1 |
+1 |
Keyboard completion and CTRL+SPACE Work. Need to add support variables + quick access button. |
+1 |
4 similar comments
+1 |
+1 |
+1 |
+1 |
@xarg what do you think of asking a freelancer to do it? |
@ghinda can you please have a look at what can we do here? There is really lots of demand for this. |
Started work on the plugin for Google Inbox. It's still very much wip. Will finish it up after the new year's. |
@ghinda seems there are some issues with Inbox still. For example the text sometimes goes outside of the edit area and stays there. See the gif below: To reproduce this, I deleted all the text and then used the dialog. Seems like it loses focus from the editor and goes to the element on top of it. Unrelated: Can we also add the little |
…, when the editor is empty. #109 (comment)
…, when the editor is empty. #109 (comment)
* Fix issues with inserting template before the editor, in Google Inbox, when the editor is empty. #109 (comment) * Implement a whitelist for the quick-action button, and enable it for google inbox. Fix broken quick-action button positioning, caused by trying to clone the boundingClientRect dimensions. The problem wasn't visibile because Gmail uses custom positioning. * In Google Inbox, the BCC field was filled with the CC value. * `from` stopped working in the Google Inbox plugin. Google Inbox changed the markup classes, so the account info node was not found. Change the way we get `from` data in the Inbox plugin, to prevent changed classes from affecting it.
Fixed in version 5.6.4 |
By popular request make a Google Inbox plugin.
The text was updated successfully, but these errors were encountered: