The current keyboard loading and registration process has some inefficiencies that nee

Re-analysis notes: (On point 1) There's nothing

(On point 1) It only loads the metadata in that initial injection; it won

Implemented with <a class="issue-link js-issue-link" data-error-text="Failed to load t

Decouple keyboard registration and stub processing about keyman HOT 3 CLOSED

keymanapp commented on September 26, 2024

Decouple keyboard registration and stub processing

from keyman.

jahorton commented on September 26, 2024

Re-analysis notes:

(On point 1) There's nothing within the keymanweb.addKeyboardArray function that checks against already-registered keyboards. The closest thing is the check for pre-specified filenames on existing stubs.
(On point 2) This directly affects http://help.keyman.com.local/developer/engine/web/10.0/guide/examples/full-manual-control, which is unable to set the 'global' KMW active keyboard to the 'default' English keyboard because of the current active keyboard selection behavior during initialization. It forces an existing stub to be selected as active, triggering a load; when this load completes, it forces its keyboard stub to be set as active.

from keyman.

jahorton commented on September 26, 2024

(On point 1) It only loads the metadata in that initial script injection; it won't have tried to re-register the keyboard itself. This may actually be necessary to ensure it has the correct metadata for extra languages for a preloaded keyboard.

from keyman.

jahorton commented on September 26, 2024

Implemented with #343.

from keyman.