View Single Post
Old 06-03-2021, 09:08 AM   #26
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,475
Karma: 5703586
Join Date: Nov 2009
Device: many
That is exactly the same strange behaviour that I am seeing with Bibi and your test case.

I am scratching my head as to why it acts like that.

I took a look at the Bibi js code itself and all that 'allows-scripts-in-content' does is control whether Bibi's DOM strips out all script tags on load or not.

So something is a bit strange with Bibi but it is hard to track down given all of its code has been minimized, and all his code is done via Promises.

Them rewriting the DOM tree so much makes me worry about what else they are stripping out. There is a whole sanitizer.js extension for that.

Sorry I can not be more help here.


Quote:
Originally Posted by RbnJrg View Post
In principle, to add the en-us.js file via direct script tag is not neccesary (in fact, the ebook passes epubcheck without it). But I did what you said, and I added the "en-us.js" script tag and, it WORKED!

But the curious thing is that, after removing that tag, it continued working! I can't explain why that behaviour.

By the way, the plugins for three different e-readers were very nice additions. Many thanks for that.

Last edited by KevinH; 06-03-2021 at 09:10 AM.
KevinH is online now   Reply With Quote