[Webkit-unassigned] [Bug 142945] New: REGRESSION (Yosemite): WKView visibility notifications are messed up

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=142945

            Bug ID: 142945
           Summary: REGRESSION (Yosemite): WKView visibility notifications
                    are messed up
    Classification: Unclassified
           Product: WebKit
           Version: 528+ (Nightly build)
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebKit2
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: ap at webkit.org
                CC: andersca at apple.com, barraclough at apple.com,
                    sam at webkit.org, simon.fraser at apple.com

This test fails on Yosemite when run alone:

run-webkit-tests fast/dom/Geolocation/requestQueuingForHiddenPage.html

The reason is that we use internal AppKit notifications, and clash with NSView in how they work. NSView has its own NSWindowDidOrderOffScreenNotification and NSWindowWillOrderOnScreenNotification observer, and unregisters them when it view gets a layer-backed ancestor. This happens asynchronously when a page is created, we send an enterAcceleratedCompositingMode message from WebProcess to UI process.

As both WKView and NSView try to dynamically add/remove the same view object as an observer, there are undoubtedly many situations in which they get confused.

This particular bug happens because WKView thinks that it is an observer, but NSView has already undone the registration.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20150322/6ff802fb/attachment-0002.html>