[lit-html][templateDefaultLang] Try to get inexistent defaultLang repeatedly with mixed templateDefaultLang
Root Cause
If an element's templateDefaultLang is different from the defaultLang ( = initial <html lang>), the element fails to fallback to its templateDefaultLang but repeatedly tries to get its language JSON for the defaultLang if it is inexistent
Expected Configurations to work around the issue
If different templateDefaultLang values for some elements are mixed, the defaultLang has to be set as empty, i.e., the initial <html lang> attribute of the document must be inexistent. In other words, if the default language of the document is not specified, elements can fail back to their own template language.
The priority of fallback for templateDefaultLang should be higher than that for defaultLang while the current implementation puts higher priority in defaultLang
The risks of unexpected side-effects of the priority changes would be higher than those of the simple workaround above, the priority change is put off for now.
[lit-html][templateDefaultLang] Try to get inexistent
defaultLangrepeatedly with mixedtemplateDefaultLangRoot Cause
templateDefaultLangis different from thedefaultLang( = initial<html lang>), the element fails to fallback to itstemplateDefaultLangbut repeatedly tries to get its language JSON for thedefaultLangif it is inexistentExpected Configurations to work around the issue
templateDefaultLangvalues for some elements are mixed, thedefaultLanghas to be set as empty, i.e., the initial<html lang>attribute of the document must be inexistent. In other words, if the default language of the document is not specified, elements can fail back to their own template language.Potential Fix (Under Investigation)
templateDefaultLangshould be higher than that fordefaultLangwhile the current implementation puts higher priority indefaultLangdefaultLangifbundles[defaultLang][this.is]is inexistentNotes