I'm developing a Chrome extension, which needs to call the Google Calendar API. I start with the quick start tutorial (for javascript) here:
https://developers.google.com/calendar/quickstart/js
And it works. But when I copied and pasted all the code into the extension html (which is popup.html in the official tutorial), it doesn't work. I cannot see the "Authorize" button in the popup page.
I suspect that the inputted "Authorized JavaScript origins" caused error (now I inputted "http://localhost:8000"). Or am I following a wrong example for making a Chrome Extension? Thanks!
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 making a Chrome Extension which changes the layout of a website. When my extension is activated and the website loads, you can briefly see the real website then it switches to my modified version loading in all the CSS and JS from the Chrome Extension. Though I've used other extensions that do something similar but have it displayed before anything actually shows the real website. One example is Shine for Reddit. When Reddit shows, it shows the extensions version of the website right at the start. How can I do this?
As shown in the image here:
Why would Chrome require a user to manually “Reload” an extension? The extension seems to be working for a while, then suddenly a user reports that it has stopped working and I have to instruct him/her to click the “Reload” link.
As an extension developer, I would like to be able to prevent this from happening. Here’s my extension in the Chrome Web Store.
Screenshot borrowed from a similar report from another developer.
I want to be able to call functions that I am writing in a Chrome extension from the JS console in Chrome, so that I can test them easily and see how their output changes as the page changes.
But it seems as the functions I write aren't available to the chrome JS console. I don't really understand JS that well, or the chrome extension model, but I need to somehow inject the extension source into the body of the page that I am using the extension for?
If you are talking about functions that you defined in a background page, then you need to go to your extensions page, check the developer mode box, and click on _generated_background_page.html. That is where you will find your background page code.
If you mean functions in a content script, then when you are in the console, go down to where it says <page context> and change it to your extension. Then you will have access to the functions in the content script.
Is there a way to detect if a particular tab was POSTed to via a Google Chrome extension? I am working on an extension that includes an "undo closed tab" type of function and would like to handle tabs which were POSTed to differently than GET pages.
I believe a solution exists in chrome.webRequest.onBeforeRequest via the 'method' return parameter. I will report back with a working code example once I have time to try this out.