@fioraau0 Had faced the same problem.
The custom element “on” trigger never fired.
Moving the same code into a new custom-code.js file and renaming the tag did the trick for me.
I reckon, just renaming the tag may also do the trick, weird.
@fioraau0 Had faced the same problem.
The custom element “on” trigger never fired.
Moving the same code into a new custom-code.js file and renaming the tag did the trick for me.
I reckon, just renaming the tag may also do the trick, weird.