Contact emailstcap...@chromium.org
ExplainerNone
Specification
https://w3c.github.io/IntersectionObserver/#dom-intersectionobserver-scrollmargin
Summary
Intersection Observer scrollMargin allows developers to observe targets
inside nested scroll containers that are currently clipped away by the
Contact emails...@chromium.org
ExplainerNone
Specificationhttps://tc39.es/proposal-promise-with-resolvers
Summary
Promise.withResolvers is a static methods that returns a new Promise along
with its resolver functions, i.e. `const { promise, resolve, reject } =
Promise.withResolvers()`. This is
Given that this change is not web-exposed nor user visible, an LGTM is not
required.
Nevertheless, a non-required LGTM to experiment with this!! :)
On Thu, Sep 14, 2023 at 5:18 PM Kyra Seevers wrote:
> Thanks for the questions!
>
> > Does phase 1 have any web-exposed or user-visible changes?
>
Thanks for the questions!
> Does phase 1 have any web-exposed or user-visible changes?
No. Phase 1 has no user-visible changes - only changes to the
HistoryDatabase backend.
> Not a blocker for the experiment, but might be worthwhile to file
positions early.
SGTM thank you.
> How long are you pl
Hi,
I hope you are well.
I have been trying o get WebSerial working in my React app. It works fine
in ideal conditions. However, if the serial device spams the serial port
with a lot of data very fast before serialport.connect() happens, I get
"BufferOverrunError".
I increased the buffer size
On Thu, Sep 14, 2023 at 11:02 AM Kyra Seevers
wrote:
> Intent to Experiment: Partitioning :visited links history Phase 1 (Begin
> storing triple partition keys for :visited links)
>
> Contact emails
>
> kyraseev...@chromium.org
>
> Explainer
>
> https://github.com/kyraseevers/Partitioning-visited
Intent to Experiment: Partitioning :visited links history Phase 1 (Begin
storing triple partition keys for :visited links)
Contact emails
kyraseev...@chromium.org
Explainer
https://github.com/kyraseevers/Partitioning-visited-links-history
Specification
None yet - currently getting feedback fr
LGTM3 as not subject to blink process. But thanks for the heads up!
On Wed, Sep 13, 2023, 5:50 p.m. Stephen Mcgruer
wrote:
> Thanks Mike! We were following through on the I2S process because we did
> an I2E for this feature as a way to let folks verify that the UX change
> wouldn't cause regres
