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.
GitHub Issue #:
750
Recent comments
Out of curiosity: why are these tags only relevant for admins? Don't "regular" editors on that site also need them under circumstances? Yes, the editors play nicely, no problem to...
Specific tags to work in CKEditor 5
Worked like a charm! Exactly what I envisioned... now I can edit the ruby text right in the editor, sweet:) Thank you! For those who may have a similar issue, try TinyMCE, create a new "text...
Specific tags to work in CKEditor 5
Yes, you can use TinyMCE on some content and CKEditor5 in others. There is no problem having both enabled on a system.
Specific tags to work in CKEditor 5