I was just looking at that - I tested my app in three different browsers and this issue is not apparent in FireFox but I will absolutely consider getting it bc I actually like Chrome a lot better than any other browser.
Strange and unexpected behavior. And if it should to be expected this way, than put a note in the documentation. @Geoff_Perlman gives a sample with which he cannot reproduce the problem, while @Amy_Barnes and I can with Chrome on Win10.
It’s a bug. One browser ok, another not, etc. Tim even said he had to create a workaround to the bug. The fix should be just baked into the framework. @Amy_Barnes, please, don’t mark it as solved, or the case could potentially be ignored as if it was an user error corrected by the user.
It’ll be the solution when implemented. I’d remove the [SOLVED] word from the title, because it’s not really solved, just the solution was presented. It’s schedule for 2021r1. In case of not accomplishing it, it’ll be another disappointment, but it’s the ONLY solution possible. Anything else are just workarounds because the bug is still baked into the framework causing problems everywhere until noticed.
No way Tim. I appreciate very much your efforts with those workarounds that surpass very much this only case stated in here, and would say to anyone needing such workarounds for now a “go for it”. But in no way I would say “well, Tim have a workaround for it, let’s give up and not ask for fixing it”.