Re: [presentation-api] [ReSpec] Performance regression when loading spec over file:///

After some sleuthing this happens when the "block third party cookies" setting is enabled in Chrome.  Chrome treats each file:/// URL has having a unique origin - trying to access an IndexedDB from a file:/// URL seems to be blocked as "cross-origin."  I do not know if this is intentional or not.

Workarounds:
1. Enable third-party cookies.
2. Fire up a local HTTP server.

Either way I don't think this is something that ReSpec can be expected to fix, although a tip in the README might be helpful in case other editors encounter this.



-- 
GitHub Notification of comment by mfoltzgoogle
Please view or discuss this issue at https://github.com/w3c/presentation-api/issues/412#issuecomment-288887560 using your GitHub account

Received on Thursday, 23 March 2017 23:08:35 UTC