Youtube and Vimeo videos not working in Readium

4 posts / 0 new
Last post


I've uploaded an epub file into Readium. This epub file consists of some slides with youtube/vimeo videos. These videos are working on chrome browser but not in Readium.

It gives a Cross domain error

"XMLHttpRequest cannot load No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin is therefore not allowed access."

youtube/vimeo is embeded in epub using iframe and when this epub is uploaded into readium, a scenario arises where we have a iframe within a iframe. In this case, Readium iframe becomes a parent of iframe used to embed youtube/vimeo video.
Cross domain issue arises.

Please provide the inputs, if any body has any idea regarding this issue. How this issue can be resolved?

Thank you.

Going off tangent a bit from the original question, my question is more philosophical. Is it really a good idea to embed "YouTube" video links in an eBook? What would be the status of such a book, say, 50 years from now? Of course JavaScript support is optional in EPUB3. However I think JavaScript is absolutely necessary for some types of books (animated books) but fetching videos externally at runtime to display in a book doesn't seem very portable to me.

Should EPUB support all of HTML5? Certain things that are great on web pages just look like bad taste in books.

Since the late 90s when people started using the Internet heavily, we started seeing hyperlinks being referenced in printed books. A lot of these links are now dead links and the books have not been revised. This problem reduces the value of the books and frustrates the users of such books. Still it is a minor problem compared to a situation where a digital book is filled with dead YouTube links, rendering it unusable in a matter of years. Embedding of external content, while giving power to the format, really should be confined to alternative uses of the format (i.e. for epub documents that represent something other than books). In making a book in the classical sense, any videos used should be packaged with the archive for portability and longevity.

Packaging a video for portability is a standard way in which an ePub should be packaged but on the contrary one can not deny the fact that ePub3 provides almost full support for HTML5 which could be leveraged in a constructive way thus not hampering the standard.Imagine a scenario of adding 100 videos to a book, this may result in adding lot of MB's to book size hence challenging portability.External links like YouTube/Vimeo videos have very less chances to become dead and are more prone to be changed via any ePub editor at any point of time therefore releasing a new version of book. It may be a troublesome process if we touch book content to alter 100 embedded videos.In present digital first era it is very uncertain to foresee the scenarios after 50 years.Readers/browsers may change to support new media formats and present formats may just become dead, however live streaming may have some chances to survive.It is all about the current need. As far as the problem statement of this forum topic is concerned, this is more of technical troubleshooting for solving the present real time problem.

Secondary menu