News for hackers. Stuff that matters.
Re:Show HN: A visual HTML5 animation editor in your browser by vram22 on Friday March 07, 2014 @02:08PM (#7362069)
Thanks for the fast response. Will write the post and update the comment here with the link to it.

BTW, typo in your embed code: missing an "http:" in the value of the src attribute. Works after I add that, not without it.

Re:Show HN: A visual HTML5 animation editor in your browser by carizan on Friday March 07, 2014 @03:04PM (#7362420)
Strange about the embed code - that's how Vimeo provides it, so it's weird that it didn't work for you, but great that you managed to make it work in the end! Looking forward to reading the post :)
Re:Show HN: A visual HTML5 animation editor in your browser by vram22 on Friday March 07, 2014 @03:27PM (#7362543)
Re:Show HN: A visual HTML5 animation editor in your browser by carizan on Friday March 07, 2014 @03:34PM (#7362572)
Cool, thanks so much for writing about us :)
Re:Show HN: A visual HTML5 animation editor in your browser by vram22 on Friday March 07, 2014 @04:03PM (#7362723)
If not confidential, a blog post about the tech used would be interesting.
Re:Show HN: A visual HTML5 animation editor in your browser by carizan on Friday March 07, 2014 @04:28PM (#7362845)
It's already in the works, actually! We'll post it here on HN pretty soon.
Re:Show HN: A visual HTML5 animation editor in your browser by vram22 on Friday March 07, 2014 @03:54PM (#7362675)
You're welcome.
Re:Show HN: A visual HTML5 animation editor in your browser by jrand0m on Friday March 07, 2014 @03:50PM (#7362648)
it is not an issue. your browser will use protocol(http or https) it used to load page where you have embedded the video.
Re:Show HN: A visual HTML5 animation editor in your browser by vram22 on Friday March 07, 2014 @03:57PM (#7362691)
>it is not an issue.

Was an issue for me, otherwise I would not have said so, obviously. See my above comment where I said "not without it". Also, I'm aware of this:

http://jugad2.blogspot.in/2014/03/the-protocol-relative-url-...

So it may have been some other issue, but was an issue, for sure.