The feed view has an amazing potential to facilitate what comes close to a ‘blocks’ entity, where the main entity can show related (e.g. child) entities as content blocks.
This is a simple way to mimick ‘transclusion’ of related entities, albeit limited to one rich text field.
This would be an even a more robust feature than a potentential manual transclusion of individual entities in a rich text field, which would likely be not as flexible.
One UX limitation however is that there is no way to remove the scrollbar from the Feed view in order to display the feed inside an entity as one coherent page.
I’m still looking to work around this.
Issue: The feed container, being likely the CSS class selector .feed_view, does not grow to fit its content.
Goal: Make the container auto-resize based on content height (all feed items).
Cause: Probably uses a virtualized list (e.g., react-virtuoso) renders only visible items, so height: auto makes the container collapse.
I would like to know:
- Feedback from the fibery team if this is indeed the case
- How to disable virtualization
- Any other suggestions to achieve auto height.
I figured out that this actually works, showing all feed itemst without scrollbar:
.feed_view {
height: fit-content !important;
}
[data-viewport-type="element"] {
position: relative !important;
}
This:
- Turns the Virtuoso wrapper into a regular scrollable or auto-sized container.
- Removes the virtualization layer behaviorally and visually.
- Makes the component behave just like a regular mapped list.
I’m now looking into making it use Virtuoso only if items.length > 100 so it would still show a scrollbar but only with a configurable amount of feed items.
I understand that the decision that was made to use Virtuoso relates to the potential that a feedview field is part of an entity view that may have other fields under it, which would be completely at the bottom and hard to scroll down to, if its a long feeds list. That decision is understandable but limits its use, as in my case that I need to show all items without scrollbar.
I think that in order to accomodate both use cases, it would be good to have a setting in the feed view that allows either full length or specific height scroll container.