Note that our compat principles <https://docs.google.com/document/d/1RC-pBBvsazYfCNNUSkPqAVpSpNJ96U8trhNkfV0v9fk/edit#heading=h.x5bhg5grhfeo> say "Generally we avoid breaking any use cases which cannot be shown to have a reasonable alternate implementation". While 0.000000492% is tiny, it's still non-zero. Is it possible that there's some real-world site benefiting from this API? I suppose the fallback of a JS library isn't that much worse, so perhaps we're OK from a "reasonable alternate implementation" perspective.
I also want to get to an interoperable implementation quickly and am more supportive than Alex is of the idea that API shapes sometimes need to change to get to consensus. Our compat principles <https://docs.google.com/document/d/1RC-pBBvsazYfCNNUSkPqAVpSpNJ96U8trhNkfV0v9fk/edit#heading=h.enldekz90vw> also say "Sometimes Blink chooses explicitly to ship despite higher interop risk, and we accept responsibility for that risk by being more willing to take on compat risk in the future if the consensus of the web platform community is that the API should change.". But, like Alex, I also don't like the precedent of unshipping an imperfect API while the replacement is still under design debate and also not shipped in any other engine. Typically the above principle is used to apply after some other engine has shipped an API they feel is better, and we move to it in the name of interop. How quickly do we think we could ship the new API and Frederik, do you have a timeline for when you think Firefox might be able to ship it too? To what extent would it increase the engineering costs for your team Daniel to have both forms shipping simultaneously vs. removing the old one prior to shipping the new one? Is this <https://chromestatus.com/metrics/feature/timeline/popularity/3814> the right graph for the Sanitizer API UseCounter? Other than a temporary bump (one popular site perhaps?) it doesn't seem to be growing too quickly despite being in Chrome for a year. If we're actually on a near-term path to consensus and multi-engine support, would a couple more months of the old API existing really add much risk? If usage is non-zero (regardless how small) I always think it's a more defensible position with web developers to say we're removing something because a better alternative has shipped in Chrome for at least one milestone (even if "better" is mostly limited to "likely to also have support in Firefox"). Rick On Tue, Aug 22, 2023 at 6:54 AM Yoav Weiss <yoavwe...@chromium.org> wrote: > LGTM2 > > On Mon, Aug 21, 2023 at 6:17 PM Chris Harrelson <chris...@chromium.org> > wrote: > >> LGTM1 to remove in favor of a revised, interoperable AIP in the future. >> >> On Mon, Aug 21, 2023 at 6:38 AM 'Daniel Vogelheim' via blink-dev < >> blink-dev@chromium.org> wrote: >> >>> Hi Luke & Thomas, >>> >>> On Wed, Aug 16, 2023 at 12:49 PM Thomas Steiner <to...@google.com> >>> wrote: >>> >>>> Adding in Jack as the author of the mentioned article at >>>> https://web.dev/sanitizer/. It might be worthwhile to add a big red >>>> warning aside. >>>> >>>> On Tue, Aug 15, 2023, 23:37 Luke <lukewarlow...@gmail.com> wrote: >>>> >>>>> Just to chime in here. If there's a chance this API is going to be >>>>> removed or even heavily changed its potentially worth making an effort to >>>>> take down any documentation regarding it to try to prevent any chance of >>>>> its usage going up. For example the mdn page on it seems an easy one to >>>>> remove. Likewise the web.dev article. This may not be as important if >>>>> the usage is far below any thresholds. >>>>> >>>> >>> Yes, noted and agreed. Adjusting or even removing the docs has come up >>> before, and I hesitated to act on it because we didn't yet have clarity on >>> how to proceed with the Sanitizer API. The reason for writing this >>> intent-to-deprecate is to get agreement on how to proceed, and to decide >>> whether we'll keep supporting the current API in the future or not. If it's >>> okay with you, I'd like to let this discussion run its course, and then >>> adjust the docs depending on how api owners have decided here. >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "blink-dev" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to blink-dev+unsubscr...@chromium.org. >>> To view this discussion on the web visit >>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALG6KPMrdkH5Br_useiWyt3b8gXVWkzYi9tdL2DSJ9MTwefTjA%40mail.gmail.com >>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALG6KPMrdkH5Br_useiWyt3b8gXVWkzYi9tdL2DSJ9MTwefTjA%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "blink-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to blink-dev+unsubscr...@chromium.org. >> To view this discussion on the web visit >> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw_bxEMv20aYBqJoquxdty_2_-6EnszXipt1CP6MN7LqWQ%40mail.gmail.com >> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw_bxEMv20aYBqJoquxdty_2_-6EnszXipt1CP6MN7LqWQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- > You received this message because you are subscribed to the Google Groups > "blink-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to blink-dev+unsubscr...@chromium.org. > To view this discussion on the web visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAL5BFfVNC%2BqEMqMQ1UofPsN23_34y9kEc8MoZtJXLG_rQib%3D3g%40mail.gmail.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAL5BFfVNC%2BqEMqMQ1UofPsN23_34y9kEc8MoZtJXLG_rQib%3D3g%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFUtAY9jV_4gYYC3-XzsbFgxdcQiQ6R75qdRF8F0DSuh-QVXhA%40mail.gmail.com.
