*Summary*: Change the consumption steps of the Sanitizer API <https://developer.mozilla.org/en-US/docs/Web/API/HTML_Sanitizer_API> so that it sanitizes during parse steps, rather than the reified tree.
The motivation for this is to address some issues around the non-parser sanitization steps which prevent sanitizing scoped registries and declarative shadow roots. By and large this change should not be web observable, modulo the above two points. Scoped Registries has not shipped yet, and this is one way we can unblock them from shipping. *Bug*: https://bugzilla.mozilla.org/show_bug.cgi?id=2062652 *Specification*: https://github.com/whatwg/html/pull/12645 *Standards Body*: WHATWG *Platform Coverage*: all. *Preference*: `dom.security.sanitizer.while_parsing` *DevTools Bug*: N/A *Extensions Bug*: N/A *Use Counter*: I don't think this is necessary but happy to add one if people think it would be useful. *Standards-Positions Discussion*: https://github.com/mozilla/standards-positions/issues/1443 *Other Browsers*: - Blink: Shipped 153 (sub-feature of https://chromestatus.com/feature/5054329641893888) - WebKit: Positive of the overall feature. *web-platform-tests*: Sanitizer tests are here: https://wpt.fyi/results/sanitizer-api?label=experimental&label=master&aligned -- You received this message because you are subscribed to the Google Groups "[email protected]" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/0070a14d-e22a-46b7-9f87-8735f77e14b5%40app.fastmail.com.
