-
Notifications
You must be signed in to change notification settings - Fork 28
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 #35
Comments
Expected result:
|
What version of mf2py were you testing against? In the most recent (0.2.6) I get a slightly different result with html and value nested inside value. I'll revisit the spec.
|
{
"rels": {},
"items": [
{
"type": [
"h-entry"
],
"properties": {
"content": [
{
"type": [
"h-card"
],
"properties": {
"name": [
"Hello"
]
},
"value": {
"html": "<p>Hello</p>",
"value": "Hello"
}
}
],
"name": [
"Hello"
]
}
}
],
"rel-urls": {}
} |
I was using the live version of mf2py on Kartik's site - as documented in the wiki: http://microformats.org/wiki/microformats2#Python - I just now added KevinMarks's unmung textarea which he added after I filed this issue. |
@tantek updated my sites' mf2py. Now reproduces what @kylewm and @kevinmarks get. This value:value needs to be fixed somehow. |
@kartikprabhu, @tantek updated the spec to clarify the bit that I misunderstood. i.e., that we should fold "value" and "html" into the existing object instead of nesting a new object http://microformats.org/wiki/index.php?title=microformats2-parsing&diff=64955&oldid=64926&rcid=101331 |
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: