30788 2009-10-26 13:54:12 -0700 HistoryController does not handle some opaque URLs correctly 2016-02-05 03:20:52 -0800 1 1 1 Unclassified WebKit History 528+ (Nightly build) PC Linux RESOLVED FIXED P2 Normal --- 30724 0 alex webkit-unassigned ap sam xan.lopez oldest_to_newest 157905 0 41890 alex 2009-10-26 13:54:12 -0700 Created attachment 41890 Test reproducing the problem This bug comes from the bug 30724, in the comment 2 it is explained the situation that is currently causing problems with the gtk+ DRT when testing opaque-base-url.html, but that it seems it could be reproduced with the test attached to this bug in other platforms. I've added the main authors of the opaque-base-url.html test to the CC, thanks in advance for the help. The test tries to reproduce the error in other platforms, not just gtk+, trying to do a similar action done in the gtk+ DRT. Basically this kind of opaque urls are causing problems when the state is saved in the HistoryController, it is checked if that item is in current document and that tries to create a URL using an opaque URL that hits the checkEncodedString assertion about the first character in an url. I guess even this being an invalid URL (we should remove that from the opaque test then) we should handle the situation without reaching the assertion. Can someone check the test with other platforms and see if the problem is there? I guess the patch should control the current document condition in case of this kind of opaque URLs, not sure if just avoiding saving or setting as current because there is not URL. 165356 1 alex 2009-11-20 10:45:40 -0800 (In reply to comment #0) > Created an attachment (id=41890) [details] > Test reproducing the problem > > This bug comes from the bug 30724, in the comment 2 it is explained the > situation that is currently causing problems with the gtk+ DRT when testing > opaque-base-url.html, but that it seems it could be reproduced with the test > attached to this bug in other platforms. I've added the main authors of the > opaque-base-url.html test to the CC, thanks in advance for the help. > The html code is this, I'll try to check the assertion: <script> if (window.layoutTestController) { layoutTestController.dumpAsText(); layoutTestController.queueReload(); } </script> <iframe frameborder=0 src="data:text/html,<iframe frameborder=0 src='<p>FAILURE</p>' width=10 height=10></iframe>"></iframe> 1162368 2 alex 2016-02-05 03:20:52 -0800 The test is nowadays passing, closing the bug. 41890 2009-10-26 13:54:12 -0700 2009-10-26 13:54:12 -0700 Test reproducing the problem reload-opaque-url.html text/html 258 alex CjxzY3JpcHQ+CmlmICh3aW5kb3cubGF5b3V0VGVzdENvbnRyb2xsZXIpIHsKICBsYXlvdXRUZXN0 Q29udHJvbGxlci5kdW1wQXNUZXh0KCk7CiAgbGF5b3V0VGVzdENvbnRyb2xsZXIucXVldWVSZWxv YWQoKTsKfQo8L3NjcmlwdD4KCjxpZnJhbWUgZnJhbWVib3JkZXI9MCBzcmM9ImRhdGE6dGV4dC9o dG1sLDxpZnJhbWUgZnJhbWVib3JkZXI9MCBzcmM9JzxwPkZBSUxVUkU8L3A+JyB3aWR0aD0xMCBo ZWlnaHQ9MTA+PC9pZnJhbWU+Ij48L2lmcmFtZT4K