We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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.
geo
p-geo h-geo
p-name
h-geo
Simplified HTML:
<div class="vcard"> <div class="fn">John Doe</div> <div>Location: <abbr class="geo" title="30.267991;-97.739568">Brighton</abbr></div> </div>
parsed:
"items": [ { "type": [ "h-card" ], "properties": { "name": [ "John Doe" ], "geo": [ { "type": [ "h-geo" ], "properties": { "name": [ "30.267991;-97.739568" ] }, "value": "30.267991;-97.739568" } ] } } ]
expected:
"items": [ { "type": [ "h-card" ], "properties": { "name": [ "John Doe" ], "geo": [ { "type": [ "h-geo" ], "properties": {}, "value": "30.267991;-97.739568" } ] } } ]
I think this switch needs a case for geo.
The text was updated successfully, but these errors were encountered:
Add failing test and fix for microformats#195
e84b4e9
Successfully merging a pull request may close this issue.
With this test, when the
geo
property is backcompat parsed asp-geo h-geo
, the parser is incorrectly adding an impliedp-name
for theh-geo
.Simplified HTML:
parsed:
expected:
I think this switch needs a case for
geo
.The text was updated successfully, but these errors were encountered: