Last modified: 2014-10-08 18:12:41 UTC
Using the following code: [[File:Hmv-db2291-32-4807-2wx766.flac]] generates code with urls pointing to the flac file, but this should point to the ogg file (which is the version of the file which is adapted to the web).
Parsoid probably shouldn't need to know details of media rendering, which is potentially infinitely extensible. I would expect Parsoid to only deal with placeholders that actual media viewers get inserted into...
(In reply to comment #1) > Parsoid probably shouldn't need to know details of media rendering, which is > potentially infinitely extensible. > > I would expect Parsoid to only deal with placeholders that actual media > viewers > get inserted into... Is there an API that we can call to get the current core media rendering for things that are not simple images? In the worst case we could probably abuse action=parse. We have not given the desired semantic DOM structure for videos or sounds much thought yet. It would be tempting to use native video / audio html5 tags and let shims handle the fall-back for clients that don't support it.
I have some ideas for creating a cleaner interface for this sort of thing; I'll write up some notes...
Ok threw some quick notes up at https://www.mediawiki.org/wiki/User:Brion_VIBBER/Media_rendering_encapsulation
(In reply to comment #4) > Ok threw some quick notes up at > https://www.mediawiki.org/wiki/User:Brion_VIBBER/ > Media_rendering_encapsulation @Brion: Images are handled according to https://www.mediawiki.org/wiki/Parsoid/MediaWiki_DOM_spec#Images For video / audio, my initial instinct would be to spec something similar using video and audio tags in a way that works directly on modern browsers, and let shims handle legacy clients.
Yeah I started adding markup notes along those lines -- I'm a bit unclear on where all the media parameters end up though; particularly width and height *must* be retained and I think there may be some additional custom properties... images may include a page specifier (for DjVu, PDF, etc), and TimedMediaHandler items may have things like a start time. I can certainly envision additional custom parameters on other types -- a 3d model viewer might have initial camera parameters or lighting setup, an animation may want to indicate that it should autoplay or loop (like animated GIFs do) as an alternative to non-autoplaying audio/video behavior. How do we pass those through if Parsoid and VE don't know about them specifically?
