Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"save snapshot" not working on Firefox 44.0.2? #600

Closed
iherman opened this issue Mar 3, 2016 · 5 comments
Closed

"save snapshot" not working on Firefox 44.0.2? #600

iherman opened this issue Mar 3, 2016 · 5 comments
Labels

Comments

@iherman
Copy link
Member

iherman commented Mar 3, 2016

I run https://w3c.github.io/csvw/syntax/ in FF 44.0.2 on Mac OS X 10.11.3 (El Capitan); pushing the 'Respec' button gives the pop-up menu, but none of the actions work:-(

The same file works on Chrome on the same machine.

@iherman iherman added the bug label Mar 3, 2016
@tripu
Copy link
Member

tripu commented Mar 3, 2016

I can't reproduce it on Linux.
@iherman, can you clear your browser's cache and retry? Also, see if there are JS errors on the console (I think it's ⌘+shift+K) or if any of the assets failed loading (perhaps ⌘+shift+Q)?

@iherman iherman closed this as completed Mar 3, 2016
@iherman
Copy link
Member Author

iherman commented Mar 3, 2016

Oops, a cache clear did it. But how come? Were there such drastic changes?

Anyway… sorry for the noise

@tripu
Copy link
Member

tripu commented Mar 3, 2016

No idea. It's difficult to predict the behaviour of pages when some of their assets are stuck in a cache somewhere between the source and the user…

@halindrome
Copy link
Contributor

Yes - respec was effectively rewritten in the last two weeks. Well, more
or less.

On Thu, Mar 3, 2016 at 9:22 AM, tripu notifications@github.com wrote:

No idea. It's difficult to predict the behaviour of pages when some of
their assets are stuck in a cache somewhere between the source and the user…


Reply to this email directly or view it on GitHub
#600 (comment).

Shane McCarron
halindrome@gmail.com

@marcoscaceres
Copy link
Member

Browsers cache very aggressively. I need to check what headers the w3c servers are using. I'm also thinking that using service workers to perform updates might help here.

Sent from my iPhone

On 4 Mar 2016, at 2:22 AM, tripu notifications@github.com wrote:

No idea. It's difficult to predict the behaviour of pages when some of their assets are stuck in a cache somewhere between the source and the user…


Reply to this email directly or view it on GitHub.

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

No branches or pull requests

4 participants