kylewm_KartikPrabhu: tommorris: I'm confused about the HTML whitespace thing. if i knew how to use git blame, i could maybe figure out where it was introduced...
tantekedited /microformats2-parsing-issues (+707) "adding two issues to stop "crossing the streams" interactions between classic/uf2 roots/properties. AKA don't cross the streams." (view diff)
KevinMarks_"name": [ "Testing Brid.gy", "Testing Brid.gy", "Disruption and IIW Fall 2014", "Testing Brid.gy" ], "category": [ "Uncategorized" ], "content": [ { "html": "
\n \t\t\t<div class=\"e-content\"><p>How do I get things to show up from here to twitter and facebook and also for twitter and facebook to show up here?<\/p>\n<\/div> \t\t\t",
kylewm_GWG: the idea is basically, 1) if a root element has a mf2 class on it, it will be parsed without backward compatibility; and 2) if a root element has a mf1 class without an mf2 class, mf2 properties will be ignored
KevinMarks_GWG: note that google only currently parses mf1, and is using it for page-type categorisation; it will only show a single type (though may show eg multiple reviews or events
tantekedited /microformats2-parsing-issues (+2064) "uf2 children inside a classic microformats root class name, any h- root class name overrides and stops backcompat root" (view diff)
tantekedited /microformats2-parsing-brainstorming (+497) "/* Add meta http-equiv to microformats2 parsing model */ http - reasonable as optional pass, no need for metas until someone provides use-cases" (view diff)
tommorristantek: yes, the template tag needs to be ignored. mf2py already does this and I believe php-mf2 does too. someone reported it on IRC a while back (Hixie perhaps?)