NPAPI:CocoaCompositionClarification: Difference between revisions
No edit summary |
|||
| Line 5: | Line 5: | ||
= Contributors = | = Contributors = | ||
* Last modified: November | * Last modified: November 28, 2010 | ||
* 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]]). Plugins need a way to know when complex text composition (started by returning 'kNPEventStartIME' for an 'NPCocoaEventKeyDown' event) has been canceled by the user or the browser. Plugins receive key events during composition and without this extension they cannot tell in-composition key events from post-composition key events unless a composition completes and results in an 'NPCocoaEventTextInput' event. | ||
= Specification Change = | = Specification Change = | ||
In order to provide the plugin with information about whether or not there is a complex text composition in progress we will bump the 'NPCocoaEvent' version to '2'. If a plugin receives an 'NPCocoaEvent' with a version of '2' or higher then the key structure will contain a field of type 'NPBool' called 'compositionInProgress'. | In order to provide the plugin with information about whether or not there is a complex text composition in progress we will bump the 'NPCocoaEvent' version to '2'. If a plugin receives an 'NPCocoaEvent' with a version of '2' or higher then the key structure will contain a field of type 'NPBool' called 'compositionInProgress'. The 'compositionInProgress' field is only valid for 'NPCocoaEventKeyDown' events and will be set to false when no composition is in progress and true when a composition is in progress. | ||
= Open Questions = | |||
< | <ul> | ||
<li> | <li> Alternatively, we could say that once composition is started it will always result in an 'NPCocoaEventTextInput' event and canceled compositions will simply result in an 'NPCocoaEventTextInput' event with an empty string. | ||
</ul> | |||
</ | |||
Revision as of 09:31, 28 November 2010
Status
Under consideration.
Contributors
- Last modified: November 28, 2010
- Authors: Josh Aas (Mozilla)
- Contributors: Stuart Morgan (Google)
Overview
This proposal modifies the existing Cocoa NPAPI specification (NPAPI:CocoaEventModel). Plugins need a way to know when complex text composition (started by returning 'kNPEventStartIME' for an 'NPCocoaEventKeyDown' event) has been canceled by the user or the browser. Plugins receive key events during composition and without this extension they cannot tell in-composition key events from post-composition key events unless a composition completes and results in an 'NPCocoaEventTextInput' event.
Specification Change
In order to provide the plugin with information about whether or not there is a complex text composition in progress we will bump the 'NPCocoaEvent' version to '2'. If a plugin receives an 'NPCocoaEvent' with a version of '2' or higher then the key structure will contain a field of type 'NPBool' called 'compositionInProgress'. The 'compositionInProgress' field is only valid for 'NPCocoaEventKeyDown' events and will be set to false when no composition is in progress and true when a composition is in progress.
Open Questions
- Alternatively, we could say that once composition is started it will always result in an 'NPCocoaEventTextInput' event and canceled compositions will simply result in an 'NPCocoaEventTextInput' event with an empty string.