►
From YouTube: YUI Open RoundTable 12/13/2012
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
There
is
a
page
called
round
table
topics
and
there's
an
upcoming
section
there
that
if
you
have
something
that
you
want
to
talk
about
for
the,
why
do
I
really
able
to
include
that
from
the
bottom
we
sort
of
some
things,
often
the
top,
and
if
you
are
watching-
and
this
will
help
you
decide
if
you
want
to
come
in
on
this,
the
round
table
or
I
chose
a
topic
that
you
want
to
brace
for
the
people.
You
can
not
add
it
to
hear.
A
What's
been
happening
every
time
we
mention
things
in
like
why
why
weekly
we've
been
bringing
this
up,
we
haven't
done
a
specific
for
a
while.
We
haven't
done
a
specific,
closing,
hey,
there's
Yui
round
table
every
week
at
2pm,
okay,
I
think
starting
next
week
like
to
begin
the
week.
I
will
start,
we
will
do
it.
Every
week
we
make
post
like
once
a
week
ourselves,
reminding.
A
A
A
D
Have
the
presentation
that
I've
been
starting
to
put
together
for
promises
as
pertains
to
just
understanding
how
promises
work
and
Doug's
talk
just
came
out
and
it
does
a
pretty
decent
job
of
explaining
them
technically,
and
so
this
is
sort
of
a
boxes
and
arrows
version
of
what
his
talked
says.
I'll,
probably
at
some
point,
do
a
screencast
of
that
so
may
as
well
make
it
sort
of
an
open
screencast
since
the
plan.
So
far
as
I
know
it
is
that
the
promise
work
that
I
have
done.
B
D
The
idea
is
that
well,
there's
two
parts
to
it:
there's
the
resolver
side
and
then
there's
the
promise
implementation
side,
and
so
we
expect
out
the
promise
implementation
side
and
we
got
wide
by
n.
The
only
one
that's
outstanding
didn't
have
a
specific
representation
was
jquery,
but
there's
more
of
a
complicated
story
about
that
as
well.
But
if
you
remember
from
Doug's
talk,
he
suggested
that
promises
weren't
likely
to
go
into
the
language
itself
before
maybe
being
implemented
on
the
Dom
side
of
things.
D
But
working
with
the
w3c
is
a
challenge
and
I
believe
that
Alex
Russell,
and
why
cats
and
gosh
I
can't
remember
who
else
it
was.
There
were
a
couple
other
people
that
were
up
for
inclusion
in
the
tag
as
ta
gee
I
forgot
it
stands
for,
but
it
has
to
do
with
how
decisions
are
made
on
the
w3c
as
far
as
how
to
move
that
stuff
forward
and
so
I
believe
Alex
will
be
championing
the
idea
of
promises
making
their
way
into
the
Dom
side
of
things.
So
that's
that's
a
start.
D
A
B
E
B
C
Bit
so
basically,
a
sauce
announced
today
that
they
are
giving
like
open
source
projects
use
free
time
on
sauces
infrastructure.
So
it's
limited
can't
we
is
a
limited
testing,
but
it's
limited
to
how
many
concurrent
be
into
can
run
or
interested
in
using
this
looking
at
how
this
can
work
with
Travis
that
we
already
have
been
in
the
open,
so
yeah,
so
Dave
actually
was
able
to
get
something
working
with
yet
a
pretty
quickly,
and
so
that's
what
we're
looking
at
here
is
sauce.
C
They
have
a
infrastructure
that
allows
for
screen,
recording
of
nearly
I,
think
a
hundred
different
OS
and
our
browser
or
device
combinations-
and
this
is
just
google
chrome,
I
think,
on
mountain
lion
that
was
recorded
for
a
run
with
Yui
with
Yeti,
so
we're
going
to
use
this
kind
of
thing
for
putting
on
traffic,
so
you
can
actually
get
real
browsers
festival
in
gratis
or
something
closer
than
just
using
fantage
ass
right
now.
So
this
is
just
a
recording
right
in
yes,
this
is
a
screen
recording
that
that
sauce
automatically
provides
for
for
us.
C
C
A
A
F
F
I
did
a
quick
inventory
and
these
are
the
components
that
have
tests
a
performance,
perf
or
benchmark
directory
other
tests,
so
that
is
app
attribute
base
cash,
charts
data,
schema
data,
source
data,
table
dial,
event,
custom,
graphics
and
number
and
I
know
a
couple
of
these
are
pretty
old
and
not
using
benchmark
where
they
should
be
so
I
think.
Overall,
we
could
do
a
lot
better.
Some
of
the
underlying
infrastructure
pieces
like
widget
and
litter.
F
So
that's
the
overall
bowl
I
think
that
we've
made
you
know
kind
of
drawn
a
line
in
the
sand
and
made
a
first
stab
at
it,
which
is
great,
but
I
do
want
to
keep
pushing
forward
with
that
task
will
certainly
be
spending
more
time
on
it
next
year,
but
I
wanted
to
do
pick
status
check
on
where
we
are
as
it
today.
What
are
we
with
school?
You
I,
don't
see
anything
I.
H
Haven't
checked
everything
in
wisco
view:
I
was
talking
to
set
again
about
it.
I
think
we're
figuring
out
a
way
to
automate
in
type
of
frames
per
second
or
animation.
Metric
is
gonna,
be
a
little
tricky,
so
I
don't
know
whether
it
will
be
a
manual
or
ideally,
of
course,
it's
going
to
be
automated
very.
F
K
F
H
And
one
thing
that
the
will
need
to
target
to
smoothness
of
the
intermission,
because
you
can
have
a
high
frame
rate,
but
overall
is
an
average
of
the
entire
animation,
but
it
still
needs
to
be
or
something
extraordinary
needs
to
be
as
smooth
as
possible.
So
have
not
much
deviation.
So
that
would
be
something
else
will
be
focusing.
But.
H
C
C
C
C
B
C
C
F
L
K
Before
we
can
automate
I'd
like
first,
like
you
know,
we're
running
our
own
stuff,
I've
got
a
by
own
versions
of
I,
guess,
multi
and
benchmark
running
right.
Now
that
add
adapt
for
work
with
mine,
so
I
guess
you
need
to
I
need
to
figure
out
how
they,
if
that
belongs,
and
whatever
our
benchmark
Jas
file
or
if
someone
offer
offender,
okay,
I,
don't
remember
to
hear
that
I
had
to
do
something.
Okay,.
K
F
F
As
part
of
the
exercise
of
this,
automated
from
CI
will
need
to
check
it
into
source
right.
Does
everyone
agree?
Okay,
does
anyone
object
like
this
is
a
better
question
and
we
have
to
go
ahead
to
do
that.
So
when
we
do
that,
you'll
need
to
make
sure
that
your
again,
how
whatever
is
also
checked
in
to
make
sure
that
your
tests
run
correctly,
so
it
is
that
it's
ice
so.
B
What
do
we
do?
We
have
any
plans
to
try
to
minimize
the
number
of
variables
in
when
we
try
to
compare
test
runs
against
each
other
for
the
benchmarks,
because
it
seems
like
we
could
very
easily
end
up
not
being
able
to
compare
results
if
we're
not
trying
to
isolate
all
potential
variables
that
are
changing.
Besides
the
one
change,
which
is
the
new
code,
do
we
have
any
ideas
on
how
we
can
do
that.
F
Well,
so
my
assumption
is
that
if
we
do,
if
we
have
all
these
perfect
tests
for
every
component,
we're
not
going
to
want
to
run
every
single
component
breath
test
for
every
commit
more
like
each
developer,
as
you're
changing
code
will
want
to
run
the
drug
test
for
that
component
locally
and
then
within
the
CI
environment,
maybe
once
a
day
or
more
likely,
even
once
a
week
and
do
a
basically
a
sanity
check
that
we're
not
regressing
over
time.
Our
performance
but
I.
F
F
B
I
guess
what
I'm
trying
to
get
at
is
like
independent
of
how
frequently
we
do
this
or
what
Delta
we're
comparing
the
or
we're
running
the
benchmarks
on
from
you
know,
one
check
into
10
check-ins
to
once
a
week
or
once
a
month.
How
are
we
going
to
isolate
all
other
potential
variables
between
runs
of
the
benchmarks
like
it's
almost
like?
B
We
need
to
bring
up
a
vm
fresh
with
the
same
version
of
the
browser,
the
same
browser
that
we
want
to
test
this
on
and
then
run
the
test
because,
like
if
I
do
it
locally,
I
could
be.
You
know
something
to
be
going
out
of
my
machine
time.
Machine
could
be
running
and
I
could
run
my
benchmark
and
it'd
be
different,
like
there's
so
many
different
variables
here.
So
when
we
get
like
the
real
true
numbers
that
we
want
to
report,
I'm
just
wondering
how
we
can
work
to.
F
So
problem
with
the
local
environment
and
I
think
you
have
to
take
that
with
a
grain
of
salt
and
run
a
lot
of
runs
to
get
statistical
significance
and
also
that
kind
of
spot
means
you're
looking
at
relative
numbers
more
than
absolute
numbers.
So
even
if
you
got
you
know,
10,000
iteration
was
yesterday.
H
C
Automation
for
the
board
is
truly
statistical.
This
is
just
the
relevant
and
results
or
like
the
to
take
exactly
as
much
time.
What
we
will
get
is
a
being
able
to
pass
see
trends
over
time,
even
if
they're
it
doesn't,
because
the
thing
is,
if
you're
trying
to
do
performance
testing
in
a
vm
for
using
a
grater
or
even
maybe
their
names,
lauren
p.m.
it
can
be
that
the
computer,
that
is,
the
resources
value
at
BMR,
much
more
powerful
than
what
the
average
user
would
would
get
a
tour.
C
F
B
And
if
our
and
if
the
VMS
were
are
out
of
our
control
in
the
sense
that
somebody
else
is
managing
them,
whether
that's
sauce
labs,
Travis,
internal
corporate
yahoo
machines,
we
don't
necessarily
know
if
they're
changing
hardware
and
moving
our
BM
around
and
all
of
a
sudden
having
like
a
performance
degradation
because
we
got
thrown
on
some
crappy
hardware
with
some
other
vm.
That's
taking
up
all
the
machines
really
so
I
just
wanted
to
warn
about
that.
B
F
K
K
G
A
C
F
A
A
A
F
D
D
When
in
modern
browsers,
if
you
click
on
a
disabled
button,
the
event
is
completely
swallowed,
it
behaves
as
if
there
was
no
event,
but
in
IE
clicking
on
that
clicking
on
a
disable
button
is
like
turning
mouse
oven
off.
You
know
the
CSS
style,
where
you
can
turn
my
mind
off
it.
It
just
passes
through
to
its
container
element.
So
it's
like
clicking
on
the
div
that
contains
the
button,
but
not
clicking
on
the
button
itself.
So
so
it
is
related
to
bubbling.
D
It
is
related
to
bubbling
I'm
actually
just
about
to
test
for
academic
purposes
I'm
about
to
test
whether
or
not
the
capture,
phase
click
event
is
also
swallowed
when
clicking
on
a
disabled
element
in
modern
browsers.
It
won't
affect
the
outcome
of
the
bug,
but
it's
just
information
to
have
I
honestly,
I,
don't
know
what
well
delegate
can
be
changed
to
see
if
the
target
is
is
disabled
and
if
it
is
disabled,
then
to
just
escape
to
halt.
So
we.
F
F
B
D
C
C
F
A
E
A
F
D
K
K
C
We
have
like
what
I've
done
is
I
like
run
these
four
yeti
stuff,
as
I
put
I
keep
knowledge
consist
new
until
I
start
working
on
them
and
then
I
marked
them
as
like
accepted
right
and
then,
when
they're
accepted.
That
means
I'm
about
to
work
on,
but
I
don't
know
if
that
is
clear.
That's
that's
kind
of
why
my
tickets
are
assigned
to
me,
but
I
try
to
tell
people
like
if
you
want
to
work
on
this
and
tells
us
like
accepted
that
I
have
you
know
it's
here,
but.
B
L
C
D
That's
fine
for
one
use
case.
I
would
think
that
the
majority
use
case,
though,
is
that
somebody's
coding
and
Yui
and
boom
something
happens,
that's
unexpected,
and
so
they
go.
They
think
it's
a
bug
and
they're
going
to
go
on
search
through
the
bug
database
to
see
if
it's
a
known
bug
before
they
file
a
new
one.
So
they.
A
K
B
F
B
F
A
report
or
anyone
pull
up
the
list
and
on
a
side
pods
and
be
like.
Oh,
this
is
interesting
mark.
This
is
something
that's
important
to
me
and
they
can
feel
free
to
tackle
it,
even
though
it
might
seem
poor
or
important.
I
mean
that's.
The
point
is
that
it
is
kind
of
important,
but
we
are
not
happy
working
on
when.
F
F
J
J
F
F
B
B
Well,
so
if
you
have
github
issues,
I
believe
you
can
just
you
could
assign
it
you
it'll
definitely
autocomplete
for
anyone
who
is
in
the
marked
is
like
some
something
on
the
project
like
has
commit
access,
but
you
may
be
able
to
also
then
mark
people
who
have
Forks
that
may
also
be
in
the
autocomplete
list,
or
you
can
just
probably
type
anybody's
name.
I'd
have
to
look
on
a
different
project.
Can.
F
B
C
F
A
J
D
K
B
I
think
some
of
the
main
things
were
like
Doug
was
open
to
changing
some
stuff,
but
he's
you
know
not
not
as
fast
as
the
community
behind
jeaious
hint
for
changing
things
like
dave
was
able
to
get
the
Yui
Global's
added
as
a
configuration
option,
I
believe,
to
hint
quickly
like
he
just
issued
a
pull
request.
They
accepted
it.
It
was
in
there
so
easier
to
maintain,
but
then
also
some
of
the
other
things
Doug
wasn't
willing
to
accommodate.
B
Were
the
node
environment
using
the
dunder,
dirname
style
variable
names,
even
though
that
that's
something
that's
declared
as
a
global.
If
you
try
to
use
it
in
your
application
code,
which
is
something
provided
by
the
environment,
jayus
lint
complains
that
you
shouldn't
be
using
it
that
way
and
there's
like
really
no
way
to
get
around
it.
So
I
guess
you
could
do
like
global
and
then
reference
it
by
string
name,
but
that
would
just
before
your
it.
Somebody
did
that
also.
F
So
I
don't
know
if
I'm
still
dreaming
on
that
one,
but
I
still
cling
to
that
hope
and
would
like
to
try
to
get
there
next
year.
So
does
anyone
object
to
talking
about
this
and
just
disclosing
the
change
and
summarizing
some
of
the
decision?
The
reasons
behind
the
decision?
Does
anyone
object
to
that?
E
H
H
A
I
B
B
B
F
A
N
We
had
a,
we
had
a
pretty
in-depth
conversation,
how
it
should
be
implemented,
or
at
least
the
initial
structure,
of
how
it
should
how
the
architecture
should
go.
Oh,
that
was
reflected
in
the
the
gist,
the
markdown,
just
that's
that's
up
there
or
that
I
noticed
I'm.
Sorry,
it's
a
wiki
page
that
I
made
on
on
my
fork
so
that
wiki
page
didn't.
N
N
N
B
N
B
N
It
would
just
be
creating
and
overlay
and
loading
an
instance
of
whatever
widget
was
on
the
page
are
moving
the
bounding
box
into
the
content
box
of
the
overlay
that
was
created.
If
the
widget
already
existed
on
the
page,
ok,
but
being
able
to
shift
that
around
by
plugging
it
in
unplugging
it.
What
based
on
what
functionality
you
need
it?
Ok,
so
it's
more
is
more
about
repurposing
the
wheel
that
the
wheels
that
we
have
instead
of
trying
to
recreate
one.
A
N
A
B
The
other
part
he
brought
up
in
the
same
ticket
was
people
moving
from
HTTP
to
HTTPS,
and
that
was
something
that
that
the
browser
is
going
to
enforce,
rightfully
so
on.
A
full
page
reload
on,
like
you're,
not
going
to
be
able
to
update
the
URL
from
a
HTTP
to
an
HTTPS
URL
and
not
cause
the
whole
page
to
be
reloaded
from
the
server.
So
so
those
were
two
related
issues
brought
up
in
the
ticket
and
I,
don't
know
if
anybody
else
has
experience
with
phonegap
that
could
answer
those
questions,
but
I
don't
believe.
A
A
Well,
it
sounds
like
this
topic,
something
that
this
an
example
I
think
of
one
that
would
be
good
to
bring
up
and
in
highlight
for
next
week
to
say:
hey
if
you're
interested
in
discussing
this
come
to
the
round
table
talk
because
I
think
of
sneak
in
and
we
want
to
get
two
parties
involved.
Associate
mark
I
have
what
wheels
to
cover
with
that
and
include
this
book.
B
A
So,
for
me
what
I'll
do
is
remind
folks
about
the
round
table
next
week
get
to
and
highlight.
This
is
one
of
these
that
the
first
topic
there
isn't
anything
else
on
the
on
the
wiki
page.
It
was
there
anything
that
anyone
wanted
to
bring
up
the
community
or
any
other
things
that
came
up
as
a
result
of
our
conversation.
A
C
A
Have
your
last
last
minute
comments
or
anything,
I
encourage
you.
If
you
are
listening
this
video
online
to
go
to
the
round
table
topics
page
on
the
wiki
and
add
new
things
to
the
bottom
and
assign
your
danger,
those
so
that
we
can't
discuss
them
in
future.
Talks
don't
thinks
everybody
for
coming
thanks.