RESOLVED INVALID 61941
[Qt] LayoutTests/fast/dom/Window/new-window-opener.html failed
https://bugs.webkit.org/show_bug.cgi?id=61941
Summary [Qt] LayoutTests/fast/dom/Window/new-window-opener.html failed
qi
Reported 2011-06-02 10:47:39 PDT
Need implement window.scrollbars.visible
Attachments
patch (6.14 KB, patch)
2011-06-02 10:55 PDT, qi
hausmann: review-
hausmann: commit-queue-
qi
Comment 1 2011-06-02 10:55:33 PDT
Antonio Gomes
Comment 2 2011-06-02 13:48:50 PDT
Comment on attachment 95775 [details] patch View in context: https://bugs.webkit.org/attachment.cgi?id=95775&action=review > Source/WebKit/qt/WebCoreSupport/ChromeClientQt.cpp:268 > + emit m_webPage->scrollBarVisibilityChangeRequested(visible); how does this work with set scrollbar policy we have in qwebsettings API?
qi
Comment 3 2011-06-03 05:51:48 PDT
My implementation followed the other similar function like change toolBar and menuBar visibility. I think here we just issue a event instead of changing the setting because we want browser ui has a ability to change the toolBar or scrollBar visibility (this request come from javascript), but browser also can ignore this event.
Alexis Menard (darktears)
Comment 4 2011-06-28 10:49:59 PDT
Comment on attachment 95775 [details] patch View in context: https://bugs.webkit.org/attachment.cgi?id=95775&action=review >> Source/WebKit/qt/WebCoreSupport/ChromeClientQt.cpp:268 >> + emit m_webPage->scrollBarVisibilityChangeRequested(visible); > > how does this work with set scrollbar policy we have in qwebsettings API? and the normal scrollbar policy of a QWidget? This API only meant to be used on QGraphicsWebView?
Robert Hogan
Comment 5 2011-08-05 17:50:50 PDT
Comment on attachment 95775 [details] patch View in context: https://bugs.webkit.org/attachment.cgi?id=95775&action=review > Source/WebKit/qt/WebCoreSupport/ChromeClientQt.cpp:275 > + return scrollBarVisible; Shouldn't ChromeClientQt report if the client's scrollbar is actually visible or not rather than just assume it?
Simon Hausmann
Comment 6 2011-11-01 14:31:41 PDT
Comment on attachment 95775 [details] patch I agree with the other folks. It sounds like the implementation of these two functions in ChromeClientQt should use FrameView's setCanHaveScrollbars and canHaveScrollbars. Check out the windows port for inspiration :) I don't think new API is required.
Jocelyn Turcotte
Comment 7 2014-02-03 03:17:53 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.