Open Gargron opened 6 years ago
I was able to reproduce this issue with a random post from your account, and it looks to be caused by the microformats spec having changed the implied u-url rules. Since u-photo exists, it no longer implies a u-url. I realize now that should have been a version bump as that is actually a breaking change.
Example html to reproduce.
` <div class="h-entry"> <div class="h-cite p-comment"> <a class="statusdisplay-name p-author h-card" rel="noopener" href="https://site.example/@AwesomeUser"> <img width="48" height="48" alt="" class="u-photo accountavatar" src="https://site.example/user-photo.png" /> <strong class="display-name__html p-name emojify">AwesomeUser</strong> </a> </div> </div>
`
Not sure if we should roll back the version at this point @jgarber623 thoughts?
Going forward, I would recommend specifying the u-url as no new parser will get this url value. If you wrap move the classes out of the A tag to a containing tag it will work.
<div class="h-entry"> <div class="h-cite p-comment"> <div class="p-author h-card"> <a class="statusdisplay-name u-url" rel="noopener" href="https://site.example/@AwesomeUser"> <img width="48" height="48" alt="" class="u-photo accountavatar" src="https://site.example/user-photo.png" /> <strong class="display-name__html p-name emojify">AwesomeUser</strong> </a> </div> </div> </div>`
when accessing
mf2.entry.comment.author.url
in 4.0.9. This is a breaking change from 4.0.7 where it worked fine.