Closed ezl closed 2 years ago
@yassinya i see this is marked as ready for review -- out of curiosity, what was the problem and how did you fix it?
@ezl It turns out the problem was that the “&” character was being converted to &
when setting the value of the contenteditable input using innerHTML
.
I had to switch over to using textContent
in order to solve it
Got it! Thanks for explaining!
https://www.loom.com/share/7bf59127915049afac8e48d1c8c188fe