RESOLVED INVALID 56669
[Qt] QtWebKit rendering problem when maximizing and doing a back
https://bugs.webkit.org/show_bug.cgi?id=56669
Summary [Qt] QtWebKit rendering problem when maximizing and doing a back
Aparna Nandyal
Reported 2011-03-18 13:14:16 PDT
Preconditions - QtTestBrowser is not maximized Steps to reproduce: 1. From QtTestBrowser, go to google.com 2. Search for example meego - Page 1 3. Open a link, say first link from search page - Page 2 4. Maximize the window 5. Now press back button Expected - Page 1 content should now be displayed in entire browser Actual - There is an overlap of page 1 and page 2 content
Attachments
Patch for review (4.17 KB, patch)
2011-03-21 14:07 PDT, Aparna Nandyal
no flags
Patch v02 for review (4.24 KB, patch)
2011-03-21 14:41 PDT, Aparna Nandyal
benjamin: review-
Patch v03 with comments implemented (4.33 KB, patch)
2011-03-23 00:42 PDT, Aparna Nandyal
no flags
Benjamin Poulain
Comment 1 2011-03-18 13:47:32 PDT
Setting P1 since it is a regression. For reference: https://bugs.webkit.org/show_bug.cgi?id=51892
Aparna Nandyal
Comment 2 2011-03-21 14:07:17 PDT
Created attachment 86361 [details] Patch for review Bug is caused due to changes made in http://trac.webkit.org/changeset/79167 On resizing and going back, contentsResized() is not getting called. Before the above changeset, contentsResized was called from ScrollView::setFrameRect(). Now ScrollView::setBoundsSize makes the call to contentsResized. Changes made are similar to changes made in resize() of Widget.h.
Alexis Menard (darktears)
Comment 3 2011-03-21 14:15:57 PDT
Comment on attachment 86361 [details] Patch for review Look goods to me. It was related to this changes too : http://trac.webkit.org/changeset/79450
Alexis Menard (darktears)
Comment 4 2011-03-21 14:18:21 PDT
Perhaps you should put my name for the test just in case we have stability problems, so if needed it's possible to find the original author :).
Aparna Nandyal
Comment 5 2011-03-21 14:19:36 PDT
(In reply to comment #4) > Perhaps you should put my name for the test just in case we have stability problems, so if needed it's possible to find the original author :). I just left a message to you IRC, I was not sure how to add your name too as author :). Where should it go?
Aparna Nandyal
Comment 6 2011-03-21 14:41:24 PDT
Created attachment 86367 [details] Patch v02 for review Adding Alexis as author of the auto test.
Antonio Gomes
Comment 7 2011-03-21 17:39:25 PDT
Comment on attachment 86367 [details] Patch v02 for review View in context: https://bugs.webkit.org/attachment.cgi?id=86367&action=review Was it wrong in the original patch? no layout test catching it? Is it possible to test it through DRT? > Source/WebKit/qt/tests/qwebview/tst_qwebview.cpp:442 > +void tst_QWebView::rendering() this name is meaningless.
Benjamin Poulain
Comment 8 2011-03-22 06:19:09 PDT
Comment on attachment 86367 [details] Patch v02 for review View in context: https://bugs.webkit.org/attachment.cgi?id=86367&action=review No idea about the validity of change itself though, maybe Andreas... :) > Source/WebKit/qt/tests/qwebview/tst_qwebview.cpp:472 > + QApplication::processEvents(); Can't you just waitForSignal() on loadFinished()?
Andreas Kling
Comment 9 2011-03-22 08:08:52 PDT
Comment on attachment 86367 [details] Patch v02 for review View in context: https://bugs.webkit.org/attachment.cgi?id=86367&action=review > Source/WebCore/loader/FrameLoader.cpp:2196 > + view->setBoundsSize(IntSize(rect.width(), rect.height())); view->setBoundsSize(rect.size());
Aparna Nandyal
Comment 10 2011-03-23 00:42:39 PDT
Created attachment 86582 [details] Patch v03 with comments implemented 1. Renamed the function in test. 2. Corrected the code as per comments from Andreas. 3. Corrected the code in test 3. Could not add layout test (DRT) as window.resizeTo(w, h) is not happening in QtTestBrowser.
Alexis Menard (darktears)
Comment 11 2011-03-23 06:22:47 PDT
Comment on attachment 86582 [details] Patch v03 with comments implemented LGTM :D
Andreas Kling
Comment 12 2011-03-23 06:51:28 PDT
Comment on attachment 86582 [details] Patch v03 with comments implemented LGTM, too :)
WebKit Commit Bot
Comment 13 2011-03-23 08:54:46 PDT
Comment on attachment 86582 [details] Patch v03 with comments implemented Clearing flags on attachment: 86582 Committed r81775: <http://trac.webkit.org/changeset/81775>
WebKit Commit Bot
Comment 14 2011-03-23 08:54:51 PDT
All reviewed patches have been landed. Closing bug.
WebKit Review Bot
Comment 15 2011-03-23 11:28:05 PDT
http://trac.webkit.org/changeset/81775 might have broken GTK Linux 64-bit Debug
Laszlo Gombos
Comment 16 2011-05-21 14:39:14 PDT
Reopen as this test fails on Symbian and possible on other "small screen" platforms - (see http://build.webkit.sed.hu/builders/Qt%20Symbian%20ARMv5%20Release/builds/1156/steps/API%20tests/logs/stdio) FAIL! : tst_QWebView::renderingAfterMaxAndBack() Compared values are not the same Loc: [D:/w/qt-symbian-release/build/Source/WebKit/qt/tests/qwebview/tst_qwebview.cpp(504)] Perhaps the test should render smaller sized content - e.g. 50x50 instead of 1024x768. Disabling the scrollbars would be a good ideas as well (see http://trac.webkit.org/changeset/84332) CCd Yi who might be able to help with testing on Symbian.
Joel Parks
Comment 17 2011-06-27 13:31:24 PDT
(In reply to comment #16) > Reopen as this test fails on Symbian and possible on other "small screen" platforms - (see http://build.webkit.sed.hu/builders/Qt%20Symbian%20ARMv5%20Release/builds/1156/steps/API%20tests/logs/stdio) > > FAIL! : tst_QWebView::renderingAfterMaxAndBack() Compared values are not the same > Loc: [D:/w/qt-symbian-release/build/Source/WebKit/qt/tests/qwebview/tst_qwebview.cpp(504)] > > Perhaps the test should render smaller sized content - e.g. 50x50 instead of 1024x768. Disabling the scrollbars would be a good ideas as well (see http://trac.webkit.org/changeset/84332) > > CCd Yi who might be able to help with testing on Symbian. Still failing at build #1774 http://build.webkit.sed.hu/builders/Qt%20Symbian%20ARMv5%20Release/builds/1774/steps/API%20tests/logs/stdio But is this really a P1 error?
Jocelyn Turcotte
Comment 18 2014-02-03 03:17:23 PST
=== Bulk closing of Qt bugs === If you believe that this bug report is still relevant for a non-Qt port of webkit.org, please re-open it and remove [Qt] from the summary. If you believe that this is still an important QtWebKit bug, please fill a new report at https://bugreports.qt-project.org and add a link to this issue. See http://qt-project.org/wiki/ReportingBugsInQt for additional guidelines.
Note You need to log in before you can comment on or make changes to this bug.