If you use the list-links-draggable Macro it defaults to current tiddler and the “list” field, however if you name a different field eg field=fieldlist the current tiddler is not defaulted, and you have to pass it as a parameter, to do this you must use the macrocall form;
Perhaps there is a use I don’t know but with its use with other fields one would think there is no need to fail silently, just work with the current tiddler.
I have re-written the macro defined in $:/core/macros/list and add it here so you can see the changes to the shadow with preview “differences from shdow”.
I am yet to exhaustively test it, but I can’t see how it would break anything.
If this passes “muster” perhaps someone can raise a change, or at least tell me which GitHub repository I would need to fork to submit a change to the core. Pending its review?
I have seen, there is an issue at GH from 2022. While modifying / updating essential macros, on user request, can back-fire badly, in this case it should be safe and backwards compatible.
Since the existing behaviour does not do anything at all, it should be safe if it starts working after a change.
So it is expected, that everyone, that sees this thread and is interested to test the changes, that you really test it with one of your wikis. After making a backup – And watch for side effects.
Disclaimer: It is not guaranteed, that the PR will be merged.