I know this was reported before, but I believe it was actually fixed in Firefox (or we did a workaround?). It's fundamentally a Firefox bug, but I'm not sure if there's been a regression here from it.
That's interesting. A possible solution could be switching the template modification template to use a readonly textarea instead of a div if that's the case.