see all my previous replies in this thread as to why this can't "magically" be fixed by us. I wish I could just wave a wand and utter "browser repairum!" but that's not how it works in the real world.
For anything like this to be fixed it requires:
- To know why this behaviour happens. Both in general as in what library or what not causes this and in detail exactly what behaviour is different that causes the library or framework to exhibit this strange and unwanted behaviour on UXP.
- Analysis of the different behaviour to determine if it is actually a bug on our end or a bug in the scripting (e.g. by targeting specific implementation quirks of other engines).
- Finding either a workaround or implementation solution that doesn't break anything else.