Open rubzie opened 8 months ago
I think this was intentionally removed in v4 beta? @jackmcdade
I was looking into this as well. I found that it was explicitly decided in this PR to only apply to top level fields, but I'm not sure why.
Ah thanks for the reference @Diewy! Can you enlighten us maybe, @jackmcdade? On why, and also maybe on how we could change it ourselves (feels a bit much to make an addon for it though :o)
Because they caused completely unusable experiences when you had a grid with multiple bard fields on mobile and other situations. They'd stack up so deep there'd be no textarea left.
Maybe it's possible to allow it in a Replicator, but not inside Bard?
By what logic would make one okay and not the other since they share basically everything?
Replicator doesn't have a fixed toolbar. Make it stop being fixed as soon as the first Bard field is nested inside a Bard field.
We'd like our bard field toolbars to also be sticky when they're inside replicator fields. Currently they are not. This is annoying when adding more content than a screen full, which happens often on some fields. The CSS below specifically excludes bard field toolbars in replicator fields, is there a reason for this? If not, our agency suggested changing this CSS to solve the problem:
Example of the user experience of this currently:![20231013-eUETKOOA-Advertenties ‹ Flexible Pages ‹ Collections ‹ Statamic](https://github.com/statamic/ideas/assets/213834/65aebcba-7bb0-418d-a5f4-8fdc53ceb6bd)