#Loqi[sknebel] We just encountered this difference in handling between `mf2py` and `php-mf2` while trying to help debug Bridgy on a WordPress site with the following structure:
```html
<body class="h-entry">
<div id="page" class="hfeed site wrap">
<h1 cla...
#gRegorLoveThe spec says "parse child elements (document order) by..." but php-mf2 is using xpath to pull out only the relevant elements, by mf2 prefix
#gRegorLoveSo currently mf2 finds the mf2 root, runs an xpath for mf2 properties...
#gRegorLoveBut to follow the spec precisely, and get the expected result, it should process the first child node, the <div class="hfeed"> and recurse
#gRegorLoveI'll try bumping up 'check for child mf' in the process before property parsing and see how it goes.
[kevinmarks] joined the channel
#gRegorLoveJust for parsing convenience, it does make me wonder if mf1 roots inside mf2 should be ignored, haha
#Loqi[tommorris] Thanks for reporting this @Zegnat. I currently don't have a lot of time to work on mf2py, so I can't promise to implement it soon, but I'll try and find time to implement this change at some point.
[kevinmarks], KartikPrabhu and davidmead joined the channel