Confirmed users, Bureaucrats and Sysops emeriti
1,680
edits
NPAPI:CocoaEventModel: Difference between revisions
Jump to navigation
Jump to search
→Text Input
| Line 213: | Line 213: | ||
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 return 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. | 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 return 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. | ||
Due to an [[NPAPI:CocoaCompositionClarification|amended specification]] and inconsistency in original implementations the variable <code> | Due to an [[NPAPI:CocoaCompositionClarification|amended specification]] and inconsistency in original implementations the variable <code>NPNVsupportsUpdatedCocoaTextInputBool</code> (NPNVariable = 3002) will indicate whether a browser supports this updated specification or not. If this is not defined and true then text input behavior will vary between browsers. | ||
== Notes == | == Notes == | ||