Channels tab: enable AJAX compatibility. #4938
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
4 tasks
ThoWagen
approved these changes
Dec 5, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Based on discussion in #4901, I thought it would be a good idea to investigate the feasibility of getting the Channels record tab out of "no AJAX" mode. Turns out it was simpler than I expected -- just required moving some translations into the global file instead of making them template-specific and enabling the channels.js Javascript file in a couple of extra places (one for record tabs, one for accordion/tab search result views).
I'll be interested to hear whether anyone has concerns about this. I can move the milestone to 11.1 if this is too significant a change for a patch release, but it's such a big improvement to accessibility that I'd rather not wait if it's safe.