A guide to understanding HTML APIs
codecoda.com
codecoda.com
> Canvas 2D Context API – This API allows users to draw in browsers. However, on the WHATWG living standard, it is mentioned that this API is no longer being actively maintained.
I can't find any such mention in the WHATWG canvas page[1]. Is the article correct in its claim?
The only thing that might be true is that it’s essentially a frozen feature set, with nothing new being planned, but again I don’t see a mention of that.
[1] - https://developer.mozilla.org/en-US/docs/Web/API/CanvasRende...
[2] - https://developer.mozilla.org/en-US/docs/Web/API/CanvasRende...
"There are arguments that HTML5 as a markup language does not have programming interfaces; instead, these APIs are JavaScript APIs with formatted HTML responses."
In an HTML API, the definitions and protocols are in the HTML itself, and the tools look in
HTML for the configuration. HTML APIs usually consist of a certain class and attribute patterns
that can be used on existing HTML.
HTML is just markup. You're familiar with markup if you've ever used a hilighter for instance. To make it an API just have something parse that markup according to some well-defined set of rules and to do _stuff_.I can write a parser that accepts a single API call as it were:
<p data-do-a-thing>Smith</p>
Now I can feed that into the parser and in this API of mine a `p` tag with attribute `data-do-a-thing` renders the contents of the tag prefixed with `Hello, ` giving `Hello, Smith`. Viola an API via HTML.