Re: [blink-dev] Intent to Ship: Storage Access API with Prompts

I see this as the other vendors endorsing Blink's general policy, implied by the wording in https://www.chromium.org/blink/guidelines/web-platform-changes-guidelines/#browser-engine-reviews, that there's a high bar for name changes after shipping. If this API, which has a clearly inaccurate name an

Re: [blink-dev] Intent to Ship: Enrollment for Privacy Sandbox

Transparency serves a bunch of different goals, as described in https://w3ctag.github.io/privacy-principles/#transparency, and the most valuable aren't always to give an end-user more information while they're trying to make a decision. I think the explainer is clear enough in saying that its goal

Re: [blink-dev] Intent to Ship: Deprecate TLS SHA-1 server signatures

This should probably be an "Intent to Deprecate and Remove" rather than an "Intent to Ship". I'll let an API owner say if there's a reason to re-send it; probably there isn't. On Mon, Sep 18, 2023 at 3:47 PM 'David Adrian' v

Re: [blink-dev] Intent to Ship: Deprecate TLS SHA-1 server signatures

On Mon, Sep 18, 2023 at 4:11 PM David Adrian wrote: > > This should probably be an "Intent to Deprecate and Remove" rather than > an "Intent to Ship". > > You're absolutely right that it should be, unfortunately that's not the > subject Chrome Status generated. I'll file an issue. > Oops, yes, y

Re: [blink-dev] Intent to Prototype: Verifying IPFS client

Thanks for posting this here. I have a couple questions/suggestions: * In your explainer, I don't see a description of the use cases for each of the 3 URL forms you plan to implement. https://tag.w3.org/explainers/ has some guidance around doing that. * The explainer says "Why HTTP(s)?", but nothi

Re: [blink-dev] Intent to Ship: Ruby-specific display values

My reading of #1771 is that the only thing keeping out of HTML is the lack of a Blink or WebKit implementation. It looks like https://github.com/whatwg/html/pull/6478 is already written to improve the text, so the only thing for Kent to do is to make sure that this change implements that PR and th

[blink-dev] Chromium process and tooling Survey - ACTION REQUESTED

Hello blink-dev! We continue to work on refining the Chromium process and tools, and we'd like to get YOUR thoughts to help direct how we improve the process, tools and documentation around Chromium (similar to a survey

[blink-dev] Re: Chromium process and tooling Survey - ACTION REQUESTED

You have 1 more week to tell us what you like and don't like about the Chromium process, so please fill this out if you haven't yet. We'll send a summary of the results out next week. Thanks, Jeffrey On Wed, Feb 16, 2022 at 5:00 AM Jeffrey Yasskin wrote: > Hello blink-dev! > > We continue to wo

[blink-dev] Process survey results

Hello Blink-dev! We took a survey of your impressions of our process and tooling back in February, and I wanted to share the results. This survey was an iteration of a survey conducted in early 2021