#microformats 2016-05-10

2016-05-10 UTC
laughinghan, tantek, sagerdearia, gRegorLove, dogada, Left_Turn, trevor-b, trevor_b, nitot, ben_thatmustbeme, hober, gRegorLove_, KartikPrabhu and willnorris joined the channel
#
willnorris
I get that a "value" is added on child elements that are both a property of an "outer" microformat, as well as have a microformat themselves (that was added around June of last year I think). But that's not the case in this example
#
kylewm
willnorris: I agree with you; think the "value" should not be there
#
Loqi
kylewm: tantek left you a message 1 week, 1 day ago: heads-up, since glennjones and adactio (as well as aaronpk and myself) will be at IWC Düsseldorf this weekend, I may take that opportunity to come to consensus resolutions on all outstanding mf2 parsing issues. Please add your opinions to http://microformats.org/wiki/microformats2-parsing-issues ASAP!
#
willnorris
okay, thanks. I'll file a bug
laughinghan and tantek joined the channel
#
kylewm
gRegorLove: "and is a property element" is the difference there
#
kylewm
it is a child h-* element, but not a p-*, u-*, e-*, dt-*
#
kylewm
(in other words, there's no property for the element to be the "value" of)
#
gRegorLove
Makes sense
#
gRegorLove
Looks like mf2py handles it correctly, php-mf2 doesn't.
willnorris joined the channel
#
kylewm
how about microformats-shiv?
#
gRegorLove
I think that's what generates the test results in that repo linked.
#
gRegorLove
Yeah, mf-shiv includes the value
#
kylewm
interesting
tantek joined the channel
#
kylewm
ack, race condition
#
kylewm
gRegorLove: i filed one for microformats-shiv https://github.com/glennjones/microformat-shiv/issues/26
KartikPrabhu, tantek, sagerdearia, willnorris and laughinghan joined the channel