RESOLVED INVALID 39632
[Qt] The Search button on the Twitter top page is not rendering correctly on Windows 7.
https://bugs.webkit.org/show_bug.cgi?id=39632
Summary [Qt] The Search button on the Twitter top page is not rendering correctly on ...
Ryuichi KUBUKI
Reported 2010-05-24 17:56:09 PDT
Created attachment 56950 [details] Twitter screenshot The environment: Qt 4.7 Beta (VS2008 build), Windows 7 (Japanese) [How to Reproduce] 1. Run browser.exe of the Qt demos 2. Go to twitter.com [Expected Result] The search button is put at the right side of the input box. [Actual Result] The search button is put under the input box.
Attachments
Twitter screenshot (58.56 KB, image/png)
2010-05-24 17:56 PDT, Ryuichi KUBUKI
no flags
Sriram
Comment 1 2010-06-08 11:05:10 PDT
I was not able to reproduce this with QTestBrowser on uBuntu with webkit trunk on r60753. The search button shows up next to the input box. This doesnt seem to be a platform specific issue
Ryuichi KUBUKI
Comment 2 2010-06-08 15:30:32 PDT
(In reply to comment #1) > I was not able to reproduce this with QTestBrowser on uBuntu with webkit trunk on r60753. The search button shows up next to the input box. This doesnt seem to be a platform specific issue It doesn't happen on Windows XP either, but happens on Windows 7, hence the title of this bug. Did you mean you thought it's not Qt-specific?
Kent Hansen
Comment 3 2010-06-17 07:36:33 PDT
I can reproduce this with the browser demo in 4.7, but not with QtTestBrowser in trunk r61211.
Kent Hansen
Comment 4 2010-06-21 05:53:17 PDT
Could you test if QtWebKit in 4.6 has the same issue? If not, this is a regression and should be fixed for Qt 4.7 / QtWebKit 2.1. If it's not a regression, the fix will anyway be in the next minor release of Qt / QtWebKit, since this works in trunk already.
Kent Hansen
Comment 5 2010-06-21 05:53:51 PDT
(In reply to comment #4) > If not, this is a regression and should be fixed for Qt 4.7 / QtWebKit 2.1. That should say "QtWebKit 2.0"
Note You need to log in before you can comment on or make changes to this bug.