Hello – I am encountering this exact bug from 2017:
Is there any recommendation on the fastest fix, or does the issue just persist in the same form 4 years later? Deleting the element and replacing it creates a bunch of errors throughout the app, and I’m trying to deploy this version to live over the next 30 minutes, so re-building everything isn’t an option