View Single Post
Old 11-14-2019, 07:51 PM   #8
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,621
Karma: 204624552
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
It's the svg code itself! Remove the svg tags and everything in between and the file starts behaving normally. Which leads me to believe this has everything to do the fixup for full-screen images that I suggested. Something with the "100vh" and "100vw" we inject in place of 100% for the width/height attributes is tripping up QWebEngineView for some reason.

Changing the height and width parameters of the svg from 100% to 99% will stop the replacement and allow the QWebEngineView to treat the file like xhtml again.

Weird. We'll clearly have to rethink that.

Last edited by DiapDealer; 11-14-2019 at 07:56 PM.
DiapDealer is offline   Reply With Quote