If you intend to deprecate and remove, that is the "Prepare to ship" stage on your chromestatus feature entry. You can use the review gate chips to access the intent preview and then copy and paste that to start the thread. https://screenshot.googleplex.com/5GioLEtEnQBvTZu
The subject line will be "Intent to Ship: Deprecation of non-standard declarative shadow DOM serialization". Using "Intent to deprecate and remove" should also work. ChromeStatus doesn't actually look for the colon in the subject line, it just looks for keywords near the start of the subject line, and it looks for the body line "Link to entry on the Chrome Platform Status" and the link to your entry. Thanks, jason! On Tuesday, February 6, 2024 at 8:08:54 AM UTC-8 mas...@chromium.org wrote: > On Tue, Feb 6, 2024 at 1:26 AM Yoav Weiss (@Shopify) <yoav...@chromium.org> > wrote: > >> Is this thread meant for both deprecation and removal (given the short >> timelines)? >> >> Apologies for the delay in responding here. It might be worthwhile to >> re-send it with the right title, as it's currently not caught in the API >> owner's tooling (I suspect that's due to a missing ":"). >> > > Yes, I did hope to do both with this one intent. I’ve learned not to edit > the title of the email (e.g. to say “deprecate AND remove” because then the > tool definitely doesn’t pick it up. I’m not sure what happened to the :, I > didn’t edit it. Sorry for the trouble, and thanks for catching it. > > So I should re-send the entire thing? > > > >> On Fri, Jan 26, 2024 at 11:30 PM Mason Freed <mas...@chromium.org> wrote: >> >>> >>> On Wed, Jan 24, 2024 at 8:10 AM Yoav Weiss (@Shopify) < >>> yoav...@chromium.org> wrote: >>> >>>> Also, what are the timelines you have in mind in terms of deprecation? >>>> >>> >>> I'd like to try starting to turn the feature off ASAP, in M123, to avoid >>> an effect I've discovered where usage spikes when I announce deprecations. >>> >> >> That's odd.. >> >> >>> I would very slowly enable, likely over about 2 months/milestones. Let >>> me know if that sounds ok. That's about the schedule I used for the >>> `shadowroot` attribute, and that was successful. >>> >>> >>> On Wed, Jan 24, 2024 at 4:51 PM Daniel Bratell <brat...@gmail.com> >>>> wrote: >>>> >>>>> Unreliable use counters sound scary. We base a lot of decisions off >>>>> those. So far they have only been shown to over-count though? But still, >>>>> would be great if someone could get a grip on that bug and either fix it >>>>> or >>>>> make us understand what is going on. >>>>> >>>> Yeah, I agree. In my experience (which tends to be a lot of >>> deprecations) the usage is always over-counted. My rough theory >>> <https://github.com/GoogleChrome/chromium-dashboard/issues/1545#issuecomment-949018584>, >>> >>> if correct, doesn't always mean usage will be over-counted though. >>> >>>> For this feature, what is the status of getHTML()? Can we redirect >>>>> users to it already? >>>>> >>>> It's implemented, and here's the chromestatus for that >>> <https://chromestatus.com/feature/5102952270528512>. I haven't shipped >>> it yet, but my plan is to do that ASAP. Ideally I ship it in M123, to >>> coincide with this deprecation. >>> >>> On 2024-01-23 20:38, 'Dan Clark' via blink-dev wrote: >>>>> >>>>> I guess a theoretical risk is that someone feature-checks for >>>>> HTMLTemplateElement.shadowRootMode and then assumes the existence of >>>>> getInnerHTML() based on that check. But given the lack of usage in the >>>>> top >>>>> sites I agree that this seems to not be an issue in practice. >>>>> >>>>> I suppose that's a theoretical risk, yes. I bet (hope?) it's rare >>> though. >>> >>>> I saw that there's a support email listed at https://www.heap.io/auryc. >>>>> Maybe worth a ping? >>>>> >>>>> Thanks, I'll give them a ping. I'm not sure it's worth it, given that >>> the existing feature detection is already disabled by the lack of the >>> `shadowroot` attribute. But no harm. >>> >>> Thanks, >>> Mason >>> >>> >>>> -- Dan >>>>> >>>>> On Monday, January 22, 2024 at 8:42:43 AM UTC-8 mas...@chromium.org >>>>> wrote: >>>>> >>>>>> On Mon, Jan 22, 2024 at 8:05 AM Vladimir Levin <vmp...@google.com> >>>>>> wrote: >>>>>> >>>>>>> Yeah, I think the risk is low here. >>>>>>>> >>>>>>> >>>>>> Great, thanks! >>>>>> >>>>>> >>>>>>> FWIW, I couldn't find any relevant github or contact info for this >>>>>>> library but if you had better luck finding contact information, we >>>>>>> might as >>>>>>> well file an issue or send an email. >>>>>>> >>>>>> >>>>>> I also tried to find it, but failed. It appears to be closed source. >>>>>> >>>>>> Thanks, >>>>>> Mason >>>>>> >>>>>> >>>>>> >>>>>>> >>>>>>>> Thanks, >>>>>>>> Mason >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> *Gecko*: No signal >>>>>>>> >>>>>>>> *WebKit*: No signal >>>>>>>> >>>>>>>> *Web developers*: No signals >>>>>>>> >>>>>>>> *Other signals*: >>>>>>>> >>>>>>>> WebView application risks >>>>>>>> >>>>>>>> Does this intent deprecate or change behavior of existing APIs, >>>>>>>> such that it has potentially high risk for Android WebView-based >>>>>>>> applications? >>>>>>>> >>>>>>>> None >>>>>>>> >>>>>>>> >>>>>>>> Debuggability >>>>>>>> >>>>>>>> None >>>>>>>> >>>>>>>> >>>>>>>> Is this feature fully tested by web-platform-tests >>>>>>>> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> >>>>>>>> ?No >>>>>>>> >>>>>>>> Flag name on chrome://flagsNone >>>>>>>> >>>>>>>> Finch feature nameNone >>>>>>>> >>>>>>>> Non-finch justificationNone >>>>>>>> >>>>>>>> Requires code in //chrome?False >>>>>>>> >>>>>>>> Tracking bughttps://crbug.com/1519972 >>>>>>>> >>>>>>>> Estimated milestones >>>>>>>> >>>>>>>> No milestones specified >>>>>>>> >>>>>>>> >>>>>>>> Link to entry on the Chrome Platform Status >>>>>>>> https://chromestatus.com/feature/5081733588582400 >>>>>>>> >>>>>>>> This intent message was generated by me, manually, because of this >>>>>>>> bug >>>>>>>> <https://github.com/GoogleChrome/chromium-dashboard/issues/3596>. >>>>>>>> >>>>>>>> -- >>>>>>>> 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/CAM% >>>>>>>> 3DNeDhpHobDUy1VwZ2rmy5DBUVfsm8ijXOEtk%2B1eHjJgu6FRg%40mail. >>>>>>>> gmail.com >>>>>>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM%3DNeDhpHobDUy1VwZ2rmy5DBUVfsm8ijXOEtk%2B1eHjJgu6FRg%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+...@chromium.org. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/bc371f9a-e39b-40cb-9941-c0b4dcc76342n%40chromium.org >>>>> >>>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/bc371f9a-e39b-40cb-9941-c0b4dcc76342n%40chromium.org?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+...@chromium.org. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/8357e80a-5b6b-4c73-83e7-de19e8ca1a37%40gmail.com >>>>> >>>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/8357e80a-5b6b-4c73-83e7-de19e8ca1a37%40gmail.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/7cc01cf5-46f3-4bf1-ab21-58f501bc03b1n%40chromium.org.
