Status: Unconfirmed Owner: ---- Labels: OS-Mac Area-Misc Pri-2 Type-Bug New issue 18796 by viettrungluu: Assertion failure on Mac (invalid message sent to NSEvent) http://code.google.com/p/chromium/issues/detail?id=18796
Chrome Version : <from About Google Chrome/Chromium> What steps will reproduce the problem? 0. Find a Mac with a fn key (e.g., a MacBook). 1. Run Chromium from somewhere where you'll see stderr (I think) output, e.g., from Terminal. 2. Click on the "web page area", so that key focus is there (rather than, e.g., the location bar). 3. Press the fn key. What is the expected result? Nothing. What happens instead? 2009-08-07 18:46:33.734 Chromium[62157:10b] *** Assertion failure in -[NSEvent charactersIgnoringModifiers], /SourceCache/AppKit/AppKit- 949.46/AppKit.subproj/NSEvent.m:1135 2009-08-07 18:46:33.738 Chromium[62157:10b] Invalid message sent to event "NSEvent: type=FlagsChanged loc=(0,742) time=189900.7 flags=0x100 win=0x0 winNum=19731 ctxt=0x1fd03 keyCode=63" I'm on it. I know where it's happening (WebKit::windowsKeyCodeForKeyEvent()). -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
