Re: [blink-dev] Intent to Ship: Private Aggregation API

On Tue, Jun 20, 2023 at 11:39 PM Rick Byers wrote: > > On Tue, Jun 20, 2023 at 4:51 PM Alex Turner wrote: > >> Contact emailsale...@chromium.org >> >> Explainer >> https://github.com/patcg-individual-drafts/private-aggregation-api >> >> Specification >> https://patcg-individual-drafts.github.io/

Re: [blink-dev] Re: Intent to Ship: Allow Navigator.registerProtocolHandler to register "ftp"

The HTML specification was updated for this change, and we don't see any bad signals after the last discussion. I think it's ok to land the implementation without re-approvals. On Wed, Jun 21, 2023 at 3:53 PM Javier Garcia Visiedo wrote: > Hi all, > > I'm revisiting this I2S, as the code chang

Re: [blink-dev] Intent to Prototype: Zstd Content-Encoding

On Wed, Jun 21, 2023 at 3:35 PM Yoav Weiss wrote: > > > On Wed, Jun 21, 2023 at 8:15 AM Nidhi Jaju wrote: > >> Contact emailsnidhij...@chromium.org >> >> Explainer >> https://docs.google.com/document/d/1aDyUw4mAzRdLyZyXpVgWvO-eLpc4ERz7I_7VDIPo9Hc/edit?usp=sharing >> Specificationhttps://datatrac

Re: [blink-dev] Intent to Prototype: Zstd Content-Encoding

On 2023年06月21日 18時02分49秒 (+09:00), Nidhi Jaju wrote: On Wed, Jun 21, 2023 at 3:35 PM Yoav Weiss wrote: On Wed, Jun 21, 2023 at 8:15 AM Nidhi Jaju wrote: Contact emails nidhij...@chromium.org Explainer https://docs.google.com/document/d/1aDyUw4mAzRdLyZyXpVgWvO-eLpc4ERz7I_7VDIPo9Hc/

Re: [blink-dev] Intent to Prototype: Zstd Content-Encoding

> > Drive by question: Given that the codec is going to be in the browser, are > there plans to surface this up to CompressionStreams? (same question > applies for Brotli, I suppose) For the zstd Content-Encoding, we will only be linking in the decompression part of the zstd library. But for Comp

Re: [blink-dev] Intent to Prototype: Zstd Content-Encoding

On 2023年06月21日 19時17分58秒 (+09:00), Adam Rice wrote: Drive by question: Given that the codec is going to be in the browser, are there plans to surface this up to CompressionStreams? (same question applies for Brotli, I suppose) For the zstd Content-Encoding, we will only be linking in the de

[blink-dev] Intent to Ship: WebRTC RTP header extension control

Contact emails h...@google.com, h...@google.com, phan...@microsoft.com (sticking to my already subscribed email for sending) Explainer https://docs.google.com/document/d/1y1hTsMeav5ijPvoqu1R6U4YC564i1QzgkMeIqWhgiis/edit# (slightly outdated but still conveys the general idea) Spec https://w3c.

Re: [blink-dev] Intent to Ship: Shared Storage API

I was the spec mentor for shared storage and worked with Cammie on the spec. I'd just like to add my thoughts to provide the requested spec maturity summary . Overall I think the spec process model has reached a high level

Re: [blink-dev] Intent to Implement & Ship: WebUSB exclusionFilters option in requestDevice()

LGTM1 On 6/21/23 2:32 AM, 'François Beaufort' via blink-dev wrote: Contact emails * fbeauf...@google.com reil...@google.com * Explainer * https://github.com/WICG

Re: [blink-dev] Intent to Implement & Ship: WebUSB exclusionFilters option in requestDevice()

LGTM2 On Wed, Jun 21, 2023 at 7:42 AM Mike Taylor wrote: > LGTM1 > On 6/21/23 2:32 AM, 'François Beaufort' via blink-dev wrote: > > Contact emails > > > * fbeauf...@google.com reil...@google.com > * Explainer > > > * https://github.com/WICG/webusb/pull/233#issue-1760530134 >

