NPAPI:CocoaCompositionClarification: Difference between revisions
| (15 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
= Status = | = Status = | ||
Accepted, ready for implementation. | |||
= Contributors = | = Contributors = | ||
* Last modified: | * Last modified: January 18, 2011 | ||
* Authors: Josh Aas (Mozilla) | * Authors: Josh Aas (Mozilla) | ||
* Contributors: Stuart Morgan (Google) | * Contributors: Stuart Morgan (Google) | ||
| Line 11: | Line 11: | ||
= Overview = | = Overview = | ||
This proposal modifies the existing Cocoa NPAPI specification ([[NPAPI:CocoaEventModel]]). | This proposal modifies the existing Cocoa NPAPI specification ([[NPAPI:CocoaEventModel]]). Under the current specification plugins receive key events during complex text composition but do not have a reliable way to know whether or not key events are intended for use in the composition. Since composition can be canceled by the user or the browser plugins cannot assume that composition is in progress until they receive an 'NPCocoaEventTextInput' event. | ||
= Specification Change = | = Specification Change = | ||
The original "Text Input" section stated: | |||
"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 has been changed. See the current "Text Input" section of the [[NPAPI:CocoaEventModel|Cocoa event model spec]] for the updated version. | |||
Latest revision as of 23:59, 20 January 2011
Status
Accepted, ready for implementation.
Contributors
- Last modified: January 18, 2011
- Authors: Josh Aas (Mozilla)
- Contributors: Stuart Morgan (Google)
Overview
This proposal modifies the existing Cocoa NPAPI specification (NPAPI:CocoaEventModel). Under the current specification plugins receive key events during complex text composition but do not have a reliable way to know whether or not key events are intended for use in the composition. Since composition can be canceled by the user or the browser plugins cannot assume that composition is in progress until they receive an 'NPCocoaEventTextInput' event.
Specification Change
The original "Text Input" section stated:
"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 has been changed. See the current "Text Input" section of the Cocoa event model spec for the updated version.