Open danielweck opened 6 years ago
Note that RequireJS dynamically injects the following markup into the head
of index_RequireJS_no-optimize.html
:
<script type="text/javascript" charset="utf-8" async="" data-requirecontext="_" data-requiremodule="readium_shared_js/globalsSetup" src="../readium-js/readium-shared-js/js/globalsSetup.js"></script>
...
...
... (many more)
Note the async
attribute, and compare with the "hard-coded" includes in index_RequireJS_no-optimize.html
:
Note that the removal of Rangy does not affect this behaviour ( https://github.com/readium/readium-shared-js/issues/445 )
The above bug report is with Firefox. With Chrome (where this but does not exist), the RequireJS-injected markup looks slightly different, in the sense that the async
attribute has no value (equivalent to async="async"
), whereas in Firefox is seems to be async=""
(I'm not actually sure this makes any difference at all in the in-memory DOM, maybe this is just how markup is rendered in the debugger):
<script type="text/javascript" charset="utf-8" async="" data-requirecontext="_" data-requiremodule="readium_shared_js/globalsSetup" src="../readium-js/readium-shared-js/js/globalsSetup.js"></script>
Safari on MacOS works fine too (the async
attribute is reported by the Web Inspector / DOM debugger just as with Chrome). So this bug seems to only occur in Firefox.
@danielweck In the Firefox reader is not working not loading an epub file.
npm run http
=>