[blink-dev] Intent to Ship: CSS text-wrap: pretty

Contact emailsko...@chromium.org ExplainerNone Specificationhttps://drafts.csswg.org/css-text-4/#valdef-text-wrap-pretty Design docs https://docs.google.com/document/d/1jJFD8nAUuiUX6ArFZQqQo8yTsvg8IuAq7oFrNQxPeqI/edit?usp=sharing Summary Adjusts line breaking to avoid a short single word on th

Re: [blink-dev] Intent to Ship: RFC 7616 Digest auth: Support SHA-256, SHA-512-256 and user hashing

I am missing the compatibility picture here. How will this affect existing web pages, and what happens to browsers that do not support this is we add support? /Daniel On 2023-06-20 18:13, Deomid "rojer" Ryabkov wrote: Contact emails roj...@gmail.com Explainer None

[blink-dev] Re: Intent to Ship: CSS text-wrap: pretty

Why was a TAG review not filed? On Wednesday, June 21, 2023 at 7:51:48 AM UTC-7 Koji Ishii wrote: > Contact emailsko...@chromium.org > > ExplainerNone > > Specificationhttps://drafts.csswg.org/css-text-4/#valdef-text-wrap-pretty > > Design docs > > https://docs.google.com/document/d/1jJFD8nAUuiUX

Re: [blink-dev] Intent to Implement & Ship: WebUSB exclusionFilters option in requestDevice()

LGTM3, but please send this as an FYI to the TAG. There's no such thing as a "small feature" in terms of consistency and potential for architectural impact. On Wednesday, June 21, 2023 at 7:44:55 AM UTC-7 Chris Harrelson wrote: > LGTM2 > > On Wed, Jun 21, 2023 at 7:42 AM Mike Taylor > wrote:

Re: [blink-dev] Intent to Ship: Private Aggregation API

On Tue, Jun 20, 2023 at 5:39 PM Rick Byers wrote: > > On Tue, Jun 20, 2023 at 4:51 PM Alex Turner wrote: > >> Contact emailsale...@chromium.org >> >> Explainer >> https://github.com/patcg-individual-drafts/private-aggregation-api >> >> Specification >> https://patcg-individual-drafts.github.io/p

[blink-dev] Re: Intent to Ship: Fenced Frames

Hey all, I'm not going to weigh in on if this should ship right now, but I want to express some disappointment that this design seems to be launching without a way to load from a bundle and a flag for removing the ability to load from the network. We have a lot of use-cases that would benefit f

Re: [blink-dev] Intent to Ship: Iterator helpers

LGTM3 -- 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/chro

Re: [blink-dev] Re: Intent to Ship: Fenced Frames

LGTM1 Thank you for thoroughly working through all the design and specification steps for this feature. Glad to see some positive signals from the TAG about the fundamental design in particular. I agree that Alex's comments are good to answer and investigate for future work, but also they aren't

[blink-dev] Re: Intent to Ship: CSS text-wrap: pretty

Sorry, filed here: https://github.com/w3ctag/design-reviews/issues/864 I thought the previous review covered this, but you're right that it didn't cover other values of `text-wrap`. On Thu, Jun 22, 2023 at 12:25 AM Alex Russell wrote: > Why was a TAG review not filed? > > On Wednesday, June 21,

Re: [blink-dev] Re: Intent to Ship: Fenced Frames

LGTM2 On Wed, Jun 21, 2023 at 11:46 AM Chris Harrelson wrote: > LGTM1 > > Thank you for thoroughly working through all the design and specification > steps for this feature. Glad to see some positive signals from the TAG > about the fundamental design in particular. > > I agree that Alex's comme

Re: [blink-dev] Re: Intent to Ship: Fenced Frames

LGTM3 On 6/21/23 11:53 AM, Rick Byers wrote: LGTM2 On Wed, Jun 21, 2023 at 11:46 AM Chris Harrelson wrote: LGTM1 Thank you for thoroughly working through all the design and specification steps for this feature. Glad to see some positive signals from the TAG about the fundam

