Grouped Footnotes

Thanks for the kind words, glad you like the updates!

1. Within the block there is an option to load it with javascript, typically to handle cases where content is e.g. ajax loaded/bigpipe loaded but can help handle edge case. I'd try the regular group first though as essentially it builds up the footnotes in the order they get rendered, so the top of the page should happen first. Check with cached/non-cached versions
2. yep no problem
3. yep there are some examples in the twig tweak docs here https://www.drupal.org/docs/contributed-modules/twig-tweak-2x/rendering-... →
4. yep, it doesn't care where the footnotes come from, essentially there is a service collecting them all from wherever they get rendered and dropping em into a bucket

You can also take a look at the 'references shown in pop-ups' noted on the module homepage. We use footnotes for giant publications ourselves and style that to be a minimal slide up from the bottom which our users seem to like compared to a citation jumping them down to the bottom of the page - can be a nice progressive enhancement (they still show at the bottom of the page too)

This is all good to hear. I reviewed the twig_tweak and the src for the footnotes block, the {{ drupal_block('footnotes_group', { group_via_js: true }) }} looks easy enough.

What I am not sure about is the cache part. Looking at the source for footnotes, I see on line 17 of the FootnotesGroupBlock.php file that we have the entity @ContextDefinition there. I am not sure how I would set that with the tweak. When I set that for the provided footnotes_block, is that saying that if I set it to "Node from URL" that if the node cache has been invalidated that the block should as well. So that it stays updated when the node changes?

I agree on the popups for the footnotes. I showed that to the main site editor and he was interested. We are talking this afternoon to go over this stuff so I will bring that up again. Thanks!

I think with 🐛 Block - #lazy_builder content is empty for admin user on refresh Needs review the cache should anyways be fine (but that's not in beta5 though, its merged on 4.x)

I think we can probably mark this as fixed right? Question sort of answered and if you have specific issues you can raise in the issue queue for the module later

Yep! Thanks for your support!

Automatically closed - issue fixed for 2 weeks with no activity.