First, my article is NOT about the standard webpage. It is about COMPLEX applications (for example: https://www.bobsprite.com/editor).

Also, I recommend to use an image to present a table (tabular data), because it is safe (and often used).

OK?

Now I will try to answer to your topics:

* All the mentioned "browser idiosyncrasies" are solved by using proper responsive design practices.

> OK, but are cases where we can't achieve a good result everywhere, that's why I said "throw an image".

Rendering your websites with canvas will incur a massive performance penalty on your users for no reason.

> I don't think so. I have perceiving excellent performance using canvas.

Using HTML/CSS to build your UIs will result in a more responsive and pleasant experience in pretty much every case because it is the one task that browsers are written to do.

> Browsers are written to do a lot of things. You must include JavaScript, WebAssembly, canvas... The real examples that the articles shows prove that the experience is not always pleasant or responsive.

* Using canvas for ui is an accessibility NIGHTMARE. Suddenly, anyone who uses a screenreader will not be able to use your site at all, which brings us to another no-brainer: trying to overrule your user's font size preferences is NOT a noble pursuit! It is your responsibility and your responsibility alone to make sure that your website looks presentable even in situations where the font size is not what you'd expect.

> The point is: my article is not about a standard webpage.

Oh, and of course trying to bypass the user's translation settings is also provided as a reason to use canvas. I'm starting to think this is some kind of elaborate satire.

> No. It is real deal.

* The "colored" is not a bug, it's a feature. It's called subpixel antialiasing, and it makes use of the fact that every pixel on your screen is actually composed of three subpixels to increase the text resolution, and thus, legibility. The fact that canvas does not support this demonstrates its inferior text rendering capabilities.

> In no way I said it was a bug. It is a superior feature. But the canvas is able to match the quality, this is the subject of the next article.

"We will be creating a browser inside a browser!"

This is called reinventing the wheel. It's bad. Please don't do this.

> It is already done (BobSprite) and I am very happy. And I think it is the best way to go (for applications like that, of course).

I think I have to edit the start of my article because people are not getting to the point.

Thanks for your reply!