Re: [blink-dev] Intent to Ship: Topics API

The spec looks well-written, and I'm dissapointed by the lack of technical feedback from the TAG. Because the TAG doesn't seem to be engaging at the level of platform consistency and quality in this review, I have some questions of the sort I try not to ask (in the hopes that the TAG has those

Re: [blink-dev] Intent to Ship: CustomElementsGetName

Hi, thanks for working on this feature. I'd like to wait for the spec PR to land before approving. On Mon, Jun 19, 2023 at 5:18 PM tkent via Chromestatus < admin+tk...@cr-status.appspotmail.com> wrote: > LGMT1. This is a very small addition to an existi

Re: [blink-dev] Re: Intent to Ship: Fenced Frames

Just a quick note on spec maturity: as spec mentor, I did a thorough review of the spec text, and noted many issues - all small - which have been addressed. As the feature introduces a privacy boundary between two documents with very sensitive one-way control, it is non-trivial but the design is w

Re: [blink-dev] Intent to Prototype: Zstd Content-Encoding

On Wed, Jun 21, 2023 at 3:18 AM Adam Rice wrote: > Drive by question: Given that the codec is going to be in the browser, are >> there plans to surface this up to CompressionStreams? (same question >> applies for Brotli, I suppose) > > > For the zstd Content-Encoding, we will only be linking in t

Re: [blink-dev] Intent to Ship (I2S): Protected Audience

As the spec mentor for this feature I'll offer a spec maturity summary

Re: [blink-dev] Intent to Ship: First-party sets

Is this I2S still using the externally managed JSON blob to identify first party sets, and shipping via Component Updater, i.e. there is not yet a dynamic way to specify First-Party Sets? On Tue, Jun 20, 2023 at 9:35 AM 'Hugo Bärtges' via blink-dev < blink-dev@chromium.org> wrote: > Have we reach

Re: [blink-dev] Re: Intent to Ship: Fenced Frames

Thanks all! (Response inline) On Wed, Jun 21, 2023 at 12:19 PM Joshua Bell wrote: > Just a quick note on spec maturity: as spec mentor, I did a thorough > review of the spec text, and noted many issues - all small - which have > been addressed. As the feature introduces a privacy boundary betw

Re: [blink-dev] Intent to Ship: Topics API

Thanks for the questions Alex. Responses inline: > I don't see a full "considered alternatives" section in the Explainer. What other options were explored for this API and/or design? Yes. Before Topics we had another API, FLoC . We learned early on in the OT process that

Re: [blink-dev] Intent to Ship: RFC 7616 Digest auth: Support SHA-256, SHA-512-256 and user hashing

Hi Daniel, I do not anticipate immediate impact. By and large, this is not currently used because the most popular browser engine doesn't support it. So people just use MD5, as in the bad old days. If we ship this tomorrow, nothing changes: servers still send legacy MD5 challenges, which we contin

Re: [blink-dev] Re: Intent to Ship: overflow:overlay aliases overflow:auto

hi, sry, my mistake: Safari doesn't support overlay scrollbars but Firefox has a native overlay scrollbar since version 100 on all OS. I hope Chromium will do the same or gives us developers the possibility again to overlay scrollbars for a better design. thank you Xianzhu Wang schrieb am Die

Re: [blink-dev] Re: Intent to Ship: overflow:overlay aliases overflow:auto

On Wed, Jun 21, 2023 at 12:32 PM fri tz wrote: > hi, > > sry, my mistake: Safari doesn't support overlay scrollbars but Firefox has > a native overlay scrollbar since version 100 on all OS. I hope Chromium > will do the same or gives us developers the possibility again to overlay > scrollbars for

Re: [blink-dev] Intent to Ship: First-party sets

Hugo: no, we are still examining metrics and evaluating. I will post to this thread when I have updates. David: Yes, this implementation consumes the JSON blob from https://github.com/GoogleChrome/first-party-sets via Component Updater. (There's also an enterprise policy