Re: [blink-dev] Re: Native support of Windows SSO in Chrome

I have some questions. - Is the proposal that Chrome detects such a redirect and sends an authentication request to IDP? - Is there at most one IDP for a profile? - How is IDP registered to Chrome? Thanks, On Fri, Sep 24, 2021 at 6:18 AM Owen Min wrote: > +people who may be interested in th

Re: [blink-dev] Intent to Ship: HTMLScriptElement.supports(type) method

On Fri, Sep 24, 2021 at 5:42 AM Tsuyoshi Horo wrote: > Thank you very much for LGTMs! > > > >> RisksInteroperability and Compatibility >>> >>> This method provides a synchronous way of feature detections. But for >>> unsupported browsers, developers need to use an asynchronous way as >>> discusse

Re: [blink-dev] Intent to Ship: HTMLScriptElement.supports(type) method

Thank you very much for LGTMs! > RisksInteroperability and Compatibility >> >> This method provides a synchronous way of feature detections. But for >> unsupported browsers, developers need to use an asynchronous way as >> discussed at https://github.com/WICG/import-maps/issues/171. >> > > Is it

[blink-dev] Intent to Ship: WebAssembly Content Security Policy

Contact emailsad...@chromium.org f...@chromium.org Explainer https://github.com/WebAssembly/content-security-policy/blob/master/proposals/CSP.md Specificationhttps://github.com/w3c/webappsec-csp/pull/293 Design docs https://github.com/WebAssembly/content-security-policy/blob/master/proposals/CSP

[blink-dev] Re: Native support of Windows SSO in Chrome

+people who may be interested in this. On Thursday, September 23, 2021 at 12:21:51 PM UTC-4 Sasha Tokarev wrote: > Hi all, > > I have a proposal to integration with Windows SSO in Chrome. > > Currently Windows has ability to join device to cloud identity, like AAD, > MSA. When a device is joined

[blink-dev] Intent to Ship: HTTP->HTTPS redirect for HTTPS DNS records

Contact emails erico...@chromium.org Explainer None Specification https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-svcb-https-07 Summary Query DNS for HTTPS records (alongside traditional A and queries). When a website has deployed an HTTPS DNS record and Chrome receives it, Chrom

Re: [blink-dev] Intent to Ship: HTMLScriptElement.supports(type) method

