> And what's really weird is how some new features rely on JavaScript, such as the newer <dialog> HTML element. Compared to the older alert/confirm dialogue wh

> And what's really weird is how some new features rely on JavaScript, such as the newer <dialog> HTML element. Compared to the older alert/confirm dialogue which was driven by a C++ browser window + JS boolean it kind of makes sense for <dialog> to use JS for such a thing and keep it within the HTML/stylable context. Like confirms the only place it will be used is within JS. So there's no separating the two really. Unless you're just looking for a glorified HTML5 tag that you have to do yourself.