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 18:52, 6 January 2011
, 6 January 2011no edit summary
No edit summary |
No edit summary |
||
| Line 5: | Line 5: | ||
= Contributors = | = Contributors = | ||
* Last modified: January | * Last modified: January 6, 2011 | ||
* Authors: Josh Aas (Mozilla) | * Authors: Josh Aas (Mozilla) | ||
* Contributors: Stuart Morgan (Google) | * Contributors: Stuart Morgan (Google) | ||
| Line 18: | Line 18: | ||
= Open Questions = | = Open Questions = | ||
* None | |||
= Alternatives = | |||
Preserved for reference... | |||
<ul> | <ul> | ||
<li> | <li> 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. Unlike the currently proposed solution this has the downside of potential backwards-compatibility issues. Adobe Flash? | ||
<li> | <li> 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. It will be set to false when no composition is in progress and true when a composition is in progress. | ||
</ul> | </ul> | ||