| • Jaredzimmerman-WMF | |
| Dec 9 2014, 10:18 PM |
| F2914606: out-1.ogv | |
| Jan 29 2016, 6:42 PM |
| F20303: image_viewer_close_button.mov | |
| Dec 9 2014, 10:19 PM |
Upstream: https://secure.phabricator.com/T6916
Related upstream ticket (about OGG): https://secure.phabricator.com/T6674
Video files should be viewable on site, in browser rather than requiring the user to download. Videos are often used to show bugs, the current workflow to view them is too many steps.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | None | T141457 blog.wikimedia.org post on Phabricator improvements | |||
| Resolved | • mmodell | T137727 Write blog post highlighting recent Phabricator improvements | |||
| Resolved | Aklapper | T136213 Complete the round of Phabricator improvements funded by Wikimedia | |||
| Resolved | Aklapper | T75990 Ogv videos doesn't show any image on Phabricator (as "application/ogg" is listed under files.audio-mime-types by default) | |||
| Resolved | None | T78078 Videos cannot be viewed without downloading |
The video above has the mimetype "video/quicktime" and that is not listed under files.viewable-mime-types - actually, no video mimetypes are listed at all. And adding it won't fix that either (tried that locally).
See https://secure.phabricator.com/T6674#85975 for general upstream plans; I guess we'll have to wait for upstream here.
Confirming for F2914606: The HTTP 302 becomes a HTTP 206 and then becomes a HTTP 403.
Which might be a different problem.
I personally do not really think this is a good idea. This would encourage people to make videos. Well if we absolutely can't understand what's going on, videos might be useful in a bug report, 99% of the time they would just be annoying, and better served with a prose description, or a screenshot.
Videos do not make good bug reports.
Videos do not make good bug reports.
If we don't want videos, we should reject them. As long as uploading them is allowed, it's not responsible to trash the reporter's work.
Any medium can be abused, or used to communicate better. Videos don't make good bug reports but they don't make them necessarily bad either.
Currently animated gifs can be used, and I've been using them for reporting issues (e.g., T134854) or describing new design aspects such as transitions (e.g., T120067). I think that visual communication helped to make things clear in those cases.
While you can argue that animated gifs could lead to a Phabricator crowded of memes and other distracting gifs, that has not been the case in practice. I see no evidence to think that videos would be used much differently.
Unfortunately animated gifs fall short in many cases where more bandwidth is needed to communicate some ideas (e.g., a walkthrough of a prototype).
T75990 is resolved. Upstream https://secure.phabricator.com/T6916 still open to cover some more cases hence also keeping this downstream task open.
Not usually, but sometimes I've actually found them very useful. I don't think this would be visible enough to most reporters to cause us many problems.
Another fix to this if the video is over 4mb I think.
https://secure.phabricator.com/rP01862b8f23ac47ae14d464c6005262a3f43d3915
https://secure.phabricator.com/T6916 and https://secure.phabricator.com/T6674 are closed as resolved.
The video test case provided by @Nemo_bis now plays embedded / inline for me in Firefox 47 on this very Phabricator instance.
Closing this task as resolved.