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
Short answer: yes. We are monitoring it for core. And if there are relevant contrib updates we contact the contrib maintainer. Some of the updates in that feed actually originate...
Tag1 D7ES
I'm really hoping to make this simple change on new content types: https://github.com/backdrop/backdrop-issues/issues/7080 Let's disable the "Display author and date information" by...
February 26th, 2026 - Weekly Meetings
For our DEV meeting: an older bug needs (and could have) a fix. Issue #5729 - Views: Search Filter: On Empty Input "Show None" option Shows All There are 2 pull requests, but one...
February 26th, 2026 - Weekly Meetings