►
From YouTube: WebPerfWG call 2023 02 02 - Rage clicks
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
Rage
clicks:
it's
it's
not
something
that
we're
considering
for
Coral
vitals
I'll,
explain
why
in
a
bit,
but
it's
something
that
we've
been
looking
into
in
Chrome
and
that
we're
really
interested
in
and
we're
under
wondering
if
other
people
are
interested
in
standardizing
it.
And
if
this
is
the
right
group,
so
rage
clicks
are
just
when
a
user
clicks
over
and
over
again
in
the
same
spot
and
they're
already
reported
in
a
lot
of
different
analytics
tools.
A
So
it
is,
is
like
a
a
pretty
well-known
metric
already
and
we
have
a
implementation
of
Rage,
quick
synchrome
and
we
do
find
that
it
correlates
pretty
strongly
with
poor
user
experience
on
the
left.
We're
seeing
like
the
percentage
of
if
we
break
down
all
Chrome
navigations
over
a
time
period
and
we
say
put
them
into
buckets
of
good
needs,
Improvement
and
poor
for
CLS
and
for
imp.
We
see
a
higher
percentage
of
the
needs.
A
Improvement
in
poor
navigations
have
rage,
clicks
across
the
board
and
sometimes
dramatically
so
so
we
do
think
the
rich
clicks
are
pretty
indicative
of
a
poor
user
experience
for
our
chromium
implementation,
more
so
on
desktop.
A
But
that
brings
me
to
the
fact
that
there's
actually
a
lot
of
open
questions
about
how
rage
clicks
should
be
defined.
Our
implementation
has
like
a
500,
millisecond
Max
delay
between
clicks.
Other
implementations.
Don't
have
any
delay
just
you
click
the
same
area.
What
does
that
mean
to
click
the
same
area?
We
could
have
like
the
same
X
Y
position,
which
is
what
Chrome
does.
A
You
could
also
have
on
the
same
element,
well
which
element
in
the
the
tree
and
then
should
be
counted
to
the
whole
life
cycle
of
the
page
just
in
the
the
beginning,
and
then
it
is
triple
click
a
bit,
much
of
a
mouse-centric
definition.
A
If
you're
tapping
on
a
phone
do
you
still,
we
still
Define
like
three
or
more
clicks,
like
most
of
them,
implementations,
use
and
I
was
able
to
use
the
ROM
archive
to
kind
of
understand
a
little
bit
about
how
the
definition
actually
affects
what
we
see
for
for
user
rage
clicks
so
on
the
top
is
Chrome's
implementation
and
on
the
bottom,
is
the
rum
archive
data
for
and
pulse
and
on
the
left.
You
can
see
the
percentage
of
page
pages
with
rage.
A
Clicks
on
Android
are
really
different
between
the
two
and
there's
some
differences
in
the
implementation,
where
impulse
is
taking
the
same
element
into
account,
where
Chrome
only
takes
position,
it's
looser
on
the
timing
of
the
rage,
click
and
it's
also
reporting
on
the
first
ping.
A
So
so
all
of
these
small
definitional
changes
are
actually
adding
up
to
to
difference
in
you
know
what
we
see
in
incidents
of
Rage
clicks,
so,
on
my
end,
I'm
going
to
be
doing
some
experiments
in
Chrome
to
see
like
if
we
switch
things
around
change.
A
The
way
we
Define
it
do
we
see
kind
of
these
graphs
over
on
the
left
of
Android
User
Behavior
line
up
more
with
with
what
we
see
on
desktop,
but
one
thing
I
wanted
to
to
also
mention
when
I
talked
to
people
about
rage
clicks,
they
they
often
kind
of
zero.
A
In
on
like
making
the
metric
kind
of
a
perfect
measure
of
user
experience
and
I,
don't
think
it
ever
can
be
like
right
now,
if
I
rank
web
pages
by
their
from
from
worst
to
best
based
on
rage,
clicks,
the
worst
pages
in
the
world
will
be
a
game
where
somebody
clicked
over
and
over
again
like
a
cookie
clicker
and
that
that's
obviously
not
a
bad
user
experience.
A
We
just
weren't
able
to
be
fully
able
to
infer
user
intent
and
and
that's
why
we
don't
think
that
this
is
ever
going
to
be
a
candidate
for
for
a
core
of
vital
metric,
but
we
still
think
it
can
be
a
useful
signal,
and
so
that's
kind
of
like
what
I've
learned
about
rich
clicks
and
what
leads
me
to
a
question
of,
like
are
rage,
clicks
a
good
topic
for
the
web
performance
working
group,
but
we
ever
want
to
have
like
kind
of
a
a
standard
for
what?
What
what
constitutes
your
rage?