3 ms·
What do you mean by harder to support? Supporting - in the sense that it works - canvas rendering is much simpler than even minor amounts of the DOM. The proble
by olliej 4y ago
What do you mean by harder to support? Supporting - in the sense that it works - canvas rendering is much simpler than even minor amounts of the DOM. The problem of course is that you're replacing compiled C++ that is doing the normal DOM/CSS layout and rendering with someone implementing the layout and rendering in JS (sans actual bitblitting, etc).
- tomcam 4y ago> canvas rendering is much simpler than even minor amounts of the DOM How is the accessibility picture?
- olliej 4y agoIf you’re making a site using canvas to render UI elements you are taking it upon yourself to implement a lot of standard functionality yourself, similarly even basic text entry, let alone editing, is much more complex than people seem willing to accept. At google’s size/cash implementing these things might be achievable, but I recall many people/projects over the years that decided to do in canvas rather than using the available engine (often times a belief that their desire for pixel perfect positions was reasonable, and more than made up for needing to draw everything and manage text entry themselves) always looks easy at first glance, typically because the authors don’t use accessibility tools and most who I interacted with were English-first devs who believe one keypress event == one letter. So you end up with yet another English-only (and I really do mean English specifically here, not Western European) and inaccessible rendering engine for a web page, that typically could have achieved 95-100% of what they wanted, with a bunch of the remainder being stuff that doesn’t work for people with accessibility issues.