NPAPI:CocoaCompositionClarification: Difference between revisions

NPAPI:CocoaCompositionClarification (view source)

Revision as of 01:25, 19 January 2011

4 bytes added , 19 January 2011

→‎Specification Change

Josh

Confirmed users, Bureaucrats and Sysops emeriti

1,680

edits

Revision as of 01:09, 19 January 2011 (view source) Josh (talk \| contribs) (→‎Specification Change) ← Older edit		Revision as of 01:25, 19 January 2011 (view source) Josh (talk \| contribs) (→‎Specification Change) Newer edit →
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>~~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.		The variable <code>NPNVsupportsUpdatedCocoaTextInputBool</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.