Create a static image fallback option for noscript users for frontend graph extension usage.
Description
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Open | Request | None | T274738 Archive the graphoid service and deploy repos | ||
Resolved | Clement_Goubert | T242855 Undeploy graphoid | |||
Resolved | Seddon | T255420 Provide static fallback for noscript users |
Event Timeline
This was based on feedback from the wikitech ambassadors list:
https://lists.wikimedia.org/pipermail/wikitech-ambassadors/2020-May/002300.html
Change 605561 had a related patch set uploaded (by Seddon; owner: Seddon):
[mediawiki/extensions/Graph@master] Bug:T255420 Create static image fallback option for noscript users.
Change 605561 merged by jenkins-bot:
[mediawiki/extensions/Graph@master] Bug:T255420 Create static image fallback option for noscript users.
As a random example of a proxied/no-script experience where this might appear, there is Apple's Dictionary app.
I'm sorry, is this task to provide like a static "no image available" type of image or rendering a static image as in, what Graphoid was doing? If the latter, then efforts here should go towards the RFC where I'm trying to push through a cleaner version of Graphoid to production: T249419
@Milimetric: This is more the former. It provides a static, user defined image fallback from commons in the event clientside rendering is unavailable, mainly in the event of noscript users