Optimization Request: pre-load

[sbatchelder]

To improve experience on the Localizations/Corrections views, my users asked if it would be possible to pre-load the "Next" pagination page ahead to time to avoid waiting having to wait for the localizations to buffer/load for faster loading.

As a developer too, I acknowledged that this would necessitate a pretty significant rework of the page and add a bunch of complexity, either converting it to a single-page app or some sort of browser-side pagination pre-caching. Maybe a library like ChromeLabs Quicklink would be applicable. Good luck with this one.

[bctcvai]

This is a good suggestion. We have looked at this issue from the annotator view experience.

I agree an architecture like Quicklink is worth looking into. A nuance on our end the localization graphics you see in the UI are generated server-side off of the raw media files, so in addition to pre-load scheme for caching, I think we'd also want to add some server-side caching of that generated imagery. Doing both I think you'd end up with a much snappier experience when perusing over paginated data.

[jrtcppv]

This may be addressed by #1660