The reason they probably had to do this was because contentEditable works differently in each browser, and probably even between versions. I've tried to make a

The reason they probably had to do this was because contentEditable works differently in each browser, and probably even between versions. I've tried to make a similar component earlier, and it was a frustrating experience. Pretty sure they'd have supported all browsers if it was just about typical HTML and CSS. If this is true (I don't know), we should blame the lack of standardization instead.