[Webkit-unassigned] [Bug 65264] New: kNPEventStartIME doesn't work correctly for NPAPI

[bugzilla-daemon at webkit.org]

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

           Summary: kNPEventStartIME doesn't work correctly for NPAPI
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
        OS/Version: Mac OS X 10.6
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: Plug-ins
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: billappleton at dreamfactory.com


On Safari, typing the "g" key will generate a (1) key down event and then (2) a key up event with no call to NPCocoaEventTextInput 

--> this is wrong because i used the kNPEventStartIME flag, see FireFox behavior below

On Safari, typing "option-e" and then "e" will generate (1) key up event and then (2) a NPCocoaEventTextInput event with "accented e", and then (3) a key up event

--> this is wrong because there is a strange key up event sent at first, see FireFox behavior below

Based on my understanding of the spec Safari or webkit is implementing this incorrectly

https://wiki.mozilla.org/NPAPI:CocoaEventModel

On FireFox, typing the "g" key will generate a (1) key down event and then (2) a NPCocoaEventTextInput with "g" and then NO key up event
On FireFox, typing "option-e" and then "e" will generate (1) key down event, (2) a NPCocoaEventTextInput event with "accented e" and then NO key up event

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