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
axios looks a good bet, onDownloadProgress will return us a progress event. Here's an example.
How would we expose this progress event to the user? via the config? I'm struggling to understand how we'd render and update a component alongside the static main view. Whaddaya thoughts?
importDefaultProgressfrom'./default-progress'constLoader=loadContext.customProgress||DefaultProgressclassAppextendsComponent{render(<div><Loadervalue={onDownloadProgress}/><Router>
// All your app stuff
</Router></div>)}
Maybe we could start with an event emitter proxy for a first version. Does that make sense and seem feasible?
When the Tapestry client JS bundle picks up routing and navigation, we lose any visual feedback on the progress of a page load.
The current implementation of Fetch does not have progress events, the idea is that on-the-fly calculation will be done using streams in the future.
In the meantime we will have to use an XHR solution that an
onprogress
even on the client.https://github.com/matthewwithanm/httpplease.js Seems like reasonable candidate - IE9 compatibility etc, haven't vetted it heavily though.
The text was updated successfully, but these errors were encountered: