RESOLVED FIXED 13348
Loading of non-existent resource 
https://bugs.webkit.org/show_bug.cgi?id=13348
Summary Loading of non-existent resource
Adam Treat
Reported 2007-04-13 14:57:21 PDT
Consider the following page: <html> <head> <script type="text/javascript"> function repaint() { main.document.open(); main.document.writeln('<html>'); main.document.writeln('<body>'); main.document.writeln('fubar'); main.document.writeln('</body>'); main.document.writeln('</html>'); main.document.close(); } </script> <body onLoad="repaint();"> <iframe name="main" src="http://www.webkit.org/does_not_exist.html"></iframe> </body> </html> What should webkit do with this scenario. Currently, the Qt port displays a blank iframe until the user clicks on it or interacts with it and then the repaint call is triggered and it displays 'fubar'. I checked on IRC and under Safari the page just loads and displays 'fubar'. Firefox has the same behavior, it just displays 'fubar' on load. Konqueror, on the other hand, displays a 'missing' error page in the iframe. Should I fix the Qt port to just display 'fubar' on load or is Konqueror correct?
Attachments
test case (427 bytes, text/html)
2007-07-19 06:08 PDT, Alexey Proskuryakov 		no flags
Details
test case (428 bytes, text/html)
2007-07-19 06:19 PDT, Alexey Proskuryakov 		no flags
Details
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.
Alexey Proskuryakov
Comment 1 2007-07-19 06:08:51 PDT
Created attachment 15581 [details] test case Same test as an attachment.
Alexey Proskuryakov
Comment 2 2007-07-19 06:19:10 PDT
Created attachment 15582 [details] test case Fixed to avoid cross-domain checks from killing the script.
Alexey Proskuryakov
Comment 3 2007-07-19 06:26:24 PDT
There doesn't seem to be any reason to differ from Firefox and to change the Mac version's behavior in this case IMHO. What is the iframe's src in Konqueror? Could it reset it to something that triggers cross-domain security checks, like maybe a local path?
Adam Treat
Comment 4 2009-01-11 07:38:12 PST
The Qt port now displays the same behavior as Safari.
Note You need to log in before you can comment on or make changes to this bug.