Re: [blink-dev] Re: Intent to Ship: Propagate request origin and redirect chain in passthrough service workers.

This change broke a SingleSignOn login on the FOSS software Discourse. We have a flow like: 1. User visits forum.siteA.com, click login 2. Gets redirected to idp.siteB.com 3. Fills login details 4. Gets redirected to forum.siteA.com/session/sso_login?parameters 5. Gets redirected to forum.siteA.

[blink-dev] Intent to Prototype: Focusgroup

Contact emails bebea...@microsoft.com Explainer https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/Focusgroup/explainer.md Specification Summary The Focusgroup featur

RE: [EXTERNAL] Re: [blink-dev] Re: Intent to Ship: Pickling for Async Clipboard API

Hi Philip, In the worst case we will be able to merge the pickling API changes into the EditingWG repo. We have a meeting this Friday with the Firefox folks to discuss the Pickling API as they were also interested in the proposal

Re: [blink-dev] Question on getting pixels from blink/renderer/modules/accessibility.

On Wed, Jan 12, 2022 at 8:06 AM Ramin Halavati wrote: > Thank you very much Philip. I will write a 1-pager on this discussion for > posteriority and will proceed with the inside blink approach. > > Just as the concluding question, I have a draft CL on it ( > crrev.com/c/3370381). Would you sugges

Re: [blink-dev] Intent to Ship: Origin Isolation By Default / Deprecate document.domain

Hey Daniel! While searching for this intent review, I stumbled upon https://developer.chrome.com/blog/immutable-document-domain/ That's a useful piece of documentation! Thanks +Eiji Kitamura!! This intent was just discussed at the API owner meeting (where Chris, Rego, Daniel, Philip, Alex, Mik

Re: [blink-dev] Intent to Prototype: MediaRecorderErrorEvent API

This seems like a problematic specification. They should just use ErrorEvent, instead of creating a new class that is basically identical. I have filed https://github.com/w3c/mediacapture-record/issues/211 and hope we can go that route instead. On Wed, Jan 12, 2022 at 11:59 AM Imranur Rahman wrot

[blink-dev] Intent to Prototype: MediaRecorderErrorEvent API

Contact emailsir.shi...@gmail.com ExplainerNone Specificationhttps://w3c.github.io/mediacapture-record/#errorevent-section Summary MediaRecorderErrorEvent is fired when Media Recording API faces an error. This API will enable developers to debug more conveniently when an exception occurs in Med

Re: [EXTERNAL] Re: [blink-dev] Re: Intent to Ship: Pickling for Async Clipboard API

Hi Anupam, Could https://w3c.github.io/gamepad/extensions.html be a model to follow here? I think it's important to write down (and test) what you intend to ship in something that looks like a spec. If doing that in the EditingWG doesn't seem tractable, then the WICG is also an option. This seems

Re: [blink-dev] Question on getting pixels from blink/renderer/modules/accessibility.

Thank you very much Philip. I will write a 1-pager on this discussion for posteriority and will proceed with the inside blink approach. Just as the concluding question, I have a draft CL on it ( crrev.com/c/3370381). Would you suggest that I take a (possibly simplified) copy of the DataTransfer::N

Re: [blink-dev] Intent to Ship: CORS non-wildcard request-header

Hi Yoav, Thank you for the suggestions. I'll try to add UKM. > One other question that came up: Is the usage related to developers adding the "Authorization" header on their own, or is it something the browser sends under certain circumstances? (e.g. when receiving 401 responses with "WWW-Autenti

Re: [blink-dev] Intent to Ship: Allow infinity, -infinity and NaN in CSS calc()

On Tue, Jan 11, 2022 at 10:34 PM Emilio Cobos Álvarez wrote: > > Hi Seokho, > > Curious, how do I enable this in Canary? I tried but the experimental > features doesn't seem to enable this (unless I'm holding it wrong). To answer this question -- you can enable individual runtime-enabled features

Re: [blink-dev] Intent to Ship: HTMLInputElement showPicker()

On Wed, Dec 15, 2021 at 5:59 PM Alex Russell wrote: > LGTM3 > > On Wednesday, December 15, 2021 at 7:51:30 AM UTC-8 Yoav Weiss wrote: > >> LGTM2 >> >> On Wednesday, December 15, 2021 at 4:18:50 PM UTC+1 Mike West wrote: >> >>> LGTM1. >>> >>> Given that this codifies existing Chrome behavior in a