Bug 61941 - [Qt] LayoutTests/fast/dom/Window/new-window-opener.html failed
Summary: [Qt] LayoutTests/fast/dom/Window/new-window-opener.html failed
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKit API (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC Linux
: P2 Normal
Assignee: qi
URL:
Keywords: Qt
Depends on:
Blocks:
 
Reported: 2011-06-02 10:47 PDT by qi
Modified: 2014-02-03 03:17 PST (History)
3 users (show)

See Also:


Attachments
patch (6.14 KB, patch)
2011-06-02 10:55 PDT, qi
hausmann: review-
hausmann: commit-queue-
Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description qi 2011-06-02 10:47:39 PDT
Need implement window.scrollbars.visible
Comment 1 qi 2011-06-02 10:55:33 PDT
Created attachment 95775 [details]
patch
Comment 2 Antonio Gomes 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?
Comment 3 qi 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.
Comment 4 Alexis Menard (darktears) 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?
Comment 5 Robert Hogan 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?
Comment 6 Simon Hausmann 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.
Comment 7 Jocelyn Turcotte 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.