The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.Problem/Motivation
Based on #343535: Enable bookmarking of AJAX views and https://www.drupal.org/node/3552223, it appears that starting with Drupal 11.3.x, the AJAX Views bookmarking functionality in the core/views module is enabled by default and cannot be disabled.
There are scenarios where disabling this functionality would be desirable. For example, a page may contain multiple View blocks with AJAX enabled and exposed filters. Because bookmarking is always enabled, each interaction can add additional query parameters to the URL. This can result in excessively long and cluttered URLs, which may be undesirable in some cases. In other situations, the bookmarking functionality may simply not be needed, and simpler URLs would be preferred.
In addition, the current bookmarking implementation has been reported to cause issues, as noted in https://www.drupal.org/project/drupal/issues/343535#comment-16579695.
Steps to reproduce
is currently no setting or configuration option to disable this behavior.
Proposed resolution
Allow the AJAX Views bookmarking functionality to be enabled or disabled through the View's configuration settings.
Here are some screenshots of the proposed solution from MR #16252:
The new disable AJAX option appears when AJAX is used in the view.
The option opens a dialog to disable AJAX URL rewriting.
Remaining tasks
Issue fork drupal-3604351
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
changes
Comments
Comment #2
takkuyu commentedComment #3
takkuyu commentedPatch file #1 has been created which removed the new SetBrowserUrl to disable the view ajax bookmarking (just a temporary patch to force it disabled)
Comment #5
takkuyu commentedComment #6
cilefen commentedComment #7
quietone commentedHi, Issues for Drupal core should be targeted to the 'main' branch, our primary development branch. Changes are made on the main branch first, and are then back ported as needed according to the Core change policies. The version the problem was discovered on should be stated in the issue summary Problem/Motivation section. Thanks.
Comment #12
marcoliverI added an MR with a proposed solution. As suggested in the issue description, it adds another checkbox allowing you to disable the AJAX bookmarking feature. If the value is true, views AJAX responses will skip the "add to browser URL" step.
I also added another test to ExposedFilterAjaxTest.
Probably not the final word on this, but it might be a start.
Comment #13
needs-review-queue-bot commentedThe Needs Review Queue Bot tested this issue. It fails the Drupal core commit checks. Therefore, this issue status is now "Needs work".
This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.
Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.
Comment #14
marcoliverMoving back to Needs review.
The bot flagged an unused use statement in the older MR. Pushed a change there to get the bot off my case.
Comment #15
marcoliverComment #16
smustgrave commentedAppears to have 2 MRs can one be closed or hidden please.
Also sounds like something that may need test coverage.
Can screenshots of the new configuration be added to the summary too.
Comment #19
marcoliverComment #20
marcoliverComment #21
marcoliverNo problem!
The old MR is hidden now.
Currently there is one new test, basically the reverse situation of the AJAX form filter test introduced in the previous issue. If more tests are needed, I'm certainly open to suggestions!
Finally, added some screenshots of where the new option would pop up using the MR. Updated issue summary accordingly.
Comment #22
marcoliverComment #23
marcoliverComment #24
smustgrave commentedThanks for keeping it going, left a comment on the MR.
Comment #25
marcoliverI updated the MR. It now contains an upgrade path via ViewsConfigUpdater, kernel tests for the updated updater, and a functional update test.
Comment #26
needs-review-queue-bot commentedThe Needs Review Queue Bot tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".
This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.
Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.
Comment #27
marcoliverRebased, patch should apply again.