Thank you all for your great support!
There's no more outstanding questions or bugs in my mind that might block
shipping this, but I need to get 3 LGTMs from you to process the final ship.
Is that possible we could cherry-pick it to M96? Otherwise we have to wait
about 4 months for M98 stable,
Yes. The only use case of respondWithNewView() is when you've transferred
the ArrayBuffer and so you can't use respond(). Most people will never need
it.
On Thu, 14 Oct 2021 at 01:59, Reilly Grant wrote:
> This is somewhat of a tangent but I'm curious what the use case for
> respondWithNewView()
This is somewhat of a tangent but I'm curious what the use case for
respondWithNewView() is when it seems like the "new" view can only be the
existing view but shorter. It seems equivalent to calling
respondWith(newView.byteLength).
Reilly Grant | Software Engineer | reil...@chromium.org | Google C
*Contact emails*
rid...@google.com
*Explainer*
Add the authenticator attachment (platform/cross-platform) used during both
registration and authentication to the public key credential payload
returned from the browser to the RP/relying party (website/application etc).
This feature enables the
Hi all,
*(If you do not work with readable byte streams, you can ignore this.)*
We have recently submitted some CLs for updating readable byte streams in
the Blink Implementation based on the latest spec changes in the Streams
API standard. These updates fix various issues related to readable byt
It does seem worth trying to ship this given the lack of (known) bugs,
but maybe we should consider waiting until M98 to avoid sites needing to
deploy fixes during the holiday season, assuming a few weeks of latency
for bug reports.
On 10/13/21 9:18 AM, Philip Jägenstedt wrote:
Thanks for exp
Thanks for explaining this, Rakina, I definitely didn't get the whole
context on my first pass.
In particular the fact that current behavior matches Firefox is a
strong reason to not make any further changes.
Wanming, are you aware of any other outstanding questions or bugs that
might crop up if
I had a quick chat with Philip about whether we want to fix
crbug.com/1209717 or not, and I think we don't need to fix that bug for
shipping this.
In the bug, the code expected a same-document history navigation (and its
scroll restoration) would happen synchronously, so any scroll changes that
hap
