(based on microformats/php-mf2#195)
With this test, when the geo property is backcompat parsed as p-geo h-geo, the parser is incorrectly adding an implied p-name for the h-geo. The u-url also shows the object is parsed as mf2, not mf1.
Simplified HTML:
<div class="vcard">
<div class="fn">John Doe</div>
<div>Location: <abbr class="geo" title="30.267991;-97.739568"><a class="u-url" href="https://brighton.co.uk">Brighton</a></abbr></div>
</div>
parsed:
{
"type": [
"h-card"
],
"properties": {
"name": [
"John Doe"
],
"geo": [
{
"type": [
"h-geo"
],
"properties": {
"url": [
"https://brighton.co.uk"
],
"name": [
"30.267991;-97.739568"
]
},
"value": "30.267991;-97.739568"
}
]
}
(based on microformats/php-mf2#195)
With this test, when the
geoproperty is backcompat parsed asp-geo h-geo, the parser is incorrectly adding an impliedp-namefor theh-geo. Theu-urlalso shows the object is parsed as mf2, not mf1.Simplified HTML:
parsed:
{ "type": [ "h-card" ], "properties": { "name": [ "John Doe" ], "geo": [ { "type": [ "h-geo" ], "properties": { "url": [ "https://brighton.co.uk" ], "name": [ "30.267991;-97.739568" ] }, "value": "30.267991;-97.739568" } ] }