sanitizer-api

With context, this article is more interesting than the title might imply. > The Sanitizer API is a proposed new browser API to bring a safe and easy-to-use capability to sanitize HTML into the web platform [and] is currently being incubated in the Sanitizer API WICG, with the goal of bringing this to the WHATWG. Which would replace the need for sanitizing user-entered content with libraries like DOMPurify by having it built into the browser's API. The proposed specification has additional information: https://github.com/WICG/sanitizer-api/

After a minute of digging, found discussion here: https://github.com/WICG/sanitizer-api/issues/100 Perhaps it can be reopened (or a new issue can be opened) regarding naming.

Seeing as [nobody seems to have brought it up to them](https://github.com/WICG/sanitizer-api/issues?q=sgml), I'm not surprised that they haven't addressed it. But, as always, specific & easy-to-use APIs are going to win out over more "fully general" ones. Are you suggesting that everybody learn DSSSL and write queries like ((match-element? nd '(section title)) (format-number-list (hierarchical-number '("chapter" "section") nd) "1" ".")) Simply to be able to safely display some markup? I for one would much rather work on an AST with normal javascript instead of having to learn another DSL.