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
On Tue, Feb 6, 2024 at 1:26 AM Yoav Weiss (@Shopify)
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
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 ":").
On Fri, Jan
On Wed, Jan 24, 2024 at 8:10 AM Yoav Weiss (@Shopify) <
yoavwe...@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
Also, what are the timelines you have in mind in terms of deprecation?
On Wed, Jan 24, 2024 at 4:51 PM Daniel Bratell 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
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.
For this feature, what is the status of
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 saw that there's a
On Mon, Jan 22, 2024 at 8:05 AM Vladimir Levin 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
On Fri, Jan 19, 2024 at 7:54 PM Mason Freed wrote:
>
>
> On Friday, January 19, 2024 at 12:27:50 PM UTC-8 vmp...@google.com wrote:
>
> Interoperability and Compatibility
>
> The use counter for getInnerHTML() (https://chromestatus.com/
> metrics/feature/timeline/popularity/3874) shows 0.04% of
On Friday, January 19, 2024 at 12:27:50 PM UTC-8 vmp...@google.com wrote:
Interoperability and Compatibility
The use counter for getInnerHTML() (https://chromestatus.com/
metrics/feature/timeline/popularity/3874) shows 0.04% of page loads using
this function as of January 2024. That
On Fri, Jan 19, 2024 at 3:13 PM Mason Freed wrote:
> Contact emailsmas...@chromium.org
>
> Explainer
> https://github.com/whatwg/html/issues/8867#issuecomment-1856696628
>
> SpecificationNone
>
> Summary
>
> The prototype implementation (which was shipped in 2020 and then
> shape-changed in
Contact emailsmas...@chromium.org
Explainerhttps://github.com/whatwg/html/issues/8867#issuecomment-1856696628
SpecificationNone
Summary
The prototype implementation (which was shipped in 2020 and then
shape-changed in 2023) contained a method called `getInnerHTML()` that
could be used to
12 matches
Mail list logo
