Henri Sivonen

> Do you consider the use cases raised in this thread to be compelling? Sorry about the late reply. I'm OK with taking a contribution to add sort key exposure...

I believe I've commented previously along the following lines when this has come up: 1. For wiki projects, it's irrelevant whether this is in HTML. The wiki software processes the...

> But this one hasn't made it onto physical or software-defined keyboards. Why is that?

`innerHTML` is unfortunate in that it changes behavior depending on the HTML vs. XML bit of the owning document. Having this API that says "HTML" always serialize as HTML (and...

Oops, the previous comment went to the wrong issue. For this issue, being able to serialize what can be parsed makes sense for symmetry.

> > Oops, the previous comment went to the wrong issue. For this issue, being able to serialize what can be parsed makes sense for symmetry. > > Thanks for...

> The shape looks OK. I should clarify, that I meant the shape on the level of 1) new (relative to `innerHTML`) HTML serialization getter, 2) it being about the...

This issue could use a more detailed analysis of the good and bad aspects of both the "classic way" and what's being proposed and why the difference justifies the addition...

What's the level of evidence of a duration input being common enough a need? For example, is it common for JS UI frameworks to provide their own duration input?

On a general level, I'm worried _on security grounds_ about keeping changing the HTML parsing algorithm. If the server and the browser implement a different spec snapshot (libraries deployed in...