►
From YouTube: SES Meeting: ShadowRealm Uncaught and Unhandled
Description
Today we discussed our advice to the HTML standard for desirable ways to allow programs to trap exceptions and rejections in a shadow realm.
A
B
B
Caridy:,
you
might
invoke
that
function
at
any,
given
time,
and
you're
free
to
use
it.
try
to
catch
on
the
inquiry,
or
to
capture
the
error,.
If
there
are
occur.
and
then,
of
course,,
you're
gonna
get
a
copy
of
that
or
not
the
actual,
error,
and
so
on..
So
all
that
works
wonderful.,
no
problem
there.
B
B
B
B
Caridy:
from
the
actual
shot
around
off
the
resolve.
and
then
the
error,
occurred.
you're
gonna
get
a
copy
of
it.,
but
you
can
capture
that.,
that's
one
thing.,
so
you,
as
they
create
or
the
shadow
wrong,
can
listen
for
error.
That
happened
there
that
I'm
not
captured
by
the
by,
the
code
running
side
of
the
shutter
on
that's
one
approach.
C
B
B
Caridy:
otherwise.
every
chat
or
wrong
in
terms
of
you,
create,
create,.
You
have
to
put
some
sort
of
condition:
there,
some
sort
of
provision
to
capture
there
and
then
for
what?
that
or
somehow
in
the
in
kuwait
around.,
but
that
makes
it
a
little
bit
more
difficult..
You
have
something
global.,
then
you
just
do
that.
Thing.
B
B
B
Caridy:,
it's
just
a
matter
of
caridy:
surfing
these
errors
that
are
happening
in
chat
wrongs
into
the
main
window.,
the
root
window,,
as
we
call
in
the
spec,,
so
they
can
get
a
copy
of
that,
and
then
everything
should
be
fine..
The
event
that
you
get
is
from
the
main
window
anyways.,
so
you
don't
necessarily
have
to
expose.
B
B
B
B
B
B
C
C
C
C
C
C
C
Mathieu
hofman:
so
there's
already
a
mechanism
in
defining
on
the
web
a
priori
on
the
web,
where
you
can
listen
for
global
or
in
your
agents.
in
this
in
that
case,,
for
your
worker.,
and
if
that
asians
and
handle
them.
it
will
be.
We
stop
re-thrown,,
but
it's
re
dispatched
on
on
on
the
parent,
agents.
C
C
C
C
C
C
C
Mathieu
hofman:
the
host
will
report
that
using
the
the
regular
host
mechanisms,
and
there's
no
way
to
wrap.,
but
I
mean,,
I
guess
you
could
wrap
the
finalization
registry
and
wrap
all
the
call
by
handlers.,
but
it
it.
it
becomes
like
one
of
those
virtualization
questions
again..
How
do
you
make
sure
you
can??
You
can
cash
all
the
errors
that
would
have
been
enandled.
and
and
report
them.
B
B
B
B
C
C
C
C
B
B
A
A
A
B
B
C
C
C
A
C
B
B
A
A
C
A
B
B
B
B
B
B
B
Caridy:,
which
is
a
promise.
caridy:,
but
if
we
open
that
up,,
then
you
might
be
able
to
get
promises
on
the
other
side..
I
can
do
the
the
work
for
you
without
breaking
the
branch.,
the
invariance
that
we
have
for
the
for
the
call
of
boundary,,
and
that
opens
the
door
for
this
second
layer
of
all
errors
and
control,,
and
so
on.
C
C
C
C
C
C
C
C
C
C
C
C
C
B
B
B
B
B
C
B
B
B
C
B
A
A
C
A
A
A
A
Kris
“cowbert”
kowal:
perpetually
that
the
the
choice
between
having
to
just
like
all
right.
well,,
we're
gonna,
have
to
just
drain
the
during
the
event,
with
an
with
a
no
catch
for
every
promise.
We
create,,
because
the
reality
and
a
distributed
semantics
is
that
you're
not
going
to
observe
these
things.
Locally.
you're,
going
to.
A
A
A
A
A
A
A
C
C
C
B
B
B
B
B
C
C
C
Mathieu
hofman:
global
objects
like
the
the
doing
mathieu
hofman:
host
global
object
receiver
as
a
receiver..
It
works,,
if
you
call
it,
with
any
other
global
object.,
it
does
not,.
This
is
a
problem
of
something
we've
experienced
in
the
session.
This
has
shame.
one
of
the
limitation
because
of
using
with
blocks.
when
you
call
a
method
of
the
global.
C
Mathieu
hofman:,
the
with
behavior,
is
to
call
user.
The
scope
object
has
the
receiver.,
so
that
means
basically
any
method,
behaves
like
a
non-strict
method
for
the
receiver.
there,
it
gets,
or
or
scope
object,,
which
obviously
doesn't
match
any
more
the
the
original
global
objects..
So
if
you
take
fetch,
for
example,,
put
it
in
a
compartment,
global
object,
scope,
and
then
call.