-
Notifications
You must be signed in to change notification settings - Fork 80
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
Doesn't work with app-cache package #136
Comments
I think that what app-cache does. You need to avoid using app-cache. On Wed, Sep 9, 2015 at 3:12 PM Artem Saffron notifications@github.com
|
And what about its benefits of caching js files? I want the best of both worlds!)) |
I'm not an expert with appcache stuff. So, I'm not the best guy to answer this :) May be if you find a way to use the appcache, only if your system goes offline. |
I see. I'm not an expert either. But I'll amend the readme about this if you don't mind. |
Okay. Send me a PR. On Wed, Sep 9, 2015 at 3:56 PM Artem Saffron notifications@github.com
|
Surely the advantage of appcache is faster page loads on subsequent visits? It's good for apps that don't need offline support too. |
On first load data is injected just fine.
But on reload, when app.manifest is present in the browser's cache - fastRender is simply ignored by the browser and no html injection occurs.
Tested in Chrome 45 and Edge
The text was updated successfully, but these errors were encountered: