[Bug 62270] Support video and audio content
https://bugzilla.wikimedia.org/show_bug.cgi?id=62270 --- Comment #7 from Erik Bernhardson ebernhard...@wikimedia.org --- currently flow is storing the html content and not migrating it forward(that is an independent bug we need to fix). Personally due to this i would rather wait for a more stable DOM spec. -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 62270] Support video and audio content
https://bugzilla.wikimedia.org/show_bug.cgi?id=62270 Matthew Flaschen mflasc...@wikimedia.org changed: What|Removed |Added CC||mflasc...@wikimedia.org See Also||https://bugzilla.wikimedia. ||org/show_bug.cgi?id=72912 -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 62270] Support video and audio content
https://bugzilla.wikimedia.org/show_bug.cgi?id=62270 --- Comment #6 from C. Scott Ananian canan...@wikimedia.org --- S -- this wasn't on the current quarter's roadmap. How high of a priority is it? We should try to coordinate a schedule between our teams. Full audio/video support will probably take a bit of effort to nail down. Is flow interested in starting to work with a rough first draft, with the caveat that our DOM spec could change and break things as we nail down more details of obscure audio/video parameters (there are a lot of them, IIRC)? Or would you rather wait until we've got a reasonable test suite and decent options coverage and are more confident our DOM spec is on the right track? -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 62270] Support video and audio content
https://bugzilla.wikimedia.org/show_bug.cgi?id=62270 Arlo Breault abrea...@wikimedia.org changed: What|Removed |Added CC||abrea...@wikimedia.org Assignee|gwi...@wikimedia.org|parsoid-t...@wikimedia.org -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 62270] Support video and audio content
https://bugzilla.wikimedia.org/show_bug.cgi?id=62270 sp...@wikimedia.org changed: What|Removed |Added Severity|normal |major --- Comment #5 from sp...@wikimedia.org --- Flow would like this to work, embedding video and audio in Flow results in https://www.mediawiki.org/wiki/Topic:S52i2un1zblzd8s8#flow-post-s5fley5jhc8a8pub img links to the raw video and audio files that the browser renders as a broken image, hence raising the severity of this. In regular pages ogg and webm appear as audio or video tags within div class=mediaContainer, even with JavaScript disabled. -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 62270] Support video and audio content
https://bugzilla.wikimedia.org/show_bug.cgi?id=62270 Gabriel Wicke gwi...@wikimedia.org changed: What|Removed |Added Blocks||61769 -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 62270] Support video and audio content
https://bugzilla.wikimedia.org/show_bug.cgi?id=62270 --- Comment #1 from Gabriel Wicke gwi...@wikimedia.org --- There is a videoinfo API end point that provides a mediatype and a link to the full-size resource, which we can set in a source tag inside video or audio. It also seems to support everything we currently get from imageinfo, so I guess we can just switch to using that. http://en.wikipedia.org/w/api.php?action=queryprop=videoinfotitles=File:Wiki.pngformat=jsonviprop=url|mediatype There is also prop=transcodestatus, which returns the list of transcodes for a video [1]. This should be used by the client as the list of transcodes changes over time (after upload, when new sizes are added). It currently also only seems to work locally, so the API request for a video on commons needs to go to commons [2]. I guess that could be fixed in the API in the longer term. The current resource attribute is always a relative link, which makes it somewhat hard for a client to discover that they'll need to contact commons. Maybe this can be worked around client-side though by a) sending the API request to both commons and the local wikis, or b) fixing prop=transcodestatus to always work in the local wiki. In a perfect world all our media was on commons anyway so we could just use a single API all the time. [1]: http://commons.wikimedia.org/w/api.php?action=queryprop=transcodestatustitles=File:Sparkler_359-fps_Slow-Motion.webmformat=json [2]: http://en.wikipedia.org/w/api.php?action=queryprop=transcodestatustitles=File:Sparkler_359-fps_Slow-Motion.webmformat=json -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 62270] Support video and audio content
https://bugzilla.wikimedia.org/show_bug.cgi?id=62270 --- Comment #2 from Brion Vibber br...@wikimedia.org --- Note you can get the transcodes from prop=videoinfo on the local wiki using the 'derivatives' key: http://en.wikipedia.org/w/api.php?action=queryprop=videoinfotitles=File:Sparkler_359-fps_Slow-Motion.webmformat=jsonviprop=url|mediatype|derivatives http://en.wikipedia.org/w/api.php?action=queryprop=videoinfotitles=File:Zh-xi%C3%A8xie.oggformat=jsonviprop=url|mediatype|derivatives Be warned there is an inconsistency which causes some numeric entries to appear as strings in the JSON output (bug 55742 -- I have an old patch for it but nobody's got round to reviewing it, we should probably poke it). -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 62270] Support video and audio content
https://bugzilla.wikimedia.org/show_bug.cgi?id=62270 --- Comment #3 from Brion Vibber br...@wikimedia.org --- See also some old notes I made: https://www.mediawiki.org/wiki/User:Brion_VIBBER/Media_rendering_encapsulation -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 62270] Support video and audio content
https://bugzilla.wikimedia.org/show_bug.cgi?id=62270 --- Comment #4 from Gabriel Wicke gwi...@wikimedia.org --- (In reply to Brion Vibber from comment #2) Note you can get the transcodes from prop=videoinfo on the local wiki using the 'derivatives' key: Ahh, nice! That solves the resource issue, so we can continue to use relative links in there. -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 62270] Support video and audio content
https://bugzilla.wikimedia.org/show_bug.cgi?id=62270 Gabriel Wicke gwi...@wikimedia.org changed: What|Removed |Added Priority|Unprioritized |Normal -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 62270] Support video and audio content
https://bugzilla.wikimedia.org/show_bug.cgi?id=62270 Gabriel Wicke gwi...@wikimedia.org changed: What|Removed |Added Blocks||54844 -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
