The link to "Download in Ogg Theora format" on http://www-trunk.stage.mozilla.com/en-US/firefox/beta/features/ (from inside the video player) renders http://videos.mozilla.org/firefox4beta/Firefox_4_beta.theora.ogv in the browser, rather than setting content-disposition:attachment.
This appears to be true of all Ogg Theora videos on videos.mozilla.org and not specific to this particular video.
The mp4 version does the same, and this is actually true across the whole site, so not specific to this page. In fact, the only way to set content-disposition: attachment is from apache on videos.m.o, so this can't really be fixed via mozilla.com code. There might be an apache trick we can play, where if ?download exists, apache will set that header, otherwise it won't. I'm not sure how that will interact with videos-cdn.m.n though. Oremj, is that something we could implement on videos.m.o and do you know if it would work well with videos-cdn? If that doesn't work, we can always say "right click and choose Save link as..." or something. Since this is a site-wide problem, I think it shouldn't block the 4.0b1 pages, stephend is that OK?
No longer blocks: 571647
Summary: Link to "Download in Ogg Theora format" for Firefox 4 beta video displays video inline, rather than prompting to download → Link to download ogg/mp4 videos displays video inline, rather than prompting to download
Alex: reading bug 501377 might help, but no, I don't think this is a blocker (not sure it's my call, even).
Nevermind; it doesn't really help, just says to change the text, sorry.
/me facepalms this is what happens when you have two sites, using the same code, in separate repositories.... the solution in that bug works for me.
Forgot about that. Wording on features page changed in r69992.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
Component: www.mozilla.org/firefox → www.mozilla.org
Product: Websites → Websites
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
You need to log in before you can comment on or make changes to this bug.