View Single Post
Old 10-02-2018, 10:30 PM   #23
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,860
Karma: 6120478
Join Date: Nov 2009
Device: many
So something in Webkit has open that file and has not closed it. On Linux and Mac, all resources/images used by an xhtml page are read in and actually cached. You can even delete the resource/image files and until you flush the cache the xhtml page will look unchanged.

So somehow Webkit on Windows is not bothering to close a resource file (in this case a css file) after reading it into its cache or it is doing some kind of smart lazy loading. Not sure which. Either way this is a Qt Webkit bug that we either ignore or try to workaround in some way.

I just do not understand why the same permission bug does not happen due to Preview which is also a Webkit window.

In other words, why does BV cause this permission issue when CV with Preview does not?

Something is strange!
KevinH is online now   Reply With Quote