►
From YouTube: Backdrop Weekly - Sept 8th 2022
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
Hi
everyone,
it's
September,
8th
2022-
and
this
is
the
backdrop
weekly
developer
meeting.
We
get
together
every
week
to
talk
about
priorities
facing
the
backdrop
project
and
usually
with
a
heavy
focus
on
core
this
week
is
the
is
one
week
out
from
the
release
of
backdrop,
123
we're
in
the
calm
period,
sort
of
between
feature
freeze,
which
happened
on
September
1st
and
the
release
that
happens:
September
15th.
A
So
this
meeting
we'll
we'll
talk
about
the
last
minute,
changes
that
are
still
happening
in
123
and
also
other
areas
that
we
can
put
some
effort
towards
before
we
open
up
core
for
new
development
again,
so
we'll
do
introductions
of
those
present.
My
name
is
Nate
Lampton
I'm,
core
committer
for
the
backdoor
project
and
I'm,
calling
from
Oakland
California
we'll
go
to
Joseph
and
then
Jen
hi.
B
I'm
Joseph
I'm
a
developer
for
from
Las
Vegas
Nevada.
C
Jen
Jen
Lampton
also
joining
from
Oakland
California,
and
do
you
want
me
to
go
into
Community
contributions?
Okay,
there's
one
new
contrib
module
this
week
from
Robert
Lang
energy
cash,
Administration
I'm,
not
sure
what
it
does.
I
haven't
looked
at
it
yet,
but
it
looks
interesting.
B
A
All
right,
let's
see
General
discussion,
we
had
a
a
question
brought
up.
Yorkshire
pudding,
I
believe
raised
the
issue
that
is
reared
its
head
many
times
before
issue
38
to
24,
and
the
title
of
this
issue
is
thorough
warning.
If
Max
input
virus
is
not
properly
set,
we've
had
a
pull
request
for
this
in
the
works
for
quite
a
while,
actually
I,
don't
know.
This
is
open
in
2019.
A
and
Jen
actually
just
spent
the
last
couple
of
like
our
like
getting
that
one
updated
and
re-rolled.
So
we
now
have
a
fresh
pull
request
there
to
take
a
look
at
and
review
you
wanna
say
anything
about
that.
Jen.
C
Looks
like
it's
still
failing
tests.
I
can't
get
the
same
tests
to
fail
on
my
local
computer,
so
I'm
trying
to
figure
out
why
that
is.
A
I
was
I,
was
thinking,
I
looked
at
this
pull
request
and
the
status
report
portion
of
it
is
entirely
independent,
could
be
done
separately
and
also
as
almost
no
impact
on
existing
sites.
It's
literally
just
a
warning
saying:
hey,
you're,
probably
gonna
have
a
problem
if
you
use
the
default
value
of
a
thousand
so.
C
A
C
A
Possible,
yeah
and-
and
it
is
kind
of
a
good
opportunity
right
now
doing
it
at
123,
because
it
it
might
be
I
mean
it
will
be
somewhat
alarming.
Quite
literally,
you
know
that
the
status
report
will
be
throwing
a
warning
and
when
previously
it
wasn't-
and
all
you
did
was
update
core
right,
you
didn't
do
anything
and
something
is
wrong,
but
that's
not
the
fault
of
the
person
doing
the
upgrade.
A
That's
just
literally
like
it's
always
been
wrong,
and
you
just
haven't
known
about
it
and
for
a
lot
of
people,
the
the
default
value
is
actually
fine,
so
yeah
I
mean
for
a
little
while
at
least
right
people
don't
usually
run
into
it
until
you
know
they
get.
You
know
a
couple
dozen
contrib
modules
installed
in
the
permissions
page
get
or
or
something
like
field
permissions.
A
Yeah
I
have
to
wonder
if
that
would
have
helped
Martin
in
this
situation
that
you
know
he
might
not
have
known
about
it.
Yeah.
C
It
definitely
would
help
me
because
every
time
like
you
inherit
a
new
site
triple
seven
Drupal
nine
backed
up
whatever
you
never
know
what
hosting
platform
it's
on
like
what
they've
got
things
set
at
and
I
ran
into
this
problem.
Earlier
this
week
on
a
Drupal,
7
side,
I
hadn't
worked
on
for
a
while,
because
we
just
updated
Aqua.
We
made
everyone
update
to
php8
and
guess
what
default
value
is
still
a
thousand,
and
so
the
site
that
was
working
on
Triple
Seven
didn't
work
on
Drupal
8.
C
A
Let's
see
we
have
a
documentation
page
for
this
already,
which
is
great
docs,
dot
backdrop
cms.org
Max
Dash
input
Dash
bars,
so
you
couldn't
get
them
more
clear
URL,
because
we'll
probably
you
know,
need
to
point
at
this
page
in
our
documentation.
A
B
A
A
Interesting,
okay!
Well
anyway,
that
would
be
great
to
fix.
This
is
also
kind
of
interesting
that
in
some
situations,
HT
access
can
be
used
to
increase
the
max
input
vars,
because.
A
B
Sorry
take
a
look.
B
B
A
A
Yeah
so
I
think
that's
the
the
fastest
way
to
move
forward
is
just
pull
out.
The
status
report
make
that
its
own
thing
and
then
I
don't
know
if
you
want
to
take
your
current
pull
request
that
you
know
dynamically,
identifies
it
and
and
move
that
into
its
own
separate
issue
or
if
you
want
to
keep
this
one
open
and
keep
working
in
there.
A
Okay,
great
all
right,
let's
see
so
in
the
world
of
Bank
jump
123.
A
Let's
see
one
thing
to
note
is
that
we
did
get
in
one
last
feature
request
after
last
week's
meeting,
so
last
week's
meeting
was
the
was
feature
freeze
day
and
although
we
didn't
actually
finish
it
on
feature
freeze
day,
we
merged
it
before
the
preview
release
was
released,
and
that
was
the
the
cleanup
of
the
user
profile
page
with
vertical
tabs.
As
a
user
experience
fix,
it
actually
kind
of
was
not
not
kind
of
but
could
be
permitted
even
during
or
after
the
preview
release.
A
So
we
still
kind
of
were
within
our
own
rules
there,
but
we
also
got
it
out
before
the
preview
release.
So
right
now
the
preview
release
is
still
cutting
edge.
It's
got
everything
in
it
and,
if
you're
looking
at
checking
out
what
123
is
going
to
do,
the
preview
release
is
great
place
to
look
so,
let's
see
that
was
issue
3872
and
that
has
been
completed
and
merged.
A
that
seemingly
after
after
merging
the
hi
to
title
hide
comment.
Titles
issue
that
it
caused
a
test
to
fail
in
comment
test,
but
that
failure
is
not
actually
bubbling
up
to
be
reported
as
a
failure
in
GitHub.
So
it
turns
out
there's
actually
a
syntax
error
where
there's
like
a
missing
semicolon.
A
So
that's
a
little
embarrassing
that
that
we
have
a
missing
semicolon
in
there
and
what
seems
to
be
happening
is
that
the
test
is
kind
of
silently
crashing
I.
Think
if
you
looked
at
the
GitHub
actions,
log
you'd
probably
see
the
crash,
but
it's
not
being
reported
upwards
as
a
failure
to
the
pull
request.
So
issue
5764
fixes
the
comments.
A
Syntax
error
comment
test
syntax
error,
but
there's
actually
another
test
failure.
That
is
still
happening
on
that
pull
request.
So
so
we
have
a
little
bit
of
sleuthing
to
do
to
to
get
the
comment
tests
running
again.
In
the
meantime,
it's
not
hold
actually
holding
up
any
other
development
work,
but
the
comment
test
is
just
not
being
executed
because
it
crashes
with
the
syntax
error.
A
So
it
doesn't
really
stop
other
development,
because
not
all
pull
requests
are
failing
their
tests,
at
least
according
to
GitHub,
but
is
it's
about
a
combination
of
both
like
undesirable
and
something
that
we
should
get
fixed
so
that
we
have
full
test
coverage
again
as
soon
as
possible?
So
that's
definitely
a
priority
for
us.
I'm
sure
Greg
could
use
some
help
getting
that
running.
He
filed
a
pull
request
a
couple
days
ago,
but
that
was
just
fixing
the
syntax
error
and
there's
a
couple.
A
The
other
failures
will
probably
require
a
little
bit
of
Investigation
to
get
worked
out
and
in
response
to
that
pull
request,
there's
or
that
issue.
There's
some
obvious
shortcomings
that
we
should
try
to
address
like
a
syntax
error,
should
count
as
a
failure
on
our
test
and
I
think
it
does
actually
syntax
errors.
In
the
rest
of
backdrop,
the
tests
catch
the
syntax
error
and
then
report
this
index
error
as
as
a
failure.
A
You
know
when
you
get
a
an
air
500,
instead
of
instead
of
a
page
back,
the
tests
fail,
but
in
this
case
the
failure
actually
was
in
the
test
files
themselves
and
apparently
that
doesn't
get
caught
well.
One
solution
to
that
the
Indigo
Zella
raised
is
that
if
we
had
a
code
lender
running
on
all
of
core,
that
would
find
identify
and
stop
these
sorts
of
problems
from
happening.
A
So
that
issue
is
52.45.
A
She
kind
of
appointed
at
this
one
again
because
she'd
been
working
on
a
parallel
issue
as
well
issue,
5296
to
add
PHP,
lint
and
PHP
lint
only
checks
for
major
things
like
like
syntax
errors,
but
doesn't
check
for
code
styling
like
tabs
versus
spaces,
and
she
pointed
out
that
if
we
use
phpcs
for
syntax
checking
that
there's
also
a
simple
plugin
for
phpcs,
that
also
does
linting.
So
we
don't
need
two
separate
tools
if
we
get
phpcs
in
there,
because
it
can
also
do
the
linting.
A
However,
this
phpcs
issue
has
been
going
on
for
a
while
I
think
that
we've
got
all
the
blockers
out
of
the
way
we
now
have
new,
like
repository
for
where
the
work
is
going
on,
I
think
the
code
is
in
it
and
and
indigozella
has
updated.
The
pull
request
recently
so
I
think
that
this
doesn't
need
anything
new.
It
doesn't
have
any
blockers,
it
just
needs
some
review
and
some
help
to
move
forward.
A
Okay,
that's
all
that
I've
got
actually
for
today.
You
know
123
is
is
definitely
where
our
focus
is
we're
kind
of
in
this.
A
It's
not
really
a
total
code
freeze,
because
we
can
still
do
bug,
fixes
the
Arya
TBC
list
and
actually
the
issues
that
are
in
the
122.3
Milestone,
there's
actually
quite
a
few
of
them
in
there.
Let
me
see
there
are,
which
is.
A
Wow
19
actually
open
pull
requests
that
are
rtbc
already,
and
so
we
can
work
through
those
as
soon
as
possible
to
try
to
get
them
completed.
Well,
if
we
get
these
in
that'll
bring
our
total
number
of
bug
fix
issues
down
to
26
issues
that
would
be
great.
A
historical
low
got
some
bug.
Fixers,
yeah
well,
I
think
the
herb
dual
has
been
a
little
bit
more
aggressive
about
like
cleaning
up
the
the
minor
or
sorry.
A
Like
if
something
hasn't
had
any
activity
or
we've
changed
our
Direction
on
it
and
he
pulls
it
back
out
of
the
the
bug
fix
Milestone,
which
has
been
making
sense.
A
Okay,
I,
don't
have
any
other
topics
for
today.
Anything
else
you
guys
want
to
talk
about.
There's
a
new
pull.
C
I've
labeled
it
as
a
milestone
candidate.
So
if
someone
else
can
add
the
Milestone,
then
at
least
we
can
track
it
in
the
Milestone
and
see
if
it'll
get
in
issue
number
is
five:
seven.
Seven
one.
A
Great
yeah
and
then
the
your
the
other
issue,
3824,
could
potentially
be
pulled
out
of
the
Milestone
yeah.
A
Yeah-
and
actually
this
is
kind
of
interesting,
because
this,
like
just
said
earlier,
like
doing
it
during
the
minor
release,
has
some
benefit,
because
the
warning
shows
up
because,
like
you've
updated
to
the
new
minor
version
and
it
identify
something
else
so
doing
this
one
actually
shouldn't
be
in.
Oh,
you
already
did
you
said
you
said
minor.
Sorry,
it's
a
candidate
for
minor,
not
bug
fix,
yeah,
that's
great
okay,
yeah
I'll,
just
go
ahead
and
second,
that
I'm
I'll,
put
you
as
The
Advocate.
Is
that
okay?
Yes,.
A
C
C
I
create
an
issue
to
talk
about
it,
and
so
there's
going
to
be
a
bunch
of
like
relatively
recent
Ally
issues
in
the
in
the
queue
with
all
of
that
stuff
on
it,
I'm
hoping
to
work
on
some
of
those
during
open
source
day,
because
those
are
usually
minor.
Markup
changes
that
are
reasonable
for
new
people
to
work
on,
which
is
great,
but
I'm
not
entirely
sure.
C
If
all
of
them
are
things
that
belong
in
core
right,
because
because
there's
things
that
like
we
could
due
to
improve
core
as
we
ship
it
that
it
isn't
necessarily
going
to
improve
the
end
result
of
the
website
that
people
are
building
like
I'm,
not
sure
making
core
more
accessible.
With
like
the
basis
theme
in
the
current
home
page,
configuration
is
gonna
make
sites
that
build
with
backdrop
more
accessible,
so
I
could
use
some
feedback
on
those
as
like
it
should
that's.
C
Should
that
still
be
a
priority,
because
I've
been
sort
of
operating
under
that
like
if
it
we
should
just
make
it
accessible.
If
we
can
but
yeah
I,
don't
know
I
guess
getting
some
more
feedback
on
how
to
establish
patterns
versus
individual
Pages,
because
accessibility
of
every
page
is
individual
right,
like
the
structure
of
every
single
page
and
so
even
on
one
site,
like
a
pattern
that
you
put
on
the
home
page,
isn't
necessarily
going
to
work
on
another
page,
and
so
it's
really
hard
to
build
an
accessible
framework.
C
C
C
Have
I
have
been
creating
issues
around
accessibility,
just
because
that's
what's
happening
in
my
regular
work
and
when
I
see
something
that
backdrop
can
benefit.
I
can
create
it,
but
when
I
create
the
issue,
my
intent
is
like.
Oh,
this
is
great.
It's
a
minor
markup
change.
We
can
use
it
for
open
source
day,
but
in
the
back
of
my
head,
I'm
thinking
is
this
the
best
solution
for
a
backdrop
and
part
of
it
is
because
I
don't
know
how
a
pat
like
okay.
C
So
let
me
use
a
specific
example
instead
of
talking
about
it
generally,
if
you
have
an
image
that
links
to
another
page,
the
alternate
text
for
that
image
needs
to
tell
the
screen
reader
where
the
link
goes,
and
so
it
does
yeah
question.
C
C
B
C
The
question
is
like
we
have
these
scenarios
built
into
core,
where
on
any
image
using
image
formatter,
you
can
choose
it
to
link
it
to
the
content
or
link
it
to
the
file,
and
the
alternate
text
needs
to
be
different
in
those
two
scenarios,
and
so
the
question
so
I
built
in
a
just
a
little
change
to
the
link
formatter.
That
was
like
if
the
link
is
to
content,
then
put
in
the
alternate
text.
That's
the
title
of
the
content,
so
people.
C
If
the
link
is
the
file,
you
know
we
could
figure
out,
it
would
be
like
view
image
or
whatever
like
text
we
want
in
there
instead,
and
that
was
the
solution
we
ended
up
implementing
for
our
site
because
we
knew
it
would
catch
all
linked
images.
C
So
that
would
work
fine,
but
the
people
I'm
working
with
are
there's
a
bunch
of
ways
you
can
solve
this
problem
like
one
of
them
is,
you
could
just
say
if
it's,
for
example,
an
image
and
a
teaser,
you
could
just
Mark
that
image
as
like
tab
index
minus
one
to
make
it
invisible
to
the
page,
because
the
teaser
has
a
heading
tag
that
links
to
its
destination,
and
so
you
don't
want
the
screen
reader
to
go.
C
Link
page
two
link
page
two,
because
it's
got
the
image
and
the
heading,
and
so
even
though,
that's
how
like
more
helpful
than
like
having
a
link-
and
you
don't
know
where
it
goes,
and
it
being
like
a
beautiful
sunset
and
you're
like.
But
it's
a
link
like
what
is
a
beautiful
sense.
I
have
to
do
anything
right.
That
would
be
the
if
we
were
using
the
alternate
text
for
the
image
instead
of
the
destination,
even
though
having
it
said
twice
is
better
than
that.
C
The
best
possible
experience
is
to
have
it
only
said
once
right.
So
the
question
is
like:
how
do
we
build
something
like
that
into
backdrop
core
right,
because
we
don't
know
whether
that
image
is
going
to
be
like
linked
to
content
in
a
view
where
there
isn't
a
heading
or
a
link
to
content
in
a
View
mode
where
there
is
a
heading
or
even,
if
you're,
in
a
View
mode
and
there's
a
heading?
C
If
the
heading
is
in
the
link,
if
the
image
is
the
only
link
like
there's
so
many
customizations,
you
can
do
that
page.
Your
choice
for
what
can
make
it
most
accessible
is
very
specific
to
what
you're
doing
so
in
general.
My
thought
is
well,
let's
do
the
thing:
that's
not
bad
and
not
the
thing
that
might
be
the
best,
because
we
aren't
going
to
be
able
to
know
what
the
thing
that
is
the
best
is
until
it's,
we
have
a
specific
page
to
diagnose
so
yeah
I,
just
I.
C
Guess
for
this
meeting,
my
note
would
be
like
if
anyone
has
thoughts
on
accessibility
you
can
play
in
on
some
of
these
issues
about
what
the
scenarios
are.
Where
changes
are
significant
improvements
or
not.
That
will
be.
A
Yeah
yeah,
here's
a
I'll
put
this
in
the
zoom
chat,
but
I
know
it's
not
helpful
for
everybody
else,
but
the
the
the
w3c
has
a
tutorial
on
what
they
call
functional
images.
That
seems
to
be
kind
of
what
this
is
mostly
talking
about.
Where
yeah,
that's
exactly
what
you
said.
Basically,
that's,
like
you
shouldn't
describe
the
content
of
an
image
if
an
image
serves
a
purpose
like
instead
of
the
logo.
It's
it's
a
typical
example
of
the
logo
and
the
header
saying
the
logo
of
my
company.
A
It
should
say:
go
back
to
the
home
page,
so
it
should
say
what
that
image
does,
rather
than
what
is
in
the
content
of
it,
but
I.
But
this
is
in
a
particular
situation
where
it's
like
this
specifically
describing
them
as
functional
images,
which
I
don't
think.
That's
necessarily
the
same
thing
as
images
that
are
part
of
content.
Like
a
the
example
used
where
it's
like
a
teaser
or
maybe
a
card
right,
where
there's
like
a
link
to
the
content
and
then
immediately,
there's
also
an
image
that
also
links
to
the
content.
C
As
long
as
it's
not
a
link,
you
have
to
remove
the
link.
If
you
want
to
use
the
description
of
the
image,
because
otherwise
it
will
say,
link
and
then
it
will
say
a
beautiful
sunset
and
that
doesn't
tell
the
person
who's
listening
where
that
link
goes,
they
don't
know
if
it
goes
to
the
content,
they
don't
know
if
it
goes
anywhere
else.
They
still
need
to
know
where
that
link
goes.
B
A
My
interpretation
of
this
page
doesn't
say
that
that's
what
should
happen
that
this,
the
description
of
where
link
should
be
used
is
only
for
images.
That's
only
serve
one
purpose.
You
know
that
they're
they're,
really
like
the
the
logo,
is
actually
the
home
page
link,
for
example,
that
that's
really
its
purpose.
You
don't
even
care
that
it's
the
logo
of
the
company,
but
an
image
is
like,
if
there's
actually
like
a
yeah,
something
that
is
like
a
an
image
related
to
the
contents
of
an
article.
C
C
There
might
be
some
alternate
solution.
It's
like
you
can
add
Aria
attributes
to
the
Anchor
tag
which
I,
don't
think
is
normally
a
thing,
but
maybe
that
might
be
a
way
to
get
around
it.
C
A
Is
a
good
solution
for
carts,
but
not
in
all
situations
like
again,
it's
like
site-specific,
because
sometimes
you
have
multiple
things
inside
of
the
card,
like
maybe
a
short
sentence,
or
something
like
that.
That
might
also
have
a
link
in
it
or
a
taxonomy
term.
That
might
also
have
a
link,
so
sometimes
cards
aren't
themselves
always
the
entire
thing.
One
link,
oh.
C
C
Then
you
can
link
the
image
and
the
heading
and
you'd
have
the
text
you
need
in
there
without
having
it
duplicated,
but
I
couldn't
figure
out
like
so
that
would
be
like
a
lot
of
pre-processing
to
shove.
The
image
into
the
dollar
sign
title
variable
in
the
node
template,
which
seemed
like
a
bad
idea.
C
B
B
B
A
A
C
We
could
also
have
default
value
set,
so
when
you
said
link
to
like
it
would
buy
automatically
be
like
file
image,
alt
or
whatever
the
token.
And
then
when
you
switch
to
link
to
content,
it
could
go
node
title
and
when
you
switch
back
to
image
it
could
go
file
image
alt
again,
so
that
you
would
know
like
when
you
change.
You
could
see
an
example
of
what
we're
like
this
is
what
you
should
hear
some
good
defaults.
But
then,
if
people
were
like,
oh
I,
don't
want
that.
A
I've
been
to
W3
see
example
of
it's
described
as
combining
adjacent
image
and
text
links
for
the
same
resource.
That
sounds
like
what
we're
talking
about.
A
A
B
C
B
And
that's
that
would
be
a
property
on
the
HTML
element.
B
A
I
mean
unfeasible
for
I
mean
most
situations
like
the
styling
of
this
would
just
be
way
more
difficult,
but
it's
it's
interesting
and
wouldn't
work
for
something
that
is
like
a
field-based
system
like
a
Content
management
system.
Unless
you
started
doing
crazy
things
like
crazy
things
like
how.
C
B
A
B
A
I
was
sorry
going
on
a
tangent
here.
I've
been
building
out
a
backdrop
site
recently
and
the
the
layout
system's
ability
to
like
move.
The
title
around
is
pretty
incredible,
but
one
thing
that
I
found
that
well
I
I
almost
missed
it.
I
was
like
it
would
be
nice
if
I
could
take
the
title
and
the
title
of
the
page
and
use
that
as
the
title
of
a
block.
A
But
then
I
realized
that
wasn't
necessary
because
I
can
just
place
the
title
block
and
then
remove
all
the
wrappers
from
it
and
then
I
can
move
the
title
around
anywhere.
I
want
on
the
page,
yeah
so
kind
of
similar,
actually
that
the
layout
title
can
take
the
title
of
any
block
on
the
the
page
and
then
and
then
use
that
it's
kind
of
I
don't
know
it's
not
I'm
just
saying
in
some
places
we
actually
have
systems
that
are
flexible
enough
to
handle.
This
kind
of
you
know
complicated
situation,
yeah.
B
A
Very
complex.
C
C
C
Here
it
is
issue,
remember,
seven,
five,
seven,
six,
five.
B
A
A
Yeah,
let's
weigh
in
there
on
the
issue.
If
we
have
additional
feedback
to
get
it
saved
for
posterity
I,
don't
have
any
other
topics
for
today.
We
kind
of
already
just
want
to
attention
just
to
just
because.
A
Because
we
had
time
exactly
so,
let's
let's
go
ahead
and
wrap
up
for
today,
thanks
again
to
all
of
our
contributors
for
excellent
work,
going
into
the
123
release,
it's
going
to
be
a
really
great
release,
there's
just
a
fantastic
collection
of
functionality.
A
You
know
we
tried
not
to
save
everything
for
the
last
minute.
We
might,
you
know,
had
some
successes
with
that,
especially
with
entity
reference.
But
then
you
know
at
the
end
of
it,
like
the
last
six
pull
requests
all
came
in
the
last
two
days,
so
for
better,
whereas
deadlines
work
and
yeah,
it
was
great
release
in
the
way
that
we
got
all
of
these
substantial
features
in
for
the
release
coming
out
next
week.
So
let's
go
ahead
and
call
it
for
today.