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

all bridgy posts should have explicit p-name inside their h-entry #48

Closed
tantek opened this issue Jan 29, 2014 · 0 comments
Closed

all bridgy posts should have explicit p-name inside their h-entry #48

tantek opened this issue Jan 29, 2014 · 0 comments
Assignees

Comments

@tantek
Copy link
Contributor

tantek commented Jan 29, 2014

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.

@ghost ghost assigned snarfed Jan 29, 2014
snarfed added a commit to snarfed/granary that referenced this issue Feb 2, 2014
other types (comment, like, repost) coming up next
snarfed added a commit to snarfed/granary that referenced this issue Feb 3, 2014
snarfed added a commit to snarfed/granary that referenced this issue Feb 3, 2014
snarfed added a commit to snarfed/granary that referenced this issue Feb 3, 2014
snarfed added a commit to snarfed/granary that referenced this issue Feb 3, 2014
@snarfed snarfed closed this as completed Feb 3, 2014
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

2 participants