You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 29, 2019. It is now read-only.
Hm, is this maybe a service worker or caching thing? I'm having trouble reproducing, either with my main Chrome profile, an incognito profile, or other browsers like Safari and Firefox.
I am seeing a bit of a delay while the page initializes on first navigation.
Ah, yeah, if a user gets a cached version of the iron-doc-viewer bundle, then it wouldn't have <iron-doc-module>, and the page would be blank.
Do we have a way of dealing with this in our service worker? If the user goes to any other page on the site, will the iron-doc-viewer bundle be updated? If that's the case, then only users that land on a specific 3.0 API docs as their first post-3.0 page view on the site will be affected.
We show the "Site updated, refresh to reload" toast, but you need to do a full page reload to get the new bundle. Clicking links on the same window will not trigger a full page reload.
Not really a way to "hotfix" since CEs are already defined, but maybe in the future we can just force the page to reload instead of just showing the toast.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
For example, navigate to: https://3-0-staging-dot-polymer-project.appspot.com/3.0/docs/api/polymer-element
Page is blank on initial load, displays correctly on reload.
The text was updated successfully, but these errors were encountered: