> I hope it lands in the browsers. Why would you want world's least performant layout/UI engine infect canvas? This literally just cements the situation you qu

> I hope it lands in the browsers. Why would you want world's least performant layout/UI engine infect canvas? This literally just cements the situation you quote about having no access to good APIs. A reminder that Figma had to "create a browser inside a browser" to work around DOM limitations: https://www.figma.com/blog/building-a-professional-design-tool-on-the-web/ https://www.figma.com/blog/building-a-professional-design-to... > It's simply impossible to do with contenteditable in a product level way - one of the reasons Google docs has a custom layout engine. This proposal would enable full use of contenteditable for rich text, but with full page/print layout control. Why would it enable contenteditable for rich text if you yourself are saying that it doesn't work, and Google had to implement its own engine?