I'm interesting in developing Chrome Extension for Gmail.
Unfortunately I couldn't find any tutorials on this subject (demonstrating a simple action as adding a button).
I'm looking for adding a button to the compose toolbar, and creating a new tag/folder in gmail account.
Please, Help!
You should check out these APIS at https://github.com/joscha/gmailr, it is a fork of https://github.com/jamesyu/gmailr but the original author has been too busy to update it.
Related
I currently have a chrome extension which adds a new button on the GMail Toolbar each time I open a message in GMail on a chrome tab. This is done currently using inboxSDK's (1) registerThreadViewHandler() and (2) registerMessageViewHandler()
Unfortunately, using inboxSDK library will make the extension call remote code which is disallowed in Manifest V3.
I would like to ask if there are other possible and sustainable ways to do this without inboxSDK.
Thank you very much.
I'm trying to add a support page right in the extension window but all that I can find is adding a link to another page. I've included some pictures, as I don't know how to really describe the feature.
that's what I have currently, and below is what I want to have-
This is a screenshot of what I have on the dev page, concerning the support feature-
I'm not sure what I need to change, so any help would be appreciated! (Directed here from this chrome forum thread)
Go to https://chrome.google.com/webstore/developer/dashboard
Click "Edit your User Feedback preferences"
Check the "Enable User Feedback for all my apps in Chrome Webstore." box.
Note that neither you nor your users will get notified of new posts made in the webstore support section, so you probably want to direct users to a third party support platform, such as issues on the project's Github repo.
I am developing a little extensions called "Tab Bundler", which in short saves all the open tabs in a window into a bundle that can be opened with the click of a button. When a bundle is opened however, no history of how the user got to that url is saved, ie. the user can't click back to see how they got to that url. This is functionality I want to implement. I looked for a while, googling, looking thoroughly through the google chrome extension documentation: http://code.google.com/chrome/extensions/history.html. But I couldn't figure out how to get this information without tracking it myself. Is that the only option I have? Any thoughts would be really appreciated.
Thanks!
Look, many people tried this before. You are not alone in this quest!
At the moment the answer in Google Code was: anybody asked for it when they where developing the History API. Then there's no elegant way to access tabs' history.
Of course, you can hook chrome.tabs.onUpdated to record every page and make your own tab's history...
You could probably hook chrome.tab.onUpdate as well as some state or focus change hook to correlate.
I really want this, please make it!
I'm not sure if this is the correct exchange for this questions as I don't think it is explicitly programming related, but I can't think of a better place to ask the question.
I keep seeing this tab for chrome extensions that allows users to ask questions, suggest things or submit problems:
I haven't been able to find anything in the developer dashboard or in documentation about this tab. I know that I can get a support tab with a link by adding a url to the support link field in the project settings, but I can't figure out how to get the functionality shown here.
Go to https://chrome.google.com/webstore/developer/dashboard
Click in the link:
Edit your User Feedback preferences: User Feedback is disabled
And then enable it.
It's the same answer for Where does the Chrome web store "Support" tab come from?, it works for Apps and extensions.
I'm trying to write a chrome extension that is used in the GMail compose screen. So far I have it working the way I want to except that when the GMail does its auto-save it removes my extension.
I'm adding in my extension with the content_script via java inject. and appending to the compose iframe.
Any help would be appreciated :)
You have to track DOM changes and re-add your code after the auto-save. There is another answer that gives a quick intro to DOMNodeInserted events. You should be able to watch for the Draft saved at ... insert.