838166 - Consider refactoring how we react to missing entities while localizing document

Status: RESOLVED INCOMPLETE

(L20n :: HTML Bindings, defect)

Description

[Zibi Braniecki [:zbraniecki][:gandalf]]

An idea from bug 801663 is to change how we react to missing entities while localizing the document.

We then adjust l20n-xml code to:
 - switch this flag on on localizationReady when it begins localizing nodes
 - when it encounters a node that is missing (and throws exception) it ignites fallback context loading asynchronously and add this node to the list of nodes that will be localized when fallback context is ready
 - it continues localizing nodes, and if it encounters more nodes that cannot be translated it adds them to that list
 - when subcontext is loaded it localizes those that were waiting
 - it fires DocumentLocalized only when all nodes are localized
 - on firing DocumentLocalized it switches off the dontFallback flag to off

 - if DocumentLocalized has loaded and the developer programmatically asks for an entity that we don't have, we load fallback context synchronously.

 - before DocumentLocalized we encourage to use getAsync or prepare for get throwing

Comment 1

[Staś Małolepszy :stas]

We moved to async-only API in the meantime, so this is no longer relevant.