►
From YouTube: WebPerfWG call 2023 03 16 - Pending Request proposal
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
B
So
my
name
is
Ming
Fargo
and
I'm,
working
on
BF
cache
in
Tokyo,
and
so
I'm
gonna
send
the
pending
request
API.
So
actually
we
have
been
working
on
this
in
the
past
year,
but
it
was
called
pending
B
camp.
In
response
to
recent
discussions,
we
want
to
provide
an
alternative.
Api.
Animated
motivation
is
that
we
would
like
to
provide
a
reliable
way
for
sending
requests
on
page
and
and
the
current
condition
required
user
to
somehow
register
on
one
of
the
visibility
change
event
listener.
B
Over
page
other
page
life
cycle
event
listener,
along
with
either
SMB
account
or
veggie
but
like,
but
this
actually
doesn't
it's
not
quite
reliable
and
we
think
that
we
can
provide
an
API
that
that
the
browser
handle
is
sending
Behavior
and
the
concrete
requirements
are.
Basically.
B
A
B
B
B
We
only
want
to
allow
a
subset
of
the
request
original
request
field
to
be
update.
Datable
here.
B
Accordingly's
measure
will
transform
the
pending
request,
object
into
the
a
regular
fetch
request
object
and
there
is
a
send
after
being
background
timeout,
as
mentioned,
if
setting
this
time
out,
it
will
allow
a
browser
to
send
this
earlier
when
entering
the
children,
disability
state
and
with
the
pending
requests
user
will
be
able
to
update
the
headers
or
UI
or
party
operation
requests.
A
Sorry,
meaning
I
just
want
to
interrupt,
and
just
say
one
thing
just
so
that
people
aren't
might
be
confused
like
this.
Api
is
very
similar
to
what
we
had
been
proposing
before,
which
were
the
pending
Beacon
things
that
you
would
create,
so
we've
moved
away
from
creating
an
object
that
manages
the
whole
thing
to
creating
a
request
that
goes
into
fetch.
A
So
it's
if
you're
thinking
this
sounds
familiar.
It
is,
but
it's
not
that's
the
the
big
difference
between
what
we
did.
B
Sorry
I
forgot
to
mention
yeah.
It
was
previously
a
group
of
newcasts
we
proposed,
but
now
it's
a
surprise
of
the
request.
The.
A
B
And
specifically,
the
pending
request
object
in
a
Constructor.
It
takes
a
pending
request.
It
needs.
We
only
want
to
allow
personalizing
these
fields
for
all
the
other
fields
like
keyboard
I
or
we
will
underlying
issued
enforcing
other
request
fields.
B
So
I'm
going
to
some
examples
here.
The
first
one
is:
if
you
want
to
queue
a
requests
to
be
sent
on
page
discussed,
you
can
just
create
a
new
pending
request,
object
and
just
call
the
page
API
and
know
that
the
promise
may
never
resolve
as
the
page.
If
you
keep
opening
a
page
here,
then
it
won't
be
sent
out
and
you
send
for
the
Post
request.
B
B
B
And
here
is
a
more
concrete
example:
first,
we
create
a
get
pending
request
and
kill
it
into
a
browser,
and
we
may
collect
some
data
and
we
check
if
the
request
is
still
pending.
If
so,
we
update
the
data
into
the
spending
request,
URL
and
if
it's
not
pending,
which
means
that
requests
might
have
been
sent
out
and
we
will
need
to
create
a
new
another
new
pending
request
and
queue
with
the
fetch
API
and
at
the
end,
we
can
also
export
to
send
it
all
immediately.
B
B
Okay,
anyway,
first
we
want
to
get
feedback
on
the
API
ship
and
hopefully
get
agreements
is
to
unblock
our
professor.
B
To
unblock
our
version
like
either
implementation
or
launching
so
yeah
I'm,
not
sure
if
the
web
keyboards
are
here
or
not
yeah,
so
let
me
stop
recording
and
we
can
move
on
to
the
questions.
Please.