#microformats 2017-07-29

2017-07-29 UTC
KartikPrabhu, davidmead, [miklb], tantek, nitot, deep-book-gk_, [jeremycherfas], gRegorLove and [jemostrom] joined the channel
#
Zegnat Hmm, u- parsing order is biting me. Say you have a partial feed as per http://indieweb.org/h-feed#partial_feeds where you want to provide a u-url for the feed but don’t want that URL as an A element on the feed title (because it is unnecessary). I thought I would fix this by using <data class="u-url" value="#relative">title</data>. But turns out re
#
Zegnat lative URLs aren’t resolved for DATA elements because of parser order.
#
Zegnat Filed https://github.com/microformats/microformats2-parsing/issues/10
#
Loqi [Zegnat] #10 When should u- values be normalised to absolute URLs?
[kevinmarks] joined the channel
#
Zegnat sknebel that might interest you as well ^^^
ben_thatmustbeme and [miklb] joined the channel
#
Zegnat Wait … why can’t LINK elements be used for u- properties?
#
Zegnat Parsers must already read them for finding all the rel links.
KartikPrabhu and [kevinmarks] joined the channel
#
[kevinmarks] Because they are hoisted to the head I think, they don't stay in the body
#
Zegnat The rel value decides if the LINK is allowed in the body. But non-HTML "specifications can also define body-ok keywords", so we could make e.g. rel-me allowed.
#
Zegnat And even if they are only allowed in the head, IndieWeb sometimes recommend putting a root format on the html element so link elements would definitely be within
#
Zegnat No hoisting should apply
[eddie] and rodolfojcj joined the channel
#
sknebel that body-ok stuff is relatively new I think
#
sknebel do you have specific use case for using LINK, Zegnat?
#
Zegnat Needed to do an invisible metadata for email. Wanted to do <link class="u-email" rel="me" href="mailto:">, but now I needed to use an A
#
Zegnat But of course A elements become valid tab targets and all that jazz, so then you need to do display:none; and possibly a tabindex="-1"
rodolfojcj joined the channel
#
Zegnat Normally I would use DATA elements for invisible data, but DATA can’t have a rel attribute.
#
sknebel ah
#
Zegnat aaronpk uses LINK for hidden rel-me values, e.g. for RelMeAuth over SMS. If he would have wanted to also include his phone number in his h-card he can’t just add class="u-phone" but will have to use another element entirely.
#
Zegnat Mostly it just doesn’t make sense to me that href attributes are taken from A and AREA but not LINK.
#
Zegnat LINK is also explicitly allowed within BODY if it has an itemprop attribute. So for people who are looking to make schema data available through microformats it might be essential to have LINK get parsed. (Not sure, not good with schema, but I can see this come up.)
#
sknebel the microdata use case seems similar, yes. hidden u- values
#
Zegnat Yep. So just something I ran into today. But wasn’t sure if there were specific reasons and didn’t want to file it as an issue.
#
Zegnat Unlike the URL normalisation one, which I ran into when doing invisible URL data, and is a lot more annoying
rodolfojcj, KartikPrabhu and davidmead joined the channel