Quote:
Originally Posted by kovidgoyal
So, it happens all the time in browsers. It is unavoidable given that browsers load things asynchronously, as should be obvious to anyone that knows even a little bit about how browsers work. If you haven't seen it, it is because the sites you visit happen to have worked around it by hiding content till the asynchronous loading is complete, or the content is already in your browsers cache. Or you are blind.
Just as I already said I have worked around it in the calibre viewer as well, exactly by hiding content until loading is complete. And broken paragraphs when resizing windows happened in the old viewer as well and happen in any browser that is rendering multi-column content. Indeed, the viewer, both old and new is a goddamn browser.
|
Modern browsers do not show HTML without applying CSS. That would be a mess (I remember old browser sometimes did this). JavaScript is applied after page is fully loaded, that's true, but CSS not.
Your viewer is not as fast as modern browsers in rendering, so that's why loader is necessary until the page is fully rendered.
Try this: Set custom Unicode font (heavy font, I have Bookerly), take book with a lot of pure text (~200KB per chapter) and see youself what I'm talking about. I see garbled text/paragraphs for sometimes as much as 1 second.