Cool spec for an action attribute on buttons, but I particularly liked this description of the distinction between a button and a link:

Buttons model actions which affect the current document, while hyperlinks model other documents (which the user could choose to open in the current browsing context, or a new one). Even though they both might result in GET requests, they represent different possibilities on the page...A button enforces that the close action always happens in this browsing context, while a hyperlink does not.

A spec proposal by Alexander Petros and Carson Gross:

we simply urge that HTML support the relevant, existing HTTP methods, which are so useful that they are universally-supported by servers in spite of their absence from the HTML standard.

I’m all for it! Let’s have HTML catch up to HTTP.

The usefulness of methods as an HTTP semantic—a priori to the semantics of the methods themselves—is so self-evident that the hypertext transfer protocol has long standardized a bunch of additional methods; all that remains is for the dominant hypertext markup to support them.

This is one part of the Triptych Proposals which look exciting to me.

it should be easy to use HTML to declare page behavior that makes HTTP requests, and then tell the browser to either do a full-page navigation or replace part of the page with the response.