Skip to content
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

Ambiguous property-microformat collapsing rules for p- properties #67

Open
JKingweb opened this issue Jul 17, 2023 · 0 comments
Open

Ambiguous property-microformat collapsing rules for p- properties #67

JKingweb opened this issue Jul 17, 2023 · 0 comments

Comments

@JKingweb
Copy link

JKingweb commented Jul 17, 2023

The general parsing rules state:

  • if that child element itself has a microformat ("h-*" or backcompat roots) and is a property element, add it into the array of values for that property as a { } structure, add to that { } structure:
    • value:
      • if it's a p-* property element, use the first p-name of the h-* child
      • else if it's an e-* property element, re-use its { } structure with existing value: inside.
      • else if it's a u-* property element and the h-* child has a u-url, use the first such u-url
      • else use the parsed property value per p-,u-,dt-* parsing respectively

The difference between handling of p- properties and u- properties (there is no "and the h-* child has a p-name" clause) implies that p-name should be used unconditionally even if the child has none, yet the "else" at the end does does apply to p- properties.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant