View Single Post
Old 03-02-2017, 01:10 PM   #12
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,809
Karma: 6000000
Join Date: Nov 2009
Device: many
I did find one interesting tidbit. If we run document.execCommand("styleWithCSS", "true") once BookView has been loaded up properly, it will force the internal webkit wiget to use inline styles to handle underlining, strike, subscript, superscript, etc.

That means that the code produced by BookView (although unsightly with all of those spans with inline styles flying around) would at least be technically correct for both epub2 and epub3.

My guess is this is why the strike bug has not been noticed and fixed by Qt previously as many users will have this set.

So that is at least an option.

KevinH
KevinH is offline   Reply With Quote