Please add an option to allow client side SVG rendering.
This epic is specifically about serving up SVGs that were uploaded to the File namespaces, as svg images, instead of PNG thumbnails.
Several challenges have been identified over the years that would be required to be solved for this to become a reality.
1. Fallback: Not all browsers support SVG, so we will need a fallback (This likely can be striken by now. By the time this gets deployed a fallback is likely no longer needed)
2. Size: Some SVGs are way too large to serve them up raw. A limit (for instance 100Kb maximum on the original size ) has to be defined as to what is acceptable to serve up to user agents, SVGs above that either need to be simplified or served up as PNG.
3. Feature: We support translations and these translations can be different than the user-agent language. This functionality should not be broken
4. Rendering: SVGs can contain text that is not converted to paths. This text depends on the fonts installed on the user-agent/browser. In order to preserve the intent of the uploader, it might be required to do on the fly conversion to paths or something to ensure that all users get consistent rendering of the SVG
5. Software adaptations for the above issues have to be implemented in the MediaWiki SVG handler
6. Similar adaptations for the above issues might have to be implemented in the WMF Thumbor service which renders the thumbnails for Wikimedia
7. The changes have to be behind a configuration flag, to assist with gradual rollout
8. The changes have to be regression tested
9. The changes have to be announced to the community
10. The change have to be rolled out and any feedback needs to be collected and follow up on.
**See Also**: {T10901}