#microformats 2026-01-13

2026-01-13 UTC
baileyyyyyyyyyyy joined the channel
#
[tantek] interesting, I think I have run into a variant of the rel=alternate parsing challenge you ran into [snarfed]
#
[tantek] if you have a site with multiple link rel=icon elements, and want to pick one with a particular "sizes" attribute, the mf2 parser output is insufficient to do so ("sizes" attribute is not included)
#
[tantek] this conversation: https://chat.indieweb.org/microformats/2025-12-18
#
[tantek] we may need to find a structure to expose the type and sizes attributes in addition to href
#
[tantek] there are so many other link attributes, once we have a structure for type, sizes, href, should we "just" include all the attributes on each link rel? https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/link
#
[tantek] using rel values as an array key still makes sense. and then having a nested array inside of the links with that rel (in document source order)
#
[tantek] should we make each index into that nested array either a string (of the href) as it currently is, or an object with keys for each attribute present?
#
[tantek] how much would that disrupt existing clients of mf2 parsers?
#
[tantek] e.g. "rels" collection has a nested "icon" array that can have items like index 0 "https://tantek.com/logo.jpg" if it only has an href, or an object like { href: "https://tantek.com/88x31.png", sizes: "88x31" } if it has other attributes in addition (actual values from my home page)
duanin2, sebbu2, [pfefferle], [schmarty], [snarfed], gRegor, Zegnat, sknebel, Kaja, ehmry, barnaby, [morgan] and btrem joined the channel