14171 2007-06-15 09:33:36 -0700 DOM not always available in didFinishLoadForFrame if multiple WebViews are busy loading (Colloquy doesn't display chat messages) 2016-09-20 09:51:57 -0700 1 1 1 Unclassified WebKit New Bugs 523.x (Safari 3) Mac OS X 10.4 ASSIGNED http://colloquy.info/project/ticket/576 InRadar P2 Normal --- 1 alex webkit-unassigned ap cdumez dev+webkit edcrfv ismail jeff pnasrat tofu.linden oldest_to_newest 7428 0 alex 2007-06-15 09:33:36 -0700 Sometimes Colloquy's webviews are just blank when loading (= when joining a chat room). And also this problem is appearing a lot more often (not all the time though) for everyone with the Safari 3 beta than with Tiger's original WebKit. Colloquy's trac ticket on this bug is in the URL field. 7344 1 beidson 2007-06-16 09:22:22 -0700 a workaround, in the meantime, is to type "/reload style" in one of these blank webviews. 4562 2 mrowe 2007-07-17 00:47:17 -0700 A workaround was landed in Colloquy's SVN in r3708. It mentions that there is likely something that needs fixed in WebKit, but doesn't provide any specifics... Does anyone know what the issue is here? 4500 3 timothy 2007-07-17 11:23:17 -0700 I am working on the WebKit issue. 4464 4 timothy 2007-07-17 16:02:32 -0700 The issue here is that Colloquy is trying to access the DOM from the didFinishLoadForFrame: delegate call. In cases where there are many WebViews loading at once, the HTML parser and tokenizer doesn't finish making the DOM until after didFinishLoadForFrame: is called. This design has always been the case in WebKit. It is never guaranteed that the DOM will be ready when didFinishLoadForFrame is called. Colloquy does a workaround and will release an update sometime. We should rethink this API and decide what didFinishLoadForFrame really means and make that clear in the API docs also. The attached patch almost fixes this completely but it broke the fast/dom/Document/document-reopen.html layout test. This test never closes the document, so with this patch didFinishLoadForFrame never fires. We need to rework the loader to fire the didFinishLoadForFrame when the main resource and sub-resource loads finish and the parser is done. But this test re-opens the document and makes the page seem like it never finishes. The explicit document.open with no document.close should not affect this delegate call. 4461 5 timothy 2007-07-17 16:03:16 -0700 <rdar://problem/5036833> 4460 6 15556 timothy 2007-07-17 16:03:48 -0700 Created attachment 15556 Almost working patch 15556 2007-07-17 16:03:48 -0700 2010-06-10 15:42:20 -0700 Almost working patch almost.patch text/plain 516 timothy SW5kZXg6IGxvYWRlci9GcmFtZUxvYWRlci5jcHAKPT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PQotLS0gbG9hZGVyL0ZyYW1l TG9hZGVyLmNwcCAgICAgIChyZXZpc2lvbiAyNDM2OSkKKysrIGxvYWRlci9GcmFtZUxvYWRlci5j cHAgICAgICAod29ya2luZyBjb3B5KQpAQCAtMjc4Nyw3ICsyNzg3LDcgQEAKICAgICAgICAgCiAg ICAgICAgIGNhc2UgRnJhbWVTdGF0ZUNvbW1pdHRlZFBhZ2U6IHsKICAgICAgICAgICAgIERvY3Vt ZW50TG9hZGVyKiBkbCA9IG1fZG9jdW1lbnRMb2FkZXIuZ2V0KCk7ICAgICAgICAgICAgCi0gICAg ICAgICAgICBpZiAoIWRsIHx8IGRsLT5pc0xvYWRpbmdJbkFQSVNlbnNlKCkpCisgICAgICAgICAg ICBpZiAoIWRsIHx8IGRsLT5pc0xvYWRpbmdJbkFQSVNlbnNlKCkgfHwgIW1faXNDb21wbGV0ZSkK ICAgICAgICAgICAgICAgICByZXR1cm47CiAKICAgICAgICAgICAgIG1hcmtMb2FkQ29tcGxldGUo KTsK