RESOLVED FIXED 40292
REGRESSION (r60742-r60820): Frame pages don't render in Frameset
https://bugs.webkit.org/show_bug.cgi?id=40292
Summary REGRESSION (r60742-r60820): Frame pages don't render in Frameset
Kevin M. Dean
Reported 2010-06-08 04:58:12 PDT
The pages contained in this frameset just don't render. They just stay blank white. Viewing source shows the code is there. The frameset itself renders, just not the linked content.
Attachments
Alexey Proskuryakov
Comment 1 2010-06-08 12:45:37 PDT
See also: bug 40299.
Alexey Proskuryakov
Comment 2 2010-06-08 14:39:02 PDT
I'm actually getting a crash on this URL with r60820 on an Intel Mac with Mac OS X 10.5.8. Thread 0 Crashed: 0 dyld 0x8fe18c02 misaligned_stack_error + 0 1 com.apple.WebKit 0x00309a9c -[WebFrame(WebInternal) _getVisibleRect:] + 124 2 com.apple.WebKit 0x0031c430 -[WebFrameView visibleRect] + 80 3 com.apple.WebCore 0x01d6d5ca WebCore::Widget::setFrameRect(WebCore::IntRect const&) + 218 4 com.apple.WebCore 0x01c12ba9 WebCore::ScrollView::setFrameRect(WebCore::IntRect const&) + 73 5 com.apple.WebCore 0x01bd1269 WebCore::RenderWidget::setWidgetGeometry(WebCore::IntRect const&) + 297 6 com.apple.WebCore 0x01bd14a7 WebCore::RenderWidget::updateWidgetPosition() + 391
Adam Barth
Comment 3 2010-06-08 14:46:57 PDT
I can't reproduce with a Debug build of http://svn.webkit.org/repository/webkit/trunk@60827
Alexey Proskuryakov
Comment 4 2010-06-08 14:55:34 PDT
I can reproduce the blank frame problem on Mac OS X 10.6 with Safari 5 installed, but ToT seems to work fine.
Adam Barth
Comment 5 2010-06-08 15:05:40 PDT
I should say I'm using 10.6 w/ Safari 5
Alexey Proskuryakov
Comment 6 2010-06-08 15:12:07 PDT
This was broken in r60820, and fixed in r60821. Just inconsistent settings between WebCore and WebKit projects.
Alexey Proskuryakov
Comment 7 2010-06-08 15:12:23 PDT
*** Bug 40299 has been marked as a duplicate of this bug. ***
Mark Rowe (bdash)
Comment 8 2010-06-08 15:19:44 PDT
I’m building a new nightly now. It should be up in an hour or two.
Note You need to log in before you can comment on or make changes to this bug.