Extract out PopcornEditor and point to remote host

RESOLVED INVALID

Status

Webtools
Air Mozilla
RESOLVED INVALID
2 years ago
2 years ago

People

(Reporter: peterbe, Assigned: nolski)

Tracking

Trunk
Dependency tree / graph

Firefox Tracking Flags

(firefox42 affected)

Details

(Reporter)

Description

2 years ago
We currently have https://github.com/mozilla/airmozilla/tree/master/airmozilla/popcorn/static/popcorn/PopcornEditor
 in our repo and this code has been moved to https://github.com/mozilla/PopcornEditor instead. 

https://bugzilla.mozilla.org/show_bug.cgi?id=1192284 is about publishing those files via S3. 

We should 1) `git rm -r` the files out of our repo and 2) change the iframe URL to whatever #1192284 decides is the full host name.
(Reporter)

Comment 1

2 years ago
Mike, did you ever try with the new cloudfront URL?
(Reporter)

Comment 2

2 years ago
Hi Mike, 
Any chance you can help me with this one? I'm refactoring the static assets in airmozilla and I would love to be able to rip out all those Popcorn .css and .js etc. and just point to the S3 URL. 

For example, I notice that http://org.mozilla.air.popcorneditor.s3-website-us-east-1.amazonaws.com/ works. 

So, instead of https://github.com/mozilla/airmozilla/blob/master/airmozilla/popcorn/static/popcorn/PopcornEditor/css/transitions.css we can use
http://org.mozilla.air.popcorneditor.s3-website-us-east-1.amazonaws.com/PopcornEditor/css/transitions.css

What I did was to try to replace this https://github.com/mozilla/airmozilla/blob/1ef50c9f654d71d0636d39248c281cb8ad9361f9/airmozilla/popcorn/templates/popcorn/editor.html#L14
with <script src="http://org.mozilla.air.popcorneditor.s3-website-us-east-1.amazonaws.com/PopcornEditor/src/PopcornEditor.js></script>

But it's causing HTTPS mixed content errors. I'll ping lonnen about that. 
If you click to ignore the HTTPS mixed content errors it seems to load but at the end you get:
`TypeError: data.data.media.clipData is undefined`
(Reporter)

Updated

2 years ago
Depends on: 1220922
(Reporter)

Comment 3

2 years ago
It has been moved out but there are other errors about frames and DOMWindow.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → INVALID
(Reporter)

Comment 4

2 years ago
Closing because we just don't care enough to fix it since it's not working well and not being used at all.
You need to log in before you can comment on or make changes to this bug.