►
From YouTube: OpenJS Foundation AMA: webhint
Description
The OpenJS Foundation is a member-supported non-profit organization that provides a neutral home for some of the most important project in the JavaScript ecosystem.
Learn more and join us at https://openjsf.org
A
Alright,
it
looks
like
we
are:
live
on,
YouTube,
welcome
everybody
to
open
Jas
foundations,
monthly
AMA,
where
you
have
an
opportunity
to
ask
questions
of
some
of
our
hosted
projects.
Today
we
have
the
web
hint
team
and
moderating
today's
ama
will
be
rachel
while
and
so
I
will
go
ahead
and
I
will
go
ahead
and
pass
it
over
to
Rachel.
Well,
hey.
B
B
A
B
Talk
about
web
and
today,
I'm
going
to
be
moderating
the
discussion.
So
I
hear
we
have
questions.
We
have
a
couple
pre
submitted
questions.
We
have
the
ability
to
ask
questions
live
on
YouTube.
You
can
tweet
at
open
JSF
with
your
questions
about
weapon,
so
we're
gonna
get
started
here
in
a
minute
with
two
contributors
before
we
we
get
started.
I
just
want
to
just
introduce
myself
again.
My
name
is
Rachel,
while
I'm
a
program
manager
for
dev
tools
for
Microsoft
edge,
so
I've
been
there
for
not
quite
a
year
yet.
B
But
it's
been
exciting,
of
course,
because
we
just
really
started
chromium
based
browsers.
So
it's
been
really
fun
for
me
to
work
in
open
source
again
to
collaborate
out
in
the
open,
with
folks
at
chrome
and
contributors
on
the
chromium
project
and
I.
Think
that
dovetails
really
nicely
with
what
we're
going
to
be
talking
about
today
with
web
hint,
which
is
all
about
making
the
web
a
great
place
to
dev.
Regardless
of
what
browser
you
choose.
So
that's
a
little
bit
about
me.
B
C
Yeah
I'm
Harold,
the
hungry
member
of
the
project,
part
of
the
Firefox
side,
I'm,
a
product
manager
on
Firefox
dev
tools,
which
includes
automation
and
the
front
end
of
dev
tools
and
a
few
other
things.
So
it
generally
do
developer
experience.
So
big
part
of
my
job
is
thinking
yeah
to
make
things
better
for
developers
so
collaborating
here
with
weaponed
and
thinking
about
how
we
extend
these
things
into
dev
tools.
It's
part
of
my
job
so
and
it's
been
a
fun
we're
to
Tony.
Well,.
D
Yeah
I'm
Tony
Roth's
I'm,
a
software
engineer
on
the
developer
tools
for
Microsoft
edge,
I
joined
the
project.
We've
got
a
little
over
two
years
ago
and
yeah
just
really
excited
to
kind
of
help,
build
tools
for
developers
getting
to
do
this
out
in
the
open
and
getting
to
collaborate
not
only
with
other
people
but
other
projects
to
bring
this
experience
together.
It
has
probably
been
my
favorite
thing
so
far.
B
Great
excellent
well
before
we
get
looking
at
some
of
the
community
questions,
I
wanted
to
open
with
a
couple
of
background
questions
just
to
sort
of
set
the
scene
for
folks
who
might
not
be
aware
of
web
hint
or
what
it
is
so,
first
of
all
I'm
curious
to
know
how
did
web
cam
come
about,
and
what
does
it
do
exactly?
He
wants
to
give
the
elevator
pitch
for
what
WebM
is.
D
So
I
actually
think
Harold
has
the
longest
history
with
the
project
of
anyone
here,
if
I
recall
correctly,
but
I
can
totally
feel
this
too.
To
start,
so
my
understanding
of
the
history
of
weapon
came
out
that
there
was
a
project
I
think
that
had
inspired
trying
to
originate
this
for
some
of
the
work
that
had
been
done
for
online
scanner
for
Internet
Explorer,
there's
a
modern
ie,
but
that
was
very
browser.
D
Centric
and
I
know
that
Anton,
who
really
helped
get
the
project
started,
was
interested
in
doing
something
that
was
broader
reaching
for
web
developers
and
I
think
Harold.
In
conversations
with
you
in
particular,
you
helped
encourage
him
to
open
that
up
and
explore
something
that
could
be
useful
for
web
developers,
regardless
of
which
browser
or
browsers
they
were
developing
for
and
I
think
the
the
key
problem
that
was
looking
to
be
solved
with
the
project.
Is
this
huge
amount
of
knowledge
and
that
ever
increasing
in
web
development?
D
We
do
you
have
so
many
different
resources
and
in
there's
so
many
new
standards,
new
developments
going
on
in
browsers.
You
can't
hardly
keep
up
with
it
all,
let
alone
the
community
driven
projects
and
frameworks
that
build
on
top
of
the
core
platform
and
so
trying
to
build
the
best
web
content
that
you
can
can
be
a
really
daunting
task
and
having
a
project
like
web
hint
to
kind
of
help,
set
the
guardrails
and
help.
Keep
you
on
the
happy
path.
I
think
is
really
the
core
idea.
What
it's
about.
C
Like
you
can
remove
this,
this
meta
tag
you
can
route
this,
because
I
can
so
much
so
much
of
that
knowledge
is
kind
of
lost
in
nowhere
where
it's
just
you
don't
really
know
what
can
be
touched
without
like
or
why
why
things
were
headed
initially.
So
that's
the
thing
too
big,
a
big
part
of
just
being
helpful
to
developers
on
what
parts
of
the
code
don't
do
anything
which
is
something
Firefox.
Dev
tools
has
are
more
for
CSS
as
well,
which
weapon
does
rely
C
for
for
HTML
and
other
parts.
Certainly
that's
that's.
C
C
This
is
probably
something
not
something
you
need,
there's
something
you
can
expand
to
support
more
browsers,
so
just
like
not
having
just
this
this
knowledge
of
what
works
across
all
browsers
in
what
shape
in
in
their
hat,
but
putting
that
into
a
tool
makes
it
easier
and
dinner
parties
that
that
it
it's
it's
set
up
in
a
way
thanks
to
a
J's
foundation
that
it
can
be
expanded,
so
it
shouldn't
doesn't
try
to
be
opinionated
to
say,
I'm
telling
you.
This
is
bad.
C
B
It
sounds
like
it's
kind
of
taking
that
you
know
that
thing
we
do
when
we're
developing
for
the
web.
We
have
like
a
tab
open
on
MVN
and
we
have
one
open
on
the
wicked
standards
and
we
have
one
open
on,
like
some
Stack
Overflow
post
about
how
to
take
care
of
a
certain
problem
and
all
that,
like
institutional
knowledge
that
we
have
in
our
heads,
this
is
about
sort
of
like
consolidating
it
into
one.
B
You
know
between,
like
the
the
hints
that
weapon--
provides,
as
well
as
the
configurations
sort
of
a
custom,
but
that
custom
sort
of
recommendation
experience
and
yeah.
It's
definitely
hard
to
keep
up
with
the
ever-changing
web
and
all
of
the
you
know,
standards
new
implementations,
things
get
deprecated,
it
happens.
So
that's
a
great
interest
of
the
project,
Thanks,
so
I'm
kind
of
curious.
Actually
how
I
totally
touched
on
this
little
bit,
but
how
the
two
of
you
came
to
be
interested
in
working
on
my
hands.
What
could
have
drew
you
to
the
project.
B
C
Think
two
three
years
ago,
probably
I'm
ton
reached
out
I
think,
like
chrome,
tough,
sometimes
a
lot
of
browser
people
were
in
town
in
Mountain,
View
California,
so
we're
just
kind
of
meeting
up
with
two
people
and
Anton
reached
out
with
somebody
from
the
Jays
Foundation
as
well.
They
just
want
to
kind
of
get
to
talk
about
like
this.
C
This
project
I
had
in
mind
that
they
want
to
get
into
a
json
Dacian
to
be
to
be
a
cross-browser
project,
so
everybody
can
participate
so
and
have
this
open
platform
for
everybody
to
feedback
in
to
the
project
and
that
that's
where
we
initially
started
so
I
think
it
took
like
another
half
a
year,
actually
get
the
project
launched
and
like
another,
two
years,
probably
to
it
a
1.0.
So
it
just
things
like
time.
C
Officially,
that
was
just
in
my
role,
that's
kind
of
getting
a
keeping
tabs
on
the
web
and
see
where
we
can
collaborate
more
with
people
creating
interesting
things
on
a
web,
and
there
was
already
yeah
really
an
interesting
space,
because
that
was
kind
of
evolving
where
dev
tools,
extension
system
and
then
later
on
thinking
more
about
how
these
extensions
can
integrate
deeper
within
dev
tools,
that's
kind
of
where
it
evolved
into
so
yeah.
That's
my.
D
B
Great,
so
actually
I
want
to
kind
of
expand
on
a
couple
points
that
folks
made
here
so
I
know:
Harold
mentioned
dev
tools,
extensions
and
Tony.
You
mentioned
automation.
We
talked
a
little
bit
about
the
problems
that
web
pencils,
but
we
haven't
really
talked
about
what
exactly
it
is
of
in
terms
of
like
the
forms
it
takes
and
in
fact
there
are
quite
a
few
like
sort
of
entries
in
the
web
hint
product
suite
so
Tony.
Maybe
you
could
talk
a
little
bit
about
what
the
weapon
offerings
are.
B
D
And
to
give
kind
of
the
very
quick
summary
of
what
the
project
is
it
you
can
think
of
it
succinctly
as
a
linter
for
the
web.
If
you
will,
but
you
know
it's
a
tool
about
helping
you
identify
best
practices
of
your
code,
Carol
referenced
earlier
being
not
too
opinionated
with
the
weapon
and
I
think
that
the
way
I
look
at
that
is
it's
presenting
opportunities
for
best
practices.
It's
identifying
opportunities
in
your
code,
as
opposed
to
telling
you.
This
is
exactly
how
you
have
to
do
it.
D
That's
why
it's
configurable,
so
you
can
change
things
now
to
provide
that
and
to
help
make
it
useful.
When
we
talk
about
like
what
offerings
are
actually
involved,
we
we're
trying
to
integrate
into
an
increasingly
wide
array
of
places.
We've
been
looking
at
this
with
the
project
is
part
of
hitting
different
parts
of
the
developer
lifecycle,
whether
you're
developed
writing
code
and
developing
whether
you're
debugging
it
in
a
browser
or
whether
you've
already
deployed,
and
you
want
to
evaluate
something.
That's
in
production.
D
That's
still
very
useful
and
up
there,
where
you
can
go
to
weapon
IO,
you
can
type
in
any
public,
URL
and
it'll
just
kick
off
a
scan
using
weapons
web
service
and
give
you
the
results,
but
from
that
I
think
we
moved
into
node,
and
so
there
is
a
hint
package
on
NPM
that
you
can
get
so
that
you
can
run
it
like
any
other
linter
against
a
maybe
a
staging
or
local
URL
or
even
raw
files
on
your
filesystem
to
get
feedback.
That
way.
D
There's
an
own
API
if
you
want
to
programmatically
drive
that,
but
there's
also
the
command-line
interface
that
you
can
run
in
the
past
year.
We've
branched
out
from
that
to
expand
into
extensions
into
browser,
dev
tools
to
really
help
more.
With
that
debugging
side
of
the
life
cycle,
and
so
in
the
fall.
We
the
project,
released
dev
tools,
extension
for
Chrome,
the
new
chromium
based
edge
and
Firefox.
D
The
later
you
discover
them
to
actually
resolve
and
fix
and
so
engaging
while
you're
writing
code
is
sort
of
the
optimal
place
to
find
something
there's
other
places
we're
still
expanding
into
as
well.
We
think
that,
being
part
of
your
test
flow
to
help,
you
hold
the
line
on
the
qualities
that
you
think
are
important
in
your
own
project.
It's
really
important,
so
you
can
integrate
weapon
into
your
CI
flow.
We've
got
instructions
on
the
website
to
do
that
with
like
Travis
and
circle
and
there's
an
early
project
we're
working
on.
B
That's
awesome
thanks.
Yeah
I'm
really
excited
about
the
BS
code.
Extension
I
just
wrote,
actually
a
blog
post
about
it.
Tony
and
I
collaborated
on
that,
and
it's
up.
If
you
follow
a
web
hint
on
Twitter,
webhead
IO
is
the
handle.
You
can
find
our
blog
post
about
that
recent
announcement,
as
well
as
other
web
hint
news,
so
small
plug
great,
so
I
think
the
next
question
I
was
interested
in
asking
and
I'll
address
this
one
to
Harold.
C
I
think
to
just
the
general
theme
of
building
things
for
users:
I
think
that's
what
often
like
we
as
tool
builders,
but
also
developers
like
have
to
keep
in
mind
as
the
goal
like
the
end
user.
So
anything
that
helps
sites
to
work
better
and
for
more
users.
Is
this
helpful
so
things
that
often
fall
through
cracks?
I
guess
of
course,
X
ability.
C
So
that's
like
the
the
Louis
bar
and
X
build
even
comes
in
a
gradient
of
keyboard,
accessibility,
color,
accessibility,
readability,
there's
a
lot
of
things
that
fall
into
this,
so
that
just
that's
something
we
know
we're
struggle
with
like
because
it
has
so
many
aspects
to
it.
So
you
can
you
can
start
small,
you
can
end
up
screen
readers
and
it's
not
easy
to
test.
C
So
any
any
help
we
can
give
developers
it's
helpful,
but
it
all
speeds
into
performance
like
performance
itself,
is
next
ability
issue
for
some
people,
especially
if
you
traveled
on
2g
so
doesn't
load.
If
caching
is
broken
like
there's
so
many
things
you
can
do
wrong
and
often
times
when
you
do
performance
audits.
It's
not
it's
not
any
main
thread.
Io!
That's
cuz
roms,
just
like
bad
caching,
sending
too
much
data,
and
that's
that's
that's
easy
to
to
audit
foreign.
C
It's
those
are
really
hard
to
fix
because
our
for
my
big
architectural
problems
as
well
versus
like
just
switching
on
a
CDN
so
yeah,
it's
it's
everything.
Kind
of
in
support
of
building
better
user
experience
this,
especially
where
fixes
or
hopefully
just
adding
some
tax.
It's
not
about
like
a
broken
product
design.
C
It's
really
the
engineering
aspects
of
it
which
people
often
forget
and
having
the
tools
in
place
to
hold
up
that
bar
like
what
once
you
fix
those
things
you
don't
want
to
regress
them
so
having
those
tools
in
place
across
your
development
pipeline
in
your
editor
in
your
animation
and
your
browser,
so
people
can
test
it
on
to
open
in
production,
like
that's,
that's
I
think
the
biggest
thing.
So
the
setting
expectations
for
user
experience
and
having
a
tool
to
hold
people
accountable,
yeah.
B
Yeah
yeah,
actually
you
brought
a
great
point.
I
think
one
thing
we
haven't
really
talked
about
is
like
not
only
does
web
hint
like
provide
developers
with
some
guidance,
but
you
talked
about
fixes
so
I
hope
actually
Tony.
If
you
want
to
take
this
one,
maybe
explain
of
folks
like
what
web
hint
provides,
not
just
in
terms
of
like
information
or
standards,
but
in
terms
of
like
actually
helping
developers
be
able
to
fix
the
issues
that
they
encounter,
and
this
could
be
sure.
D
If
it's
something
to
do
with
HTML,
then
the
browser
extension
will
help
jump
you
to
the
correct
element
in
the
elements
panel,
so
that
you
can
kind
of
explore
it
in
case
that
may
have
been
dynamically
generated.
You
can
at
least
explore
how
it
fits
in
to
the
rest
of
the
page
and
get
you
back
to
that
point,
and
another
thing
I
wanted
to
just
plug
real
quick
here
too,
is
the
hints
themselves,
aren't
just
part
of
the
project
like
with
this.
D
B
D
Is
the
beauty
of
the
community
nature,
and
what's
nice
too,
is
that
when
we
find
something
new
you
know,
I
can
go
and
I
don't
just
contribute
to
weapon.
I
can
I've
made
contributions
to
browser
competitor
where
I
find
something
that
may
be
a
bug
or
just
hasn't
been
documented
yet
there,
and
so
it's
a
great
opportunity
to
kind
of
not
only
consume
other
projects
but
reach
into
them
and
help
improve
them
as
well.
C
C
C
Lighthouse
has
focused
a
lot
on
performance,
a
lot
of
people
like
open
yeah,
mostly
for
performance,
and
it's
good
that
I
have
other
audits
in
there
as
well
to
make
them
visible
so
and
then
it
has
a
bigger
audience
now,
outside
of
the
browser,
we've
been
integrated
into
PageSpeed
insights
and
really
driving
these
business
metrics
that
Google
ones.
People
talk
to
my
seconds
so
I
think
that's
a
great
like
factor
for
or
create
a
showcase
of
how
a
tool
can
can
expand
the
audience
even
to
to
everybody
talk
to
minds
against
the
same
thing.
C
So
that's
that's
interesting!
Think
T
it.
The
biggest
piece
for
me
is
the
extensibility
of
weapons
and
how
it
initially
really
focused
heavily
on
being
across
the
development
pipeline,
so
being
able
to
hook
into
Thea's
code,
to
audit
your
CSS
HTML,
really
on
a
code
level
versus
on
this,
like
loading,
a
page
and
the
browser
and
seeing
like
it
all
comes
together,
it's
important
as
well,
so
you
like
across
every
state,
every
piece
of
these
components
to
build
up
eventually
a
website
for
the
user.
C
They
want
to
know
what
they
can
improve
in
their
project,
but
also
it
has
been
interesting
for
weapon
tests
only
mentioned
like
they
have,
including
like
web
company
de
which
lighthouse
software
it
doesn't
show,
but
they
have
a
big
repertoire
of
thing,
so
there's
definitely
room
for
those
things,
but
they're
detter.
The
last
words
for
the
opinionated
aspect
like
there's
a
lot
of
kind
of
red
and
green
within
within
lighthouse.
C
Like
things
you
do
wrong
so,
but
developers
like
developers
like
to
have
a
prioritized
bucket
list,
but
they
also
just
want
to
get
a
general
stand
like
where,
where
can
I
fix,
where
the
low-hanging
fruits
we're
like
the
bigger
architectural
problems
so
having
a
full
list
displayed
I
think
it's
also
helpful.
In
many
cases,
yeah.
D
Is
it
doesn't
do
a
lot
of
metrics
and
in
terms
of
real-time
measurement
of
your
performance,
the
focus
for
weapon
and
performance
in
particular,
is,
as
I
mentioned
earlier,
it's
more
about
opportunities,
it's
finding
like
things
where
you
haven't
set
cache
headers
correctly
or
looking
at
the
total
bytes
over
the
wire
and
looking
at
how
that's
most
likely
going
to
load
over
a
three
3G
or
worse
network,
but
doing
it
in
a
way.
That's
I
would
say
deterministic
so
that
you
tend
to
get
consistent
results
when
doing
it.
B
So
I
have
a
question:
I'm
gonna
direct
this
one
to
you
Tony.
What
do
you
think
is
the
most
challenging
like
interesting
challenge
in
terms
of
working
in
the
web
codebase-
and
you
know
it's
someone
who's,
obviously
a
main
contributor
to
the
project.
What
are
what
are
the
things
that
you
find
like
very
fun
or
sort
of
interesting
or
challenging
about
contributing
to
web
him?
Yeah.
D
I
I
think
the
the
most
challenging
thing
is
the
release
process
of
actually
getting
updates
out.
The
tour,
but
part
of
that
is
because
the
project
is
structured
to
be
very
loosely
coupled
between
components
to
help
make
it
easy
for
anyone
to
come
in
and
contribute
to
just
a
small
piece
like
you
want
to.
D
You
have
a
particular
idea
for
a
test
you'd
like
to
write
to
help
give
feedback
to
users
you
can
come
in,
you
can
make
a
new
hint
and
you
can
focus
just
on
a
isolated
NPM
package
for
that
hint,
as
opposed
to
having
to
worry
about
the
rest
of
the
project.
But
for
those
of
us
that
are
working
on
more
cross-cutting
pieces,
that
means
we
have
upwards
of
80
packages
that
we
actually
end
up
touching
and
when
we
need
to
go,
make
cross-cutting
changes.
B
I'm
curious-
and
maybe
you
I
don't
know
if
this
was
all
sort
of
decided
by
the
time
you
joined
the
project
but
I'm
curious
to
know
like
if
I,
never
you
have
at
this
experience
of
like.
Was
that
always
the
way
web
hint
worked
or
was
that
was
that
build
process,
sort
of
an
iterative
or
like
you
know,
was
that
iteratively
decided
upon
or
like
I'm
curious.
If
the
project
tried
one
thing
and
didn't
work
out,
and
he
sort
of
like
arrived
at
this,
like
the
mono
repo
way
of
doing
things,
yeah.
D
A
B
Cool
well
I
think
I
kind
of
want
to
talk
a
little
bit
about
kind
of
what's
new
in
web
hints.
So
we
talked
a
little
bit
about
this.
The
browser
extension
went
out
of
beta
into
v1
I,
think
late
last
year,
bs
code
extension
followed
soon
after
that,
it's
a
big,
maybe
Harold
or
Tony,
actually
either
of
you.
B
C
C
So
some
of
the
issues
I
filed
this
year
when
trying
it
out,
was
just
like
better
grouping
and
better
like
compartmentalizing
of
data,
so
that
was
in
in
the
X
ability
parts
so
having
those
grouped
and
then
also
in
the
accountability
coming
to
Bill
is
to
your
heart,
because
it's
there's
a
spate
of
like
false
positives.
So
it
is
a
big
best.
Guess,
like
this
property
might
not
work
in
most
browsers.
C
But
it's
really
hard
to
know
all
the
interdependencies
between
the
things,
and
this
doesn't
necessarily
cause
an
issue
when
you
open
the
browser,
that's
not
working,
and
but
it
could
so
it's
making
dose.
The
section
was
possible.
I
think
that
some
of
work
went
into
that
as
well
to
reduce
the
number
of
false
positives
to
relook
at
the
whole
set
and
I
was
also
a
weapon
really
let
away
because
this
was
one
of
the
first
projects
using
ambien
comfort
data.
C
For
that
purpose,
there
was
a
lot
of
kinda
additional
infrastructure
had
to
be
laid
out
to
to
make
this
more
useful
versus
just
like
I'm.
Applying
these
very
blunt
rules
against
you,
CSS,
and
these
are
all
the
things
that
didn't
work
versus
like
okay,
I'm,
actually
looking
at
your
whole
CSS
every
rule
holistically
within
within
a
set
where
it's
being
applied.
So
that's
that's
been
where
weapon
really
did
a
lot
of
effort
to
make
this
1.0
useful
yeah.
B
B
D
We
have
since
broken
that
out
into
its
own
package,
that's
still
under
weapon,
so
that
it
can
be
consumed
separately
and
we've
we're
having
we've
had.
We
haven't
recently
been
discussing
this,
but
we
have
kind
of
an
open
question
of
whether
this
might
be
something
that
would
make
sense
to
be
part
of
the
browser
compact
a
to
repo
itself
in
the
future.
D
Right
now,
I,
don't
know
of
any
other
project.
That's
chosen
to
consume
using
this
particular
API
other
than
with
him,
but
it
is
something
that
could
be
interesting
specifically
with
getting
to
the
browser
extension
being
released.
That
was
the
first
place.
We
turned
on
providing
feedback
using
the
compatibility
data
as
well.
D
If
you
added
this
vendor
prefix
or
this
alternate
property,
you
would
gain
support
for
these
other
browsers
that
you're
trying
to
target
so
that
that's
a
very.
That
was
a
piece
that
we
worked
on
there
and
then,
like
Harold,
mentioned
with
accessibility.
We
because
web
think
consumes
acts
that
have
been
treated
as
kind
of
one
hint
and
we
based
on
his
feedback,
broke
that
into
number
a
dozen
or
so
categories
that
are
based
on
the
categories
in
the
acts
core
project,
but
to
treat
them
as
independent.
D
Came
after
the
browser
extension
v1
for
the
v1
of
the
vs
code
extension
and
that
was
are
driven
a
lot
by
feedback
where
we
would
get
into
discussions
on
the
relative
importance
of
different
hints
because
out
of
the
box
on
weapon
prior
to
that
point,
there
were
him
severity
x'
for
him,
but
they
were
all
by
default.
The
same
so
you
could
customize
all
messages
from
a
hint
to
be
an
error
or
a
warning.
D
If
you
wanted,
but
out
of
the
box,
it
was
completely
unaffiliated,
but
it
made
everything
kind
of
feel
equally
important,
and
so
with
the
change
we
went
through,
we
reviewed
all
of
the
messages
generated
by
weapon
and
kind
of
assigned
severity,
x'
or
mapped
severity.
X',
where
appropriate,
like
acts
internally
already
had
a
number
of
severity
x',
and
so
we
mapped
on
the
accessibility
messages
to
those
to
come
up
with
a
more
useful
default
set
to
help
developers
understand
the
most
important
things
most
likely
to
work
on.
First,
it's
still
configurable.
D
I'll
add
for
the
vs
code
extension
to
since
we're
talking
about
things
that
are
new
previously
weapon
had
really
been
focused
just
on
the
core
web
technologies
of
HTML,
CSS
and
JavaScript,
and
then
of
course,
looking
at
network
headers
and
traffic.
But
when
you
talk
about
helping
developers
while
they're
writing
code
you're,
not
often
writing
directly
in
one
of
those
technologies,
you're
typically
using
a
transpiled
language,
be
that
typescript
or
you've
got
JSX
if
you're
using
react
or
tsx.
D
If
you're
using
react
with
typescript,
your
CSS
could
be
actually
less
or
sass,
and
so
we
implemented
pre-processors
for
those
for
WebP
in
to
help
translate
them
in
a
way
that
hints
themselves
can
still
be
authored,
predominantly
to
look
at
the
Dom
or
to
look
at
a
style
structure
or
the
JavaScript
ast,
even
if
the
original
source
is
coming
from
a
transpiled
language.
So
it
kind
of
helps
bridge
that
gap.
You
get
more
feedback
in
your
editor,
but
contributors
that
are
contributing
hints
to
the
project.
B
B
C
D
B
C
B
So
I'm
curious
to
know
and
I'll
ask
us
to
both
of
us
start
with
Toni
what
you
see
kind
of
in
the
future
for
WebP
in
parts
of
the
project,
you'd
like
to
develop
more
new
features.
Things
like
that.
You
don't
have
to
look
too
far
into
the
future,
but
just
some
things
you're
excited
about
up
and
coming
with
weapons.
D
C
I
think
yet
I'm,
definitely
just
something
I've
been
exploring
for
a
bit
it's.
C
How
can
this
be
part
of
a
default
experience
within
dev
tools,
so
looking
at
like
run
experiments
to
read
out
this
into
a
Firefox
dev
tools,
because
that
people
have
to
definitely
ask
and
asking
for
an
audit
tooling,
but
also
we
have
had
a
lot
of
good
feedback
on
any
in
context,
auditing
that
we've
been
doing
for
CSS
that
hasn't
been
applied
and
the
Flex
partisan
grid
has
been
really
helping
people
to
make
the
right
calls
and
why
things
aren't
working
order
to
get
them
work
better.
So
it's
a
it's
a
real
good
learning
tool.
C
It
should
be
exposed
more
in
dev
tools.
So
one
part
it's
like
getting
the
panel
just
into
dev
tools
for
all
users.
They
don't
have
to
discover
it,
don't
have
to
find
it
somewhere
else
and
then
the
other
piece,
like
also
providing
more
extension
hooks
into
dev
tools
that
get
it
into
the
right
place.
Like
you
want
to
see
the
CSS
and
HTML
audits
within
your
inspector
tab.
C
You
want
to
get
the
JavaScript
lated
audits
into
the
debugger
tab
and
then
the
network
tab,
so
they
need
to
be
able
do
not
just
link
to
those
tabs
if
any
information
pops
up
so
that
so
that's
where
needs
don't
need
to
improve
things,
and
so
that's
that's
yeah.
That's
my
my
focus
right
now
for
weapons
just
to
get
more
eyes
on
it
as
well.
Yeah.
B
D
Now,
honestly,
I,
don't
think
it's
something
we've
explicitly
discussed
before,
but
it's
a
really
good
suggestion,
because
we're
we're
clearly
trying
to
reach
out
to
developers
that
don't
already
have
all
this
knowledge
baked
into
their
head,
and
so
it's
got
me
thinking
just
right
now
about
what
what
are
specific
things.
We
could
potentially
do
to
help
improve
our
reach
to
that
audience
and
help
them
feel
like
they
can
engage
with
the
project.
D
One
thing
I
will
mention
that
we
we've
done
before
is
we
we
actually
have
collaborated
with
some
code
school
students
in
using
webcam
as
an
opportunity
for
them
to
start
contributing
to
open
source.
We
did
that
over
the
past
summer,
and
it
was
a
really
great
experience.
We
had
a
few
different
folks
come
through
and
contribute
hints
and
improvements
and
fixes
throughout
different
parts
of
the
project,
and
so,
in
addition
to
the
actual
knowledge
base,
that
weapon--
provides
I.
D
B
And
yeah
I
mean
it's
a
great
point.
I
feel
like
every
time.
I
use
web
hint,
I'm
learning
something
right
lay
because
I
don't
have
all
the
knowledge
in
my
head,
but
yeah.
If
you
for
the
person
who
asked
that
question,
if
you
have
any
other
ideas
or
thoughts
about
this,
feel
free
to
reach
out
on
the
web,
hint
I
Oh
Twitter
account
or
find
us
contact
info
on
the
website.
Things
like
that
I
be
super
interested
to
hear
your
more
thoughts
on
that.
B
So
thanks
for
thanks
for
the
question
so
actually
kind
of
to
springboard
off
of
this
topic,
I
was
curious
to
hear
from
folks
and
I'll
start
with
you
Harold
how
people
who
are
new
to
web
hint
can
get
started,
whether
that's
like
contributing
sort
of
familiarizing
the
code
base.
What
do
you
sort
of
recommend
for
someone
who
might
be
interested
in
getting
started
using
web
hint,
but
also
potentially
contributing
to
a
pin
yeah.
C
I
think
the
mono
repo
helps
to
discover
all
the
good
first
books.
It's
like
it's.
That's
often
like
that's
the
problem
we
have
and
other
projects
within
Firefox
like
we
are
spread
out
across
github
and
most
have
Central
mercurial,
there's
a
lot
of
places
to
find
good
first
books
so,
but
having
it
all
one
rebuilt,
it
finds
the
right
like
server
side
front
and
whatever
people
interested
in
I
think
a
great
place
to
start
toward
versus.
C
Did
the
rules
section
just
if
you
have
ideas
and
how
I
think
can
be
more
useful
for
you
if
you
found
something
that
that
weapon
should
warn
you
about,
that
could
tell
you
about
like
hey.
If
you
use
this
be
aware
about,
there
might
be
dragons
like
just
these
kind
of
rules,
then
that's
that's
the
best
way
to
start,
probably
because
that
dose
directly
will
help
developers
like
just
get
something
in
front
of
people
the
day
that
you
care
about
that
help
you
that
can
help
others
as
well.
So
it's
an
easy
way
to
share.
D
D
You
don't
have
to
start
big.
You
can
start
small
yep.
B
D
Thrall
in
there,
too
is
I
think
when
we
talk
about
new
hints
in
particular,
you
know,
there's
probably
a
backlog
of
ideas
there,
some
easier,
some
harder,
but
also
we've
I,
mean
I,
think
just
scouring
like
Twitter
and
stuff
we've
had
good
ideas
come
in
that
we'll
see
people
tweet
about
it
will
turn
around
and
try
to
get
logged.
Where
often
it
starts
with
I
just
spent
three
hours
figuring
out
that
it
says
one
line
of
code,
that's
giving
me
grief.
D
Mm-Hmm
we've
got
some
interesting
hints
in
particular
in
the
pitfalls
category,
that
kind
of
originated
there.
One
of
my
favorites
is
a
hint
about
creating
SVG
elements
dynamically,
so
SVG's
a
little
bit
special
in
the
web
space,
and
you
know
we're
used
to
using
the
dom
calling
create
element
to
get
all
our
of
our
buttons
and
divs
and
everything
we
need.
But
if
you
try
to
create
element
circle,
it's
not
going
to
render
a
circle.
It
gives
you
technically
an
HTML
element
named
circle.
D
You
have
to
use
this
alternate,
API
called
create
element
and
s
that
you
almost
never
touch
unless
you're
trying
to
dynamically
create
SVG
elements,
and
so
that's
interesting
and
the
problem.
There's
there's
no
error,
it
doesn't
fail,
it
just
doesn't
work,
and
so
you
can
lose
a
lot
of
time
kind
of
digging
through
before
you
figure
out.
B
So
I
see
another
question
here
about
the
link
to
the
repo.
So
if
you
go
to
github,
slash
web
hint,
there's
github.com,
slash
web
hints
io
and
then
the
hint
repo
so
github.com
slash
web
10
io
flash
hint.
That
is
the
mono
repo
that
we've
been
talking
about.
You'll
see
that
web
hint
io
organization
has
a
couple
other
repos
that
are
outside
of
that
like
for
the
web
site
and
things
like
that.
But
the
main
repo
that
we've
been
talking
about
is
the
hint
repo
inside
of
web
hint
io.
B
B
I
actually
feel
like
I
am
just
about
out
of
questions
from
chat
and
presubmit,
and
some
of
my
own
just
questions
I
wanted
to
ask
the
team
does
anything.
Anyone
else
have
anything
they
want
to
share
or
anything
we
didn't
touch
on
that.
You
want
folks
to
know
about
Lebanon.
D
You
know
I,
think
it's
interesting,
I,
think
racially.
You
and
I
had
discussed
this
before
kind
of
our
own
workflows
for
using
weapon
and
eating
our
own
dog
food.
If
you
will
I'd
love
to
share
that
both
within
the
project
and
in
my
own
personal
usage
within
the
project,
we
have
it
set
up
to
automatically
run
as
part
of
our
CI
process
for
both
our
website
and
the
UI
for
the
browser
extension.
D
D
For
my
personal
usage,
I
really
enjoyed
the
vs
code
extension
because
I,
like
catching
the
issues
as
early
as
possible,
so
I've
just
it's
the
easiest
one
to
just
have
on
and
I,
don't
have
to
think
about
it,
I
just
every
now
and
then
I
get
a
squiggly
and
I'm
like
oh
yeah.
I.
Wasn't
thinking
about
that,
so
I
should
go
and
fix
it.
Yeah.
B
Yeah
I
agree:
I
love
it
like
the
vs
code.
Extension,
it's
great.
So
if
you
for
folks
who
haven't
used
it,
you
get
this
sort
of
like
red
squiggly
underlines
when
you
mouse
over
an
issue.
You
get
that
sort
of
like
intellisense
dish
box
that
lets
you
know
what's
wrong,
there's
also
like
envious
code.
The
problems
pane
will
actually
list
out
just
like
any
sort
of
winter.
You
might
be
familiar
with
the
way
that
it
integrates
with
this
code.
You
can
get
a
list
of
your
problems.
B
C
C
So
how
that
will
then
carry
over
and
like
feed
into
more
aspects
of
code
will
be
interesting
to
see,
especially
if
there's
more
detail
and
then
Emily,
and
also
taking
on
more
of
that
that
knowledge
had
already
weapon
created
and
how
this
data
can
be
used
for
audits,
so
other
tools
can
hook
into
it
like
weapon
is
taking
a
lot
of
knowledge
in
from
X
and
from
snag.
So
it's
it.
It's
really
great
to
have
this
ecosystem
created
around
this
intelligent
data
that
will
just
be
able
to
apply
in
different
tools.
That's
I!
Think
yeah!
C
That's
that's!
That's
what
I
like
to
see,
especially
as
it
came
up
so
strong
in
the
amnion
survey.
There
was
a
developer's
satisfaction
survey
that
ran
a
lot
of
people
were
involved,
it's
run
through
da
and
the
N
governance
model,
so
I
have
to
involve
Google
Microsoft
Mozilla
Samsung
w3c.
So
a
lot
of
people
had
input
on
what
we
should
ask
developers
about
and
big
part.
It's
like.
C
How
satisfied
are
you
with
development
on
the
web
and
what
are
the
biggest
pain
points
and
four
out
of
the
five
pain
points
were
about
web
bility
and
cross-browser
testing,
so
people
really
want
to
like
it's
a
pimper.
Imagine
is
just
switching
between
browsers
is
hard
so
and
knowing
what
to
look
for
so
weapon
being
able
to
like
be
in
more
browsers
and
being
able
to
tell
you
in
one
browser
what
might
not
work
in
another
browser
is
really
changing
the
paradigm
of
dev
tools,
which
was
already
very
kinda.
C
This
one
browser
this
one
version
oriented
versus
it
can
kind
of
funny
break
out
of
the
box
and
be
I
can
tell
you
like
this
will
not
work
in
Safari
and
this
might
nerve
work,
and
so
people
can
open
intently,
the
right
browser
and
look
for
it
and
then
check.
Yes,
it's
actually
working.
So
that's
just
kind
of
cool
yep.
B
Absolutely
cool
well
I
think
that
pretty
much
does
it
for
our
AMA
we're
almost
right
at
an
hour.
So
I
wanted
to
thank
our
panelists,
Harold
and
Tony
for
joining
us
and
definitely
encourage
folks
who
are
watching
to
check
out
web
hentai.
Oh
so
the
website
is
web
hint
dot,
io
and
the
github
repo
is
web
hint
io
we're
on
twitter
at
weapon,
io
just
search
for
web
hand.
Io
you'll
probably
find
us
we'd
love
to
have
more
foot
more
folks.
Try
out
the
project.