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 19:19, 6 January 2011
, 6 January 2011→Specification Change
No edit summary |
|||
| Line 15: | Line 15: | ||
= Specification Change = | = Specification Change = | ||
The specification currently states, in the "Text Input" section: | |||
"During complex text input the browser will continue to send regular key events. So long as the plugin still wants complex text input (which may result in a NPCocoaEventTextInput event being sent) it should continue to return kNPEventStartIME for NPCocoaEventKeyDown. If a plugin returns anything other than kNPEventStartIME for NPCocoaEventKeyDown then complex text input will be canceled." | |||
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." | |||
= Open Questions = | = Open Questions = | ||