#microformats 2025-07-03

2025-07-03 UTC
#
sugardave for instance:
#
sugardave with my image issue, this works:
#
sugardave class="u-photo"
#
sugardave ```
#
sugardave ```
#
sugardave ```
#
sugardave but this doesn't:
#
sugardave class="u-photo w-28 h-28 rounded-full mb-4 shadow"
#
sugardave ```
#
sugardave grr
#
[tantek] wonder what part of the toolchain is misinterpreting a space delimited class attribute value
#
sugardave GitHub copilot says:
#
sugardave > This is a known issue with some microformats parsers being overly strict about class attribute parsing.
#
sugardave but it could just be guessing 🙂
#
[tantek] yeah it's wrong
#
[tantek] "overly strict" is also wrong
#
[tantek] GitHubCopilot--
#
Loqi GitHubCopilot has -1 karma over the last year
#
sugardave lol
#
[tantek] oh it's possibly (likely) the "h-28"
#
[tantek] which I'm guessing some microformats parsers are interpreting as a new root class
#
[tantek] but that shouldn't break the u-photo
#
sugardave src={imgSrc}
#
sugardave <Image
#
sugardave <div class="w-28 h-28 rounded-full mb-4 shadow overflow-hidden">
#
sugardave ```
#
sugardave not sure that's it because I tried its first suggestion with a wrapper:
#
sugardave class="u-photo w-full h-full object-cover"
#
sugardave alt="Profile Picture"
#
sugardave />
#
sugardave </div>
#
sugardave ```
#
sugardave oh...but that still has an `h-` hmmm...trying the second alternative now and just style it up
#
[tantek] the parsing spec says to reject h-n where n is a number but that might not be implemented by all parsers
#
[tantek] presuming this is from tailwind, looks like there's an issue discussing it: https://github.com/microformats/microformats2-parsing/issues/59
#
sugardave ah, that is probably it! thanks for brainstorming with me
sebbu joined the channel
#
[tantek] 👍
#
cookiezi1170 whats a microformat
#
[tantek] gotta ask that in the #indieweb-dev channel! (with "what is" 🙂 )
barnaby, Saige_Leah, [pfefferle], [KevinMarks], gRegor, [aciccarello], plantroon and angelo joined the channel