@Elchi3 @queengooborg Can we make an exception to normal rules and purge the old santizer data entirely - then restart?

The data is correct, but unhelpful. The old API was released "prematurely" - because the new and old API share some API names this can really only confuse people. They point to documentation of the old API too, which I would also like to delete.

Thoughts?

I haven't looked into the Sanitizer API in details but seems reasonable to do that to avoid confusion.
Looks like it was removed in Chromium in September 2022, so almost two years ago.
CC'ing another BCD owner for opinions: @foolip.

I'd be happy to make an exception for Sanitizer, or even change the guideline to 1 year.

Thanks @foolip

OK, @22jcampb can you point me to "evidence" of the addition in version 125.0.6422.112 and what exactly was added - i.e. is it a precise implementation that fully reflects the current spec, or something else? Does it support all the configuration options (or will it) and so on. I can't find anything on "new work" in chromestatus.

That affects how we might do this work (not so much this data, but corresponding changes in MDN content).

This is all it says, the flag "enables the Sanitizer API" and links to the GitHub page. No specific details on implementation.