Confirmed users, Bureaucrats and Sysops emeriti
1,680
edits
NPAPI:CocoaCompositionClarification: Difference between revisions
Jump to navigation
Jump to search
NPAPI:CocoaCompositionClarification (view source)
Revision as of 01:09, 19 January 2011
, 19 January 2011→Specification Change
No edit summary |
|||
| Line 23: | Line 23: | ||
"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." | "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." | ||
The variable <code> | The variable <code>NPNVsupportsUpdatedCocoaInputBool</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. | ||