[crx] old versions cached on client

[Daniel Kantor]

My extension is not in the gallery so I use the update_url property to update from my server. I have noticed that when users upgrade, they have half the new version and half the old one. I think this is b/c some pages are cached by the browser. A clearing of the cache or restart of Chrome usually fixes this. Obviously this is not ideal - the whole point of Chrome extensions is that the user doesn't need to restart. 

Would putting cache meta tags on my extension help? Here is what I am thinking about adding - 

<meta http-equiv="cache-control" content="no-store, no-cache, must-revalidate"> 

<meta http-equiv="pragma" content="no-cache"> 

<meta http-equiv="expires" content="-1">

Are there any other tags I should use? 

thanks,

Dan

--
You received this message because you are subscribed to the Google Groups "Chromium-extensions" group.
To post to this group, send email to chromium-...@chromium.org.
To unsubscribe from this group, send email to chromium-extens...@chromium.org.
For more options, visit this group at http://groups.google.com/a/chromium.org/group/chromium-extensions/?hl=en.

[Antony Sargent]

Can you elaborate on on what you mean by "..they have half the new version and half the old one"? One current limitation with content scripts is that when an extension gets updated, any currently open web pages that had script injected into them don't have the content script reloaded until that web page gets reloaded. Is it possible this is the issue you're seeing?

[Daniel Kantor]

Content scripts are not the issue I am seeing. 

I have 3 html pages - background, options and player. I have noticed (and have gotten a lot of feedback from users) that after updating, a page (ex. player.html) will show the old version even after refreshing the page. A cache clearing or Chrome restart usually clears this up. This also leads to older javascript files which throws errors. 

[Antony Sargent]

Do you know what versions of chrome and on what platforms (win,mac,linux?) people are seeing the problem?

Are you able to reproduce this yourself? You could try creating two different .crx files with some obvious difference in one of the pages, install the first .crx file by dragging onto the browser, open up the page, and then install the second .crx file by dragging onto the browser. 

If you are able to reproduce it please file a bug at http://crbug.com and include the crx files. This seems like a fairly serious issue we'd like to fix asap if we can find a reproducible case.

[Daniel Kantor]

I believe it is happening on at least Mac and Windows. I have seen it on Mac. I will make the 2 crx files and test.