Summary: | [Qt] Css is completely broken when compiling QtWebKit 2.0 against Qt 4.6 | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Jocelyn Turcotte <jturcotte> | ||||
Component: | CSS | Assignee: | QtWebKit Unassigned <webkit-qt-unassigned> | ||||
Status: | RESOLVED DUPLICATE | ||||||
Severity: | Critical | CC: | hausmann, kim.1.gronholm, noam | ||||
Priority: | P1 | Keywords: | Qt, QtTriaged | ||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | All | ||||||
OS: | All | ||||||
Bug Depends on: | |||||||
Bug Blocks: | 35784 | ||||||
Attachments: |
|
Description
Jocelyn Turcotte
2010-04-20 05:58:36 PDT
Created attachment 53804 [details]
Stack trace of the snow example crash
this == 0x0 when entering QGraphicsScene::update
Kim, Noam, this crash is interesting for you :) I was able to reproduce this. The issue is same than in https://bugs.webkit.org/show_bug.cgi?id=36755 Tested that changing back to Qt::QueuedConnection fixes also these pages. (In reply to comment #3) > I was able to reproduce this. The issue is same than in > https://bugs.webkit.org/show_bug.cgi?id=36755 > > Tested that changing back to Qt::QueuedConnection fixes also these pages. That's strange, given that there's no networking in the backtrace at all. Could it be that the QueuedConnection just hides the real bug? Sorry, my bad. I was concentrating on the messed up CSS since that's what the bug title states. The crashing in the snow example seems to be a separate issue and I'm unable to reproduce it on my Ubuntu system with Qt 4.6.2. At least for me it looks like it's totally unrelated to the broken CSS. All these problem seems to be fixed in the latest qtwebkit-2.0 branch. Resolving as duplicate of 36755 which is now fixed for the css loading issues. The crash seems to be fixed as well, as Simon suspect it might be the fact that accelerated compositing was wrongly enabled with QWebView. *** This bug has been marked as a duplicate of bug 36755 *** |