-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
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
adding h-* to an e-* property loses the "html:" key #64
Comments
Expected result:
|
Working on adding this now, where exactly is this made explicit in the parsing spec though? Reading through http://microformats.org/wiki/microformats2-parsing I cannot see where this is specified, unless it was missed out from "else if it's an e-* property element, re-use its { } structure with existing value: inside". Should that line read "else if it's an e-* property element, re-use its { } structure with existing value: and html: inside" I also find the “re-use it’s {} structure” language here a little problematic. Reading the spec it appears to suggest that parsing |
@tantek out of interest, can you remember if there was a real world example which prompted this? I’d be interested to see if if so. |
Compare how it parses:
to how it parses:
Note that in the second example the "html:" key inside content is lost for no reason.
The text was updated successfully, but these errors were encountered: