Your title is effectively far more precise than mine. So the safest way to extend your framework is to use inline js? There's no other way to be sure that one of the two JS using the helper "require js" inside a same template will be loaded before the other one?This is fixed now. The XF classes were activated before inline JS was run; I've inverted this order now as it's more consistent with how it works for non-overlay triggers. I think this is the only scenario where it comes up.
So to be a little more concrete for me, all js loaded with "require js" helper will be loaded with the ExtLoader (when an overlay is called), which means if I want to load a JS file before your Editor framework possible and safe solutions would be:Well, the core issue that you're explaining -- the phrase text in the editor when loaded only via an overlay -- is simply related to inline JS vs xfActivate trigger order, which I've changed. If inline JS is not used (and in this case, it's only used for editor phrases), there won't be any change in behavior.
I'm not really stating anything about using inline script. If you have JS B that must run after A is loaded, you may need to look at ways to either change that or change how dependencies are loaded (not using the standard ExtLoader system). When we load external dependencies, we load them in parallel to be faster, so the execution order is indeterminate.
We use essential cookies to make this site work, and optional cookies to enhance your experience.