►
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
B
B
C
C
B
B
E
B
F
B
C
G
H
H
B
G
B
F
H
H
H
G
G
J
G
D
L
G
So
we
check
box
in
issue
62
when
we
initially
transitioned
into
CR
in
2016.
We
check
boxed
our
privacy
security,
but
we
ceiling
I,
don't
know
that
we
had
a
ping
with
you,
my
friend
there.
It
is
so
we
he
did
announce
and
send
it
through
for
whatever
view,
so
the
Nessie's
team
kind
of
feels
like
we
should
send
it
back
through.
B
M
B
Was
demoted
because
it
didn't
have
been
like
supported
entry
types
and
we
concluded
that
we
need
to
add
a
bunch
of
features
in
order
to
make
this
feature
complete
and
enable
developers
to
actually
use
performance
observer.
So
one
is
the
supported
entry
types
and
the
other
is
options
for
different,
like
a
performance
observer
like
not
just
have
an
array
but
have
different
parameters
for
each
and
retighten
so
that
long
tests
and
have
different
parameters
than
resource
Lana
for.
B
B
B
F
B
P
B
G
P
L
B
B
So
one
of
them
is
just
to
align
the
town
of
the
finishing
with
course,
when
it
comes
to
cross-origin
redirects,
and
this
is
I
have
a
nobility
are
for
that.
That
will
actually
talk
about
later
and
then
be
more
explicit
about
some
resources
and
coming
from
style
sheets
that
yeah.
We
can
talk
about
that
issue
later
as
well,
but
when
it
comes
to
tests,
we
have
a
bunch
of
reds
and
yellows.
B
So
when
it
comes
to
tests,
we
have
the
test
that
is
related
to
entries
from
course
cross-origin
CSS
patches,
and
that
is
one
that
Chrome
and
Firefox
for
both
failing.
This
is
something
that
you
need
to
implement.
This
is
also
something
that
will
potentially
be
extended
with
one
of
the
issues,
because
one
of
the
issues
is
to
have
the
definition
also
applied
to
descendants
of
those
are
sorts.
B
So
if
I
have
a
no
core
CSS,
that
is
importing
a
CSS
that
is
importing
more
and
then
an
image
that
all
of
those
need
to
be
excluded,
and
this
is
something
that
will
need
to
a
define,
Chris
I
couldn't
find
precise
language
to
define
that,
but
maybe
we'll
talk
about
it
later
and
the
tests
that
you
know
it
goes
beyond
the
first
level
that
basically
the
exclusion
beyond
the
first
level
so
those
this
wool.
That's
when
we
change.
B
B
So
don't
know
the
buffer
limits
were
already
bombed
out,
at
least
in
the
recommended,
but
they
can
still
become
full.
So
all
the
comfort
full
logic
is
is
one
of
the
things
that
we're
changing,
lust
here
and
and
I
think
when
you've
had
significantly
more
failing
tests,
both
like
the
Firefox
and
Safari
side,
but
it
would
still
be
great,
basically
infighting
yeah.
If
we're
looking
for
for
each
of
those
cases,
we
have
that.
B
B
B
E
B
Q
B
B
G
B
C
G
B
B
G
L
B
B
Not
what
we
thought
we
would
be
or
not
what
we
certainly
wouldn't
be,
but
anything
free.
So
we
need
to
basically
Boris
wants
us
to
redefine
the
type
based
on
the
like
negative
of
documents
and
then
have
document
knows
what
the
resource,
what
the
navigation
type
is.
So
we
probably
need
to
move
some
of
the
Phoenicians
to
HTML
and
then
hang
it
off
of
there.
It
doesn't
seem
like
something
that
would
impact
much
real-world
usage.
H
G
E
F
F
I
G
F
G
G
I
G
O
B
B
B
O
B
The
one
issue
that
will
be
more
work-
and
that
came
in
more
recently
is
an
issue
for
Marco's,
basically
saying
that
we
rely
on
a
bunch
of
HTML
things
that
are
not
exported.
The
response
from
HTML
is,
basically,
they
shouldn't
be
exported.
A
patient's
ability
should
PR
hooks
into
HTML
and
then
use
them
yeah.
You
should.
E
B
G
My
review
and
a
lot
of
her
because
we
are
making
edits
so
the
thing
that
we're
changing
on
page
visibility
is
weird:
it's
the
the
change,
we're
making
is
shift
to
add
the
ability
to
include
occlude
and
I
think
what
we
decided
is
that
was
a
minor
editorial
change,
as
opposed
to
a
something
along
those
lines.
Just
by
recall,
it's
been
a
while,
since
I
actually
looks
but
a
glance
up
the
key.
Our
document.
G
Hi
yeah
tier
2
is
super
stuff
like
up
to
is
it's
like?
Let's
improve
it
lets
a
inlet
add
on
visibility,
change.
This
was
from
you
know,
over
2017,
and
actually
the
shift
most
you
may
is
like
that's
mostly
years.
No
more
that
so
that's
what
was
in
here,
I
think
what
we
decided
was
that
occlusion
was
not
sufficient
to
go
to
hell
3
and
that
we
were
going
to
do
an
edit
or
update
kind
of
like
the
proposal
today
and
Philippe
said:
yeah,
that's
fine,
and
so.
G
G
You
know
because
it
was
also
a
main:
not
a
must
occlusion,
it's
the
hey.
If
you
wish
you,
as
you
may
allow
the
change
of
the
patrons
ability
to
hidden
when
actuate
included,
so
in
terms
of
special
bra
that
previously
worked
still
work,
yeah
right,
it
adds
new,
many
yeah.
So
that
was
the
reason
it
so
I
think
we
should
follow
up
with
Philippe
de
mature.
We
don't
need
to
quite
revealing
up
okay,
so
the
a
here.
B
D
B
G
One
visibility
changed
so
what
we
were
just
discussing
earlier
myself
about
the
lifecycle
guidance
for
lifecycle
shifts
on
the
web
and
on
visibility.
Change
is
one
of
the
api's
that
we
have
been
suggesting.
People
use
to
do
their
life
cycle
changes
and
currently
Safari
seems
to
be
feeling
the
unvisible
to
change
yeah.
Is
it
just
like
he?
If
the
timeouts
here
I.
J
B
G
Bottoms
and
what
we
found
was
that
there
were
sites
were
doing
all
kinds
of
happy
things
to,
let's
say,
handle
the
fact
that
that
you
couldn't
wasn't
firing
this,
and
so
one
of
the
conversations
we
had
three
years
ago
or
whatever
was
to
enable
us
to
give
the
singing
ends
to
webpages
for
how,
when
to
save
content
and
really
make
the
lifecycle
solid,
the
unvisible
they
changed.
That
is
super
important
to
have.
J
To
go
accountable
emphasizes
a
little
bit,
the
only
good
cross
cross
a
way
to
detect
all
the
logical
changes
is
because
of
those
are
bugs
another
brother
book
as
well.
When
the
paint
is
being
closed,
you
have
to
listen
to
both.
Is
it
really
change
and
before
a
load
and
with
something
before
unload
brings
me
up
cash
in
Firefox?
It
brings
the
attach,
doesn't
break-ins
already,
curiously,.
J
Shouldn't
bring
me
a
fish,
I
think
I,
really
like
that
I
think
Safari
doesn't
has
some
heuristics
that
it
uses
to
figure
out
whether
a
case
the
pages
preventable
okay,
even
if
it
has,
regardless
of
them
yeah
anyway.
The
point
is
that,
like
it's
very
difficult
to
properly,
do
all
this,
because
very
few
developers
are
gonna,
take
the
time
to
say
like
if
I'm
in
Safari,
that
conditionally
add
this
before
loading
and
learn,
but
don't
do
it
if
not
in
Firefox
and
so
I
think
the
end
result
is
the
brakes,
be
a
caption
part.
B
J
And
WPT
I
don't
know
so
it
could
be
that
the
logic
for
removing
iframe
is
the
same
as
like
closing
a
tab,
because
I
think
the
way
it
works
since
I'm.
A
guessing
toy
works
in
Safari
is
that
it
fires
it
on
navigations,
but
doesn't
fire
it
close
so
and
something
like
yeah,
maybe,
but
what
driver
is
pretty
difficult,
I
think
you
can
have
any
tab
and
close
it,
but,
like
you
have
to
do
that.
Actually,
okay,.
G
Running
and
so
there
so
there
are
four
tests
that
are
currently
read
at
the
first
affari.
My
gut
says
if
those
tests
were
made
to
pass
that
it
might
cause
this
gap
to
get
closed,
and
it
might
be
that
then
for
web
sites
who
are
trying
to
write.
But
you
know,
hey
I
got
a
comment
or
written
some
text.
They
can
write
more
consistent
code
to
save
that
state,
yeah
and
then
the
receipt
of
those
tests
are.
J
G
B
J
B
E
G
G
It
up
and
make
you
understand,
know
why
why
it
is
that
it
matters.
It's
it's
not
just
for
going
to
the
background.
It's
the
specific
use
case
on
the
website,
save
and
stayed
so
that
went
in
the
moment,
so
that
then
after
goes
the
background.
Hopefully
they
already
know
Cody
or
when
they're
shut
down
when
they
go.
The
background
they've
already
said
that
to.
B
B
B
B
G
E
B
B
B
B
Q
G
B
B
But
yeah
we
will
need
to
look
at
what
kind
of
conditions
of
that
are
doing
what
they
should
be
doing.
Why
are
they
doing
it
and
then
define
it
as
something,
and
this
is
a
fairly
large
project
that
is
blocking
the
Firefox
implementation
as
far
as
I
know,
as
well
as
I,
don't
think
he
should
should
before
this
happens.
Thank.
J
G
B
B
B
But
yeah
it
would
be
very
hard
for
users
to
actually
know
that
those
differences
exist
unless
some
wrong
library
ref
is
relying
on.
When
you
know
some
consequences
that
have
been
seen,
there's
been
more
resource
using
and
timing
stuff,
then
I
got
the
wrong
resource
because
they
can't
be
on
the
cache
in
the
end
has
been
refreshed.
Yeah.
B
Okay
and
then
otherwise,
we
have
resource
hints,
which
we
concluded
last
year,
that
they
need
to
be
split
up
into
four
different
specs,
because
each
one
of
them
have
implementation
tests
and
like
very
different
implementation
task
statuses,
but
we
haven't
actually
done
any
of
that
work.
To
actually
do
that,
so
we
should,
but
it's
I
can
remain
working
draft
long
tasks,
pane
timing,
I
believe
they
are
yeah
all
working
drafts.
Server
timing
is
one
where
we
could
make
some
progress.
B
There
are
a
bunch
of
open
issues
that
I
talked
to
Charlie
beza
and
he's
still
interested
in
making
progress
on
them
and
interested
in
remaining
the
active
editor
test
wise.
There
are
some
think
one
of
the
issues
is
touching
on
parsing
of
malformed
headers,
so
this
needs
to
be
result,
but
once
it
wouldn't
be
like
tests,
we
do
passing
locations.
B
So
it's
mostly
a
question
of
closing
up
a
issues,
so
he
implemented
over
time
in
an
old
in
WebKit
and
okay,
I
talked
Firefox
Firefox
implemented,
and
then
we
have
the
question
of
why
purview
for
server
timing.
Then
it
comes
to
I.