Blank page as a result of using IFrames?
-
Hi,
I am using Qt WebKit 5.212.0 alpha4 in my application and I am getting a blank page when trying to load https://identifiers.org/.
I build Qt WebKit as a CMake external project, so I thought that I might have done something wrong and therefore decided to build Qt WebKit from scratch.
From there, I tried to load https://identifiers.org/ using both
MiniBrowserandQtTestBrowser, and sure enough I am also getting a blank page. (Actually, I can see the website's message about cookies, but nothing else.)I have contacted the people behind that website, but they don't know anything about Qt WebKit, so they can't really help. Fair enough.
However, they told me that their website uses IFrames (through a third-party library) and were therefore wondering whether that couldn't be the cause of the problem?
For what it is worth, I have (using Google Chrome) saved https://identifiers.org/ as a complete web page (i.e. including the JavaScript, CSS, etc. files) and loaded that page locally in both
MiniBrowserandQtTestBrowserand it's all working fine.So, would anyone have any ideas as what is going wrong here?
Thanks in advance and cheers, Alan.
-
@Konstantin-Tokarev, you wouldn't have any ideas about this one by any chance?
-
It's a bug or non-conformant behavior in old WebKit. Dev branch doesn't expose it, but it has other bug which doesn't allow correct rendering of page yet.
-
@Konstantin-Tokarev said in Blank page as a result of using IFrames?:
It's a bug or non-conformant behavior in old WebKit. Dev branch doesn't expose it, but it has other bug which doesn't allow correct rendering of page yet.
Argh, I was afraid it might be something like that. 😕 What would you recommend, if anything?
-
@Konstantin-Tokarev, I have been working on switching to Qt WebEngine, but suffice to say that I am not at all impressed. In other words, I would really like to stick to QtWebKit, if at all possible.
You said that my issue with QtWebKit (i.e. https://identifiers.org/ renders a blank page) is due to "a bug or non-conformant behavior in old WebKit". I am not quite sure what you mean by "old" here. Am I to understand that there are different versions of WebKit?
All I know is that https://identifiers.org/ works fine in Safari. So, what is the difference between the version of WebKit used in Safari and the one used in QtWebKit? Are those not the same? If not, why not?
-
So, what is the difference between the version of WebKit used in Safari and the one used in QtWebKit. Are those not the same? If not, why not?
QtWebKit 5.212.x is based on old WebKit branch from 2016 with occasional backports of fixes and features. Work on updating is still ongoing.
-
So, what is the difference between the version of WebKit used in Safari and the one used in QtWebKit. Are those not the same? If not, why not?
QtWebKit 5.212.x is based on old WebKit branch from 2016 with occasional backports of fixes and features. Work on updating is still ongoing.
@Konstantin-Tokarev said in Blank page as a result of using IFrames?:
QtWebKit 5.212.x is based on old WebKit branch from 2016 with occasional backports of fixes and features. Work on updating is still ongoing.
Ok, that explains a lot. Any ETA regarding the new WebKit branch by any chance?