#microformats 2016-01-29

2016-01-29 UTC
#
@jeffwatkins
Are we still using microformats?
(twitter.com/_/status/692868003575132160)
#
tantek
huh - 7/10 prev tweets before that primarily negative = not worth responding to
#
KartikPrabhu
already did
#
@AllTheTwits
Playing with Microformats on my blog
(twitter.com/_/status/692870495402795008)
#
Loqi
[@jeffwatkins] @kartik_prabhu Yeah. I’ve no interest in making something code consumable. Just really looking for good semantic guidelines in age of HTML5.
#
aaronpk
good reply KartikPrabhu
#
KartikPrabhu
it is the "i want a golden hammer but i have no use for it" fallacy
#
Loqi
gives KartikPrabhu a golden hammer but i have no use for it" fallacy
#
tantek
Loqi++
#
Loqi
Loqi has 386 karma
codemonkey, netweb, krijnhoetmer, Chordachi, tantek and KartikPrabhu joined the channel
#
kylewm
Loqi does some interesting stuff with quotation marks
tantek, KartikPrabhu1, Chordachi, nitot, adactio, TallTed and JohnBeales joined the channel
#
aaronpk
gives Loqi a quotation mark
#
Loqi
gives back the quotation mark
nitot, KartikPrabhu and JohnBeales joined the channel
#
aaronpk
are there different rules for parsing the contents of an h2 tag vs a div?
#
aaronpk
<h2 class="p-name"><p>hello world</p></h2> results in an empty name property, but it works fine with <div class="p-name"><p>hello world</p></div>
#
KartikPrabhu
aaronpk: weird that should not be the case IIRC
#
aaronpk
might be a bug in the php parser
#
aaronpk
works fine in the node one
#
KartikPrabhu
no same in mf2
#
KartikPrabhu
i don't think <p> is technically allowed inside <h2>
#
aaronpk
python one is okay too
#
KartikPrabhu
block element and all that. So the internal HTML parser in mf2 or php-mf2 might be causing that
#
KartikPrabhu
ok that is strange. my mf2 hosted one is not doing that
#
aaronpk
even the java one accepts it
#
aaronpk
okay yeah only the PHP one has this problem
#
KartikPrabhu
ok so in mf2 it might depend on the internal HTML parser, because my version in not giving me a name if there is a <p> inside
#
kylewm
intersting it works with html5lib but not lxml
#
KartikPrabhu
i'm using lxml
#
kylewm
KartikPrabhu: I changed mf2.kylewm.com so you can specify the backing parser
#
kylewm
hopefully will help with this in the future!
#
KartikPrabhu
default html5?
#
kylewm
it does seem like html5 does not allow <p> inside <h2> https://www.w3.org/TR/html5/dom.html#phrasing-content-1
#
KartikPrabhu
yeah block elements inside "inline" ones
#
aaronpk
I feel like if browsers are gonna render it just fine, then the parser should accept it too
#
KartikPrabhu
surprised that FF renders that even though on other elements it does some random stuff
#
kylewm
just weird bc I'd expect html5lib to blank it and lxml to be agnostic
#
KartikPrabhu
can't put a <ol> inside <p> to render in FF for example
#
KartikPrabhu
FF closes the <p> tag and puts the <ol> outside
#
KartikPrabhu
kylewm: that is what I would have expected too
gRegorLove, nitot and AngeloGladding joined the channel
JohnBeales, Loqi, gRegorLove and tantek joined the channel