You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently bridgy posts typically have an h-entry without any explicit p-name. Thus by the microformats2 implied p-name rules, the entirety of the h-entry's inner text becomes its p-name which results in unexpected / undesirable UI effects, e.g. see backfed mentions on this event post: http://aaronparecki.com/events/2014/01/29/1/homebrew-website-club
All bridgy posts with h-entry (which is all of them I think) should have an explicit p-name that makes sense for that post, that a receiver could use to display a brief text summary of the post.
The text was updated successfully, but these errors were encountered:
Currently bridgy posts typically have an h-entry without any explicit p-name. Thus by the microformats2 implied p-name rules, the entirety of the h-entry's inner text becomes its p-name which results in unexpected / undesirable UI effects, e.g. see backfed mentions on this event post: http://aaronparecki.com/events/2014/01/29/1/homebrew-website-club
All bridgy posts with h-entry (which is all of them I think) should have an explicit p-name that makes sense for that post, that a receiver could use to display a brief text summary of the post.
The text was updated successfully, but these errors were encountered: