Closed Bug 748035 Opened 12 years ago Closed 11 years ago

Broken path to .mp4 version of video on Get Involved page

Categories

(www.mozilla.org :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: Terry.F1Com, Unassigned)

References

()

Details

From here:  http://www.mozilla.org/en-US/contribute/

The source contains two forward slashes before "http" which need to be removed.

<source src="//http://videos-cdn.mozilla.net/brand/Mozilla_Firefox_Manifesto_v0.2_640.mp4" type="video/mp4" />
I just made this edit to fix the path and submitted the following pull request

https://github.com/davidwboswell/bedrock/commit/d97eb5f574c3740727048f8f444f6a7195ce18a9

CC'ing Mike, James and Steven for next steps.
Summary: Code correction to prevent failure of video playback → Broken path to .mp4 version of video on Get Involved page
FWIW, I tried testing and couldn't get the video to play on Safari -- I imagine that's related to this.
Looks good, I actually remember fixing this before but it might have gotten lost on a branch somewhere? Weird.

David, can you submit a pull request with that fix?
Oh, I see you already did.
Commits pushed to dev at https://github.com/mozilla/bedrock

https://github.com/mozilla/bedrock/commit/d97eb5f574c3740727048f8f444f6a7195ce18a9
Fixing path to .mp4 version of video -- bug 748035

https://github.com/mozilla/bedrock/commit/05034c4b0fdb25ce00a38998c442e71de91ddcd2
Merge pull request #69 from davidwboswell/patch-4

Fixing path to .mp4 version of video -- bug 748035
(In reply to David Boswell from comment #2)
> FWIW, I tried testing and couldn't get the video to play on Safari -- I
> imagine that's related to this.

To follow up on this, I tried testing the page on stage with Safari and the video still wouldn't load.  Maybe related to another issue.
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
This video isn't on this page any more.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.