When a user disables tabledrag, a cookie is set, disabling tabledrag on every page on the site. For someone who was just playing with that link to see what it did (most common use case) this creates a less-than-ideal experience and bad impression of the software.

What we really need instead of a cookie is a setting. People who want tabledrag disabled permanently should use the setting. People who need to disable it temporarily will use the link.
Recent comments
Hi Kevin I am interested assisting you developing a theme by cloning feature from existing WordPress website. Please let me know your suitable time to discuss further...
Create a theme from existing website
I've updated the Zulip link in both places I found it. No need to post again, unless you have something new to say. We'll pull together feedback from all the sources.
Backdrop CMS Core Priorities
Should we post here again, what we posted over there? Or would that unnecessarily duplicate things? The link to a Zulip thread in this initial post leads to an internal one, but there's...
Backdrop CMS Core Priorities