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
While I initially thought this would not be an issue (since after all it only affects the production phase, it doesn't change anything to the "published" version), it is slow enough that reloading the in-progress document becomes painful, and thus makes the overall update process too cumbersome.
Probably worth revisiting when w3c/w3c-api#60 lands, in which case one can hope that beyond the "first" load, reloads should be reasonably faster.
An alternative (or a complement) is to integrate a Service Worker layer and use a cache-first strategy.
No description provided.
The text was updated successfully, but these errors were encountered: