-
Notifications
You must be signed in to change notification settings - Fork 84
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
Feature Request: have IIIF progressively enhance simple derivatives #108
Comments
Linked a pull request with the simplest possible version of this. If OSD is enabled, it tries to load both sources, with |
Alternative approach would be to build a parallel site without javascript, auto-redirect to that site, and then kill the redirect with javascript. Slightly more expensive on the non-JS pages; I don't know how it plays with internet Archive. https://webplatform.github.io/docs/concepts/redirect_no_javascr |
Hi everyone, thanks for all your work on this. Really excited about getting to use this in teaching.
If it's OK to post a wishlist item: What should happen in JS-free environments? (Maybe humans, more likely spiders and scrapers). Currently, if you enable IIIF derivatives, loading a wax site with JS disabled means you get an image-free web page. (At least in my cursory testing?) And Internet Archive can't cache the image portion of a fancier wax site, while, say, an Omeka page will get fully archived.
One option would be to create the non-IIIF images in the IIIF task as well, load
<img src="static_loc.jpg">
elements in the relevant slot, and then immediately delete those images with a little piece of Javascript.Problems:
window.stop
and then restart everything except the img src calls, but that increases the pain on pointThe text was updated successfully, but these errors were encountered: