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
It looks like the h-card validator currently uses the first h-card it finds on the page. I suspect we instead want it to use the representative h-card algorithm, or if that's too much, at least the top-level h-card. The current result for eg https://indiewebify.me/validate-h-card/?url=https%3A%2F%2Fwebrocker.de shows an h-card with a u-photo from an h-entry, which is misleading, since the representative h-card doesn't have a u-photo.
I think something might not have gone right with the deploy after #101 merged -- maybe the dependencies didn't update? I'm not really familiar with how the deploy process works.
It looks like the h-card validator currently uses the first h-card it finds on the page. I suspect we instead want it to use the representative h-card algorithm, or if that's too much, at least the top-level h-card. The current result for eg https://indiewebify.me/validate-h-card/?url=https%3A%2F%2Fwebrocker.de shows an h-card with a u-photo from an h-entry, which is misleading, since the representative h-card doesn't have a u-photo.
cc @barnabywalters @gRegorLove
The text was updated successfully, but these errors were encountered: