We accidentally submitted the wrong extension for review and don't see any way of cancelling it and re-submitting.
If this extension gets approved and subsequently pushed to our customers, it will 100% break.
There has to be a way to prevent this?
If we unpublish the extension, will it also stop the review and then allow us to re-submit it? Hopefully it won't come to this, but we need to stop this extension from being submitted/approved.
Any help would be appreciated.
Unfortunately there is no way to stop a review once submitted. What you can do is unpublished the extension and wait for the review to be complete. The new package wouldn't be available via the store so it will prevent browsers from auto-updating to the wrong extension.
After the review is complete you can then upload the correct extension and then republish after that review cycle has taken place.
Related
I am working on a security extension. I am using webrequest.onbeforerequst to intercept navigations and then do an analysis on it.. However, I am noticing that when chrome is not running and I click on a external link from email. My extension does not seem to be presented with that url. I think it might be a race condition that chrome is loading the page before my extension is loaded.
My question is if its possible to make sure chrome loads my extension, prior to the first navigation. Is anyone else seeing similar?
Note: If I enable background permission the issue is resolved, however users can exit at anytime to bypass the security, even if I set the policy to prevent disabling background process. Another mitigation would be if there is a policy to prevent the user from exiting chrome completely. From what I can find that is not possible.
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!
Link to previous issue: Gmail contextual gadget broken
Yesterday we received a couple of customer complaints regarding our Gmail gadget. They claimed that it had gone missing from their account. This morning, several of our employees have reported the same although, this isn't happening for everyone.
We haven't made any changes to the gadget and since it loads for some, I don't think this was caused by us.
What happens:
The window of the contextual gadget does not appear in the main Gmail interface
The window of the contextual gadget does not appear when opening an email in a new window (shift + click). This differs from when this happened previously.
We've also contacted Google and they have responded that they are looking into the issue. We've also seen that the shift-click to open an email in a new window doesn't work as a work around this time.
The last time this happened our monitoring showed that about 10% of users lost their access to the gadget per-day. We seeing a similar drop off in activity this time around.
Here are the details of the response I received from Google for this issue
Thank you for contacting Google for Work Support. I understand that
that you Gmail Contextual Gadgets have disappeared again from the
Gmail web interface.
I notice there are other user reporting a similar behavior hence he
have requested an update from our Eng team and I am currently waiting
for their response. As soon as I have an official response, I will be
contacting you back directly with the next steps.
Also I notice you mentioned that the previous workaround is no longer
working. Previously the workaround provided was to press "Shift" and
then click on the email. The email will be opened in a new window and
then the gadgets should be displayed. Can you please confirm if the
above workaround is working or not?
I’ll keep this case open while I wait for your reply. If you have any
other questions or additional comments, don’t hesitate to reply and
I'll be happy to continue helping you.
Sincerely,
Wilmer Google for Work Support
Here is the latest update from Google
As before this issue appears to be UI based as opposed to any problem with the Contextual Gadget API itself, we've gathered some troubleshooting information from affected test environments and are working on identifying a clear root cause and then remedying the behaviour at the moment.
There isn't any further you need to do on your end, I'll update you as I learn of any changes in the status of this behaviour.
Regards,
Patrick
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.
I built a quick one-off chrome extension about a month ago during the SOPA craziness. Long story short, it unblacked Wikipedia, so that people who needed it could get some work done.
Once the blackout was over, I updated the app to no longer have any effects on any websites. I also modified it so it would put a console.log() saying essentially "The blackout is over. SOPA is still important, but you should uninstall this extension".
Unfortunately, a month later, I'm still showing that 90% of the original users have the extension installed. Certainly it doesn't have that large of a footprint, but as a developer I feel it's my duty to not let my extension become crapware on my user's computers.
Is there a way to forcefully uninstall a chrome extension? Is there some way that would be unintrusive to the user that I could inform them that they should uninstall the extension?
You can update the extension so that it requires the 'management' permission, and then use chrome.management.uninstall to make the extension uninstall itself.
In my opinion, there is no way in this situation. Unless
If your extension makes a request to a server that you can access, such as a web service from you, maybe you can send an alert to your users.
If auto update is enabled in your extension, you can update your extension. In your updated version, you can show users an alert (shouldn't be a real javascript alert. Some kind of alert) to uninstall your extension.
If auto update is enabled, you may update your extension to do nothing. Just a console.log message.