NPAPI:CocoaCompositionClarification: Difference between revisions

NPAPI:CocoaCompositionClarification (view source)

Revision as of 21:59, 6 January 2011

502 bytes removed , 6 January 2011

no edit summary

Josh

Confirmed users, Bureaucrats and Sysops emeriti

1,680

edits

@@ Line 21: / Line 21: @@
 This paragraph will be changed to:
-"No <code>NPCocoaEventKeyDown</code> or <code>NPCocoaEventKeyUp</code> events associated with a complex text input window that may be open during composition will be sent to the plugin. <code>NPCocoaEventFlagsChanged</code> events will still be sent. Browser implementers should be mindful of the edge case where a key down ends composition (typically the <code>return</code> key) - the subsequent key up event, while it may not target the input window directly, is considered to be associated with the input window and should not be sent to the plugin."
+"No <code>NPCocoaEventKeyDown</code> or <code>NPCocoaEventKeyUp</code> events will be sent to the plugin during composition. <code>NPCocoaEventFlagsChanged</code> events will still be sent. Browser implementers should be mindful of the edge case where a key down ends composition (for example, the <code>return</code> key when an input window is in use) - the subsequent key up event is considered to be associated with the composition and should not be sent to the plugin."
 = Open Questions =
-* A composition window being "open" is probably not the right criteria; in the case of simple accented characters (e.g., é), a composition is in progress when the accent is entered, but a window may not actually be displayed for that simple composition. The right behavior there would still be to not send the key events to the plugin. It would probably be better to say explicitly that it's "while composition is in progress".
+* None
 = Alternatives =