[Webkit-unassigned] [Bug 12383] New: Lost Flash events using NSBorderlessWindowMask

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Jan 23 09:35:48 PST 2007


http://bugs.webkit.org/show_bug.cgi?id=12383

           Summary: Lost Flash events using NSBorderlessWindowMask
           Product: WebKit
           Version: 418.x
          Platform: Macintosh
        OS/Version: Mac OS X 10.4
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: WebKit Misc.
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: rhoeper at measuredprogress.org


REGRESSION: Yes
SEVERITY: Is in the eye of the beholder

We have a Cocoa Kiosk built using Webkit that creates the mainWindow using
NSBorderlessWindowMask in level GSShieldingWindowLevel.  We presently build
with version 418.8 of webkit, XCode version 2.4, and find that Flash mouse
events are lost when using NSBorderlessWindowMask.  We have solved this problem
temporarily using NSTitledWindowMask, but this is, of course, not a perfect
solution.  No Flash mouse events are lost with NSTitledWindowMask.  We do have
the mainWindow as an NSWindow subclass and have canBecomeKeyWindow returning
YES.  We make one simple NIB file and do most of this programmatically.

Previous builds with Panther versions did not have this problem.

As our product is a production level Assessment Testing Kiosk, we are generally
reluctant to upgrade to latest versions without extensive compatiblity testing.
 So far, with our recent upgrades, the only big glitch we have hit is the one
above.

The Flash in question is created as Flash MX 2004, ActionScript 2.0, Player 7
documents.  Our QA tests with Flash Player plugins from version 7 up.  Since I
can turn the problem on or off by toggling NSBorderlessWindowMask or
NSTitledWindowMask, the bug points towards NSBorderlessWindowMask.  We support
and our QA tests with Panther and Tiger.

Regards,
Richard


-- 
Configure bugmail: http://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.



More information about the webkit-unassigned mailing list