[Webkit-unassigned] [Bug 82960] New: [Qt][WK2] Seg fault when property binding to experimental.contentY
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon Apr 2 15:50:37 PDT 2012
https://bugs.webkit.org/show_bug.cgi?id=82960
Summary: [Qt][WK2] Seg fault when property binding to
experimental.contentY
Product: WebKit
Version: 528+ (Nightly build)
Platform: Unspecified
OS/Version: Unspecified
Status: NEW
Severity: Normal
Priority: P2
Component: WebKit Qt
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: rafael.lobo at openbossa.org
It's easy to reproduce with MiniBrowser code. On BrowserWindow.qml, do the following:
WebView {
id: webView
+ property bool scrolledUpToBoundary: webView.experimental.contentY < 0
+ onScrolledUpToBoundaryChanged: console.log('Scrolled up?' + scrolledUpToBoundary)
It is expected that we can lookup to contentY changes and properly bind the properties here. The comparison webView.experimental.contentY < 0 is causing the seg fault. If instead of this you only work inside experimental.onContentYChanged and print the new value, it works. So you can just force updates to "scrollUpToBoundary" this way inside experimental, but I believe we should be able to do the other way around. Here's an example of the workaround:
+ property bool scrolledUpToBoundary: false
+ experimental {
+ onContentYChanged: webView.scrolledUpToBoundary = webView.experimental.contentY < 0
+ }
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list