Skip to content
This repository has been archived by the owner on Nov 15, 2017. It is now read-only.

Chromium-behind-the-scene feature might break Chrome store #27

Closed
gorhill opened this issue Oct 24, 2013 · 1 comment
Closed

Chromium-behind-the-scene feature might break Chrome store #27

gorhill opened this issue Oct 24, 2013 · 1 comment
Assignees
Labels
Milestone

Comments

@gorhill
Copy link
Owner

gorhill commented Oct 24, 2013

When trying to install an extension, Chrome store sends a request looking like this when user press "install" button:

other https://lh4.googleusercontent.com/UJOWaD1RWOFPtiiCILdm1TT0qaPQc8YuVstJd9Pbkvgeaa4FIMCULDjq0Lbm6Ka_LT5cQDQqM8k=s128-h128-e365

As seen in Stats page. If this behind-the-scene request is blocked (because user chose to block googleusercontent.com hostname), Chrome store reports:

An error has occurred
There was a problem adding the item to Chrome. Please refresh the page and try again.

@ghost ghost assigned gorhill Oct 24, 2013
@gorhill
Copy link
Owner Author

gorhill commented Oct 24, 2013

Only solution I can think of is to allow user to disengage the behind-the-scene feature: starting to put very specific hard-coded guessed workarounds in the code is not an option.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant