►
From YouTube: WebPerfWG call 2023 03 16 - AsyncContext
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).
A
A
A
Single
context
to
with
the
usage
on
the
web
performance
and
the
open
temperature
case
on
the
web-
and
this
is
a
very
quick
introduction,
so
that
we
can
discuss
the
usage
more
in
detail,
and
this
in
context
is
a
ecos
building
API.
It
can
implicitly
propagate
values
through
code
Stacks,
preserving
their
values
across
async
boundaries.
This
async
contacts
cost
has
three
methods,
and
the
first
is
the
static
method
wrap.
A
When
we
are
tracing
soft
navigations
like
say
when
I
use
the
interact
with
with
the
page
and
the
interaction
initiated
a
subsequent
async
operations,
it
is
critical
for
us
to
to
when,
when
the
HTML
is
being
updated,
we,
it
is
critical
for
us
to
know
which
operation
initiated,
which
use
the
interaction
initiated,
initiated
these
chains
of
interaction.
A
A
There
can
be
also
used
for
for
task
at
transitive
task,
attribute
attributes
like
say,
runtime
scan
schedule,
tasks
with
priorities.
However,
the
task
priorities
attributions
is
not
transitive
at
this
moment,
so
we
have
to
perform
yield
or
weight
to
to
propagate
the
priorities.
A
A
And
it,
and
in
the
application
monitoring
libraries
like
opportunity,
we
are
chasing
the
open
energy
saves
the
their
tracing
spans
in
in
the
async
context,
and
they
can
choose
the
expense
when
they
need
to
determine
what
started
this
change
over
interaction
and
those
libraries
cannot
introduce
the
developers
developer
apis
for
stimulus
monitoring.
So
they
cannot
introduce
any
additional
parameters
to
existing
libraries
so
for
seamless
in
monitoring
they
can
use
the
as
in
context
and
the
to
to
propagate
their
expense
and
and
to
they
can
use
the
async
contest
to
propagate
it.
A
A
A
With
this
in
context,
applications
can
get
obtain.
The
native
support
with
the
I
think
a
weight
syntax
with
on
the
context
propagation,
and
this
is
very
fundamental-
to
open
temperature
since
Optometry
instruments,
user
interactions
with
document
element
elements
and
then
connect
the
subsequent
Network
request
and
the
history
State
changes
they
typically.
A
Promise
continuation
like
say
we
fetch
the
neck
first
address
and
in
the
response
we
can
continue
to
fetch
another
network
network
address
and
and
other
dimension
instruments.
The
patch
apis
and
the
grid
stands
for
each
patch
invocation
and
the
the
invocation.
The
span
must
be
nested,
and
so
they
will
need
to
determine
the
initiator
of
the
vegetable
foreign.
A
In
this
can
be
where
exist
can
be
seamless
without
user
code
changes
and
it
can
generate
dispense
like
show
in
the
example,
the
critical
event
initiate
the
first
initiate.
A
Also
other
damages
supports,
can
instrument,
run
tasks,
collect,
don't
ask
timing
entries
with
the
help
or
loan
tax
loan
tasks.
Api
I
have
a
tracking
long
tasks
effectively.
We
need
the.
A
We
don't
need
the
ability
to
chase
to
tell
whether,
where
a
task
was
spawned
from.
However,
currently
it
is
not
able
to
associate
a
long
task
time
entries
with
the
initiating
Tracy
Trace
spans.
Let's
say
in
the
example:
we
don't
have
any.
A
Is
roughly
creating
a
new
performance
Observer
in
the
performance
of
Observer?
There
is
no
way
to
tell
whether
or
not
my
task
function
is
called
in
a
chasing
span.
A
A
Similarly,
resource
timing
entries
observation
has
the
similar
problems.
We
cannot
tell
exactly
the
initiative
of
the
of
an
resource
time
entries
and
of
quantity
of
Elementary
instruments.
The
Apache
API
with
the
resource
timing,
API.
A
With
an
is
not
an
intuitive
approach
to
associate
the
resource
time
entries
with
the
fetch,
with
the
fetch
space
like
in
the
example,
we
are
currently
searching
finding
space
for
each
for
each
resource
entries
with
their
with
guessing
their
names
or
and
their
starting
times
to
see.
If
even
span
is
the
initiator
and
performance
resource
timing
entries.
A
Is
there
yeah
yeah,
let
me
start
the
recording
and
we
can
move
on
to
questions.