On Thu, Sep 23, 2021 at 3:15 PM Alex Russell wrote: > LGTM3 > > Would like to see a concrete plan for expanding this method to other > media-loading elements (,

Re: [blink-dev] Intent to Ship: HTMLScriptElement.supports(type) method

LGTM3 Would like to see a concrete plan for expanding this method to other media-loading elements (,

Re: [blink-dev] Intent to Extend Origin Trial: Conversion Measurement API (Attribution Reporting API)

LGTM3 to extend to 95 On Tuesday, September 21, 2021 at 7:26:16 AM UTC-7 Chris Harrelson wrote: > LGTM2 > > On Mon, Sep 20, 2021, 10:38 PM Yoav Weiss wrote: > >> O(10) sounds manageable in case we want to change course, so that reduces >> the burn-in risk. >> Since this is an atypical OT extens

Re: [blink-dev] Re: Intent to Deprecate and Remove: U2F API (Cryptotoken)

Thanks for clarifying! On Thu, Sep 23, 2021 at 7:45 PM Martin Kreichgauer wrote: > Thanks! Just to be clear, the deprecation trial is beginning with M95, but > it would only be *required* by M98 when we disable the U2F API by > default. M104 is where we plan to delete the API, so M103 would be t

Re: [blink-dev] Re: Intent to Ship: Web Serial API

Is this ready for production use now or is it still experimental? Will the Spec change? Thanks! Nick On Wednesday, January 13, 2021 at 8:40:09 PM UTC-6 rei...@chromium.org wrote: > Thanks. Over the holidays I forgot that he'd already approved it. > > Reilly Grant | Software Engineer | rei...@

Re: [blink-dev] Intent to Extend Origin Trial: Trust Token API

With a gap, LGTM2 /Daniel On 2021-09-23 14:14, Yoav Weiss wrote: As this is an atypical OT, this requires 3 LGTMs. *LGTM1* to extend to M101, conditional on a 2 weeks gap to demonstrate that there's no premature reliance on the API. On Wed, Sep 22, 2021 at 10:26 PM Steven Valdez

Re: [blink-dev] Intent to Ship: HTMLScriptElement.supports(type) method

LGTM2 /Daniel On 2021-09-23 12:06, Yoav Weiss wrote: LGTM1 On Wed, Sep 22, 2021 at 5:21 AM Tsuyoshi Horo > wrote: Contact emails h...@chromium.org Explainer https://github.com/horo-t/explainers/blob/mai

Re: [blink-dev] Re: Intent to Deprecate and Remove: U2F API (Cryptotoken)

Thanks! Just to be clear, the deprecation trial is beginning with M95, but it would only be *required* by M98 when we disable the U2F API by default. M104 is where we plan to delete the API, so M103 would be the last release where the deprecation trial is functional. On Thu, Sep 23, 2021 at 5:18 A

Re: [blink-dev] Why is h264 encoding on Windows is limited to 1920x1088px?

bcc:blink-dev cc: media-dev +chunbo@intel.com +eug...@chromium.org GPU accelerated encode will use platform specific libraries (Mac: VideoToolbox, Windows: MediaFoundation). The windows limit was introduced back in 2017 in this change . When that

[blink-dev] Why is h264 encoding on Windows is limited to 1920x1088px?

I was trying out WebCodecs in v94 and noticed in chrome://gpu that on Windows the h264 encoding is limited to 1920x1088px: Encode h264 baseline0x0 to 1920x1088 pixels, and/or 30.000 fps On MacOS it goes to 4096x2160. Why is that? I thought that the underlying implementation was using ffmpeg

[blink-dev] Native support of Windows SSO in Chrome

Hi all, I have a proposal to integration with Windows SSO in Chrome. Currently Windows has ability to join device to cloud identity, like AAD, MSA. When a device is joined to a cloud identity provider (IDP), it would be great if I'm as a user do not need enter credentials, when I'm using a servic

Re: [blink-dev] Intent to Experiment: Conditional Focus

LGTM to experiment M96-M99 inclusive On Thu, Sep 23, 2021 at 4:04 PM Elad Alon wrote: > m99, inclusive. So four milestones in total. > > On Thu, Sep 23, 2021 at 3:53 PM Yoav Weiss wrote: > >> >> >> On Thu, Sep 23, 2021 at 3:00 PM Elad Alon wrote: >> >>> Might be good to move this to WICG to fa

Re: [blink-dev] Intent to Experiment: Conditional Focus

m99, inclusive. So four milestones in total. On Thu, Sep 23, 2021 at 3:53 PM Yoav Weiss wrote: > > > On Thu, Sep 23, 2021 at 3:00 PM Elad Alon wrote: > >> Might be good to move this to WICG to facilitate contributions (given >>> support >>>

Re: [blink-dev] Intent to Experiment: Conditional Focus

On Thu, Sep 23, 2021 at 3:00 PM Elad Alon wrote: > Might be good to move this to WICG to facilitate contributions (given >> support >> ). >> > > WICG issue #37 asked for > this to be

Re: [blink-dev] Intent to Ship: Auto-expand details elements

On 9/23/21 8:19 AM, Yoav Weiss wrote: On Thu, Sep 23, 2021 at 9:25 AM Thomas Steiner > wrote: Not sure this was discussed before, but could a new boolean attribute that opts the element in to the new behavior be the answer? At the risk of jinxing UseCounte

Re: [blink-dev] Intent to Experiment: Conditional Focus

> > Might be good to move this to WICG to facilitate contributions (given > support > ). > WICG issue #37 asked for this to be adopted by the WICG. (The same partner supported it t

Re: [blink-dev] Intent to Experiment: Conditional Focus

On Wed, Sep 22, 2021 at 2:16 PM 'Elad Alon' via blink-dev < blink-dev@chromium.org> wrote: > Contact emailselada...@chromium.org > > Explainer > https://github.com/eladalon1983/conditional-focus/blob/main/README.md > > Specificationhttps://eladalon1983.github.io/conditional-focus/ > Might be good

Re: [blink-dev] Intent to Ship: Auto-expand details elements

LGTM1 On Thu, Sep 23, 2021 at 12:03 AM PhistucK wrote: > Not sure I completely agree, so, not so "right". :) > Using / for "accordions" is kind of the prescribed way > to do this. I do not think encouraging other, maybe less accessible, > semantic or simple ways is so "right". > And this is brea

Re: [blink-dev] Intent to Ship: Auto-expand details elements

On Thu, Sep 23, 2021 at 9:25 AM Thomas Steiner wrote: > Not sure this was discussed before, but could a new boolean attribute that > opts the element in to the new behavior be the answer? > > > It seems like an opt-in would significantly diminish the user value of this feature, for all existing

Re: [blink-dev] Re: Intent to Deprecate and Remove: U2F API (Cryptotoken)

So IIUC, the deprecation trial would run from M98-M104. That seems like a reasonable time period to give to folks and enable them to adjust. Still LGTM. On Wed, Sep 22, 2021 at 10:32 PM 'Martin Kreichgauer' via blink-dev < blink-dev@chromium.org> wrote: > Dear blink-dev, > > I wanted to provide a

Re: [blink-dev] Intent to Extend Origin Trial: Trust Token API

As this is an atypical OT, this requires 3 LGTMs. *LGTM1* to extend to M101, conditional on a 2 weeks gap to demonstrate that there's no premature reliance on the API. On Wed, Sep 22, 2021 at 10:26 PM Steven Valdez wrote: > Contact emails > > sval...@chromium.org, privacy-sand...@chromium.org >

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

On Fri, Aug 13, 2021 at 7:04 PM 'Ionel Popescu' via blink-dev wrote: > https://wicg.github.io/eyedropper-api/ It seems some security issues were opened against this document post LGTMs. And after these issues were raised there hasn't been a lot of activity on the repository which makes me wonder

Re: [blink-dev] Intent to Ship: HTMLScriptElement.supports(type) method

LGTM1 On Wed, Sep 22, 2021 at 5:21 AM Tsuyoshi Horo wrote: > Contact emails > > h...@chromium.org > > > Explainer > > https://github.com/horo-t/explainers/blob/main/script_element_supports.md > > > Specification > > https://html.spec.whatwg.org/multipage/scripting.html#dom-script-supports > > D

Re: [blink-dev] Re: Intent to Ship: Reporting API: Isolate reports per-document and support the Reporting-Endpoints header

Still LGTM On Tue, Sep 21, 2021 at 10:48 PM Ian Clelland wrote: > In an exciting last minute turn of events, I've made progress on fixing > one of the last outstanding bugs regarding our implementation of the new > Reporting API spec, and I'd like to amend this intent to include that > change, b

Re: [blink-dev] Intent to Ship: Auto-expand details elements

Not sure this was discussed before, but could a new boolean attribute that opts the element in to the new behavior be the answer? -- 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, se