#microformats 2026-06-03

2026-06-03 UTC
#
[tantek]
[snarfed] or was it aaronpk, on the suggestion to use "multivalued", in context that makes it seem like every property MUST be multivalued which also isn't accurate. I think multivalue-capable expresses the possibility clearer than before and more as a MAY.
#
[snarfed]
yeah there are two different points here. every mf2 value *is* a list, but not every mf2 value has more than one value inside that list
#
[snarfed]
the first point is the one that usually surprises people
#
[snarfed]
we can definitely distinguish the two points, and make them both
emery, barnaby and yohan joined the channel
#
[KevinMarks]
I think saying that each one is a list is clearer. It also encourages people to write iterator code rather than just dereferencing. The alternative is that you need to type check and null-check each property and nested property and write a lot of conditional code, the way LD forces you to.
emery, barnaby, [Al_Abut] and ZodiacalComet joined the channel
#
ZodiacalComet
Is it expected of a MF2 parser to not catch an audio URL when it has the form `<audio class="u-audio"><source src="URL"></audio>`?
#
[tantek]
that is correct. if you put the property on an element, typically an mf2 parser will only look at the attributes (or textContent) of that element.
#
[tantek]
if you want the 'src' from the <source> element, then you MUST put the u-audio class name directly on that element
#
[tantek]
this line: else if `audio.u-x[src]` or `video.u-x[src]` or `source.u-x[src]` or `iframe.u-x[src]`, then get the `src` attribute
#
ZodiacalComet
Understood. Thanks for the info
#
[tantek]
There is an issue filed on the parser exploring the possibility of expanding u-* parsing on audio/video elements to dig into nested source elements here if you want to add more use-cases / interest: https://github.com/microformats/microformats2-parsing/issues/53
[Sophia_wood], emery and barnabywalters joined the channel