82960 2012-04-02 15:50:38 -0700 [Qt][WK2] Seg fault when property binding to experimental.contentY 2012-05-22 04:46:18 -0700 1 1 1 Unclassified WebKit WebKit Qt 528+ (Nightly build) Unspecified Unspecified RESOLVED INVALID P2 Normal --- 83033 76773 1 rafael.lobo webkit-unassigned abecsi cmarcelo hausmann kenneth oldest_to_newest 593943 0 rafael.lobo 2012-04-02 15:50:38 -0700 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 + } 594587 1 abecsi 2012-04-03 10:11:09 -0700 This bug might be invalid after https://bugs.webkit.org/show_bug.cgi?id=83033. (In reply to comment #0) > 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 > + } 594932 2 rafael.lobo 2012-04-03 14:57:33 -0700 (In reply to comment #1) > This bug might be invalid after https://bugs.webkit.org/show_bug.cgi?id=83033. > Oh yea, hope so. I will mark this one depending on that then. Thanks! :) 630245 3 abecsi 2012-05-22 04:46:18 -0700 Since the WebView is a direct subclass of Flickable, this bug is no longer valid.