"ENTER" key event channels in Mozilla (ug2tLibMozilla.js)

Rene Zanner — Wed, 16 Jan 2008 09:11:22 -0000

When adding an <eventChannel type="KEYACTION" key="(ENTER)"> to any component it is not recognized in Mozilla browsers.

The reason is, that the JavaScript function eventChannelKey() in ug2tLibMozilla.js handling that pressed key is asking for the event.charCode instead for the event.keyCode.
Only in the keyCode is sent the key code 13 for the ENTER key - exactly the same as in IE.
In ug2tLibIE.js the code is correctly checking for the keyCode (and not the charCode), so my patch is to do it exactly the same in the Mozilla version of that JS function:

In release 1.8.1 change line no. 751 of ug2tLibMozilla.js from

if (event.charCode==13)

if (event.keyCode==13)

and the ENTER key works for key event channels also in Mozilla based browsers.

Use i18n in static plugin files

Rene Zanner — Mon, 23 Jul 2007 11:22:47 -0000

The mechanism to use xml files for internationalization of plugins currently is only supported for the standard plugin file. In case someone wants to use that mechanism also in the _static_ xml file of a plugin, he cannot use the plugin specific i18n file (denoted by "LANG_PlugInID", because the initialization of this registered variable is happening AFTER the processing of the static xml plugin file.

The "if" block in UnComponentFactory::pcmf_createAggregatedPlugin():

if (l_htmlDesc.pdm_textFile != null && l_htmlDesc.pdm_defTextFile != null)

must be moved before the "if" block checking for and processing the static xml file of the plugin:

if (l_htmlDesc.pdm_staticInitialized == false && l_htmlDesc.pdm_staticXmlConf != null)

Recent changes to patches

"ENTER" key event channels in Mozilla (ug2tLibMozilla.js)

Use i18n in static plugin files