Dave Cramer
Dave Cramer
> It was put in at least in part for security reasons, as I recall, but perhaps there's a case to allow specific external references outside of HTML files. Definitely...
> First, the scope of EPUB A11Y 1.1 is the accessibility and discoverability of EPUB Publications. Humans are outside the scope. The spec is written by humans, for human content...
Made a very minimal sample EPUB with an iframe pointing to an external website, and tried it with some reading systems: 1. iBooks: failed 2. Azardi: worked 3. ADE 3.0:...
CG resolved to defer this to the next version of EPUB. The implications for the user experience, security, IP, etc. are profound. We need to get all our 🦆s in...
@mattgarrish see #252. I think we have some contradictory language in our specs :) [minimal-epub-30-iframe.zip](https://github.com/w3c/publ-epub-revision/files/2167668/minimal-epub-30-iframe.zip) (GitHub doesn't allow EPUBs as attachements; changed extension to ZIP)
Looks like epubcheck is wrong here?
Deleted my example above. It appears to be a bug in epubcheck, and confusion between "foreign" and "remote."
Filed a bug on epubcheck https://github.com/IDPF/epubcheck/issues/852 This is both an interesting hack, and a possible way forward. In general EPUB uses fallbacks when content *might* not be available to a...
> This will not work with HTML content (not well-formed) when it is allowed in EPUB4. I did find [this](https://github.com/dontcallmedom/saxon-html5) which might allow Saxon to parse HTML5.
I'm never happy when I can't use Saxon. Good luck!