- 🇩🇪Germany a.dmitriiev
The fix helped me, thanks. And it actually makes sense to have the id of the parent entity in the id attribute.
When you display the same type of entity on the same page multiple times with comments enabled (via Views), the wrapper ID stop being unique. Since this is passed through Html::getUniqueId this is not a problem on the first page load, but becomes an issue when one entity has a change in its comments and needs to be rerendered. Again this work fine for the normal AJAX reload, but when reloading the page only the changed entity will be rerendered but outside the context of the full page, so Html::getUniqueId will not do anything and the ID will not be unique, and worse the data-wrapper-html-id will point to the wrong entity, so any updates done will be shown on the wrong entity.
Make the wrapper ID more specific and don't depend on Html::getUniqueId by adding the ID of the commented entity to the ID.
Patch and review
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
The fix helped me, thanks. And it actually makes sense to have the id of the parent entity in the id attribute.