Closed (fixed)
Project:
Drupal core
Version:
11.x-dev
Component:
ajax system
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
26 Jul 2025 at 09:57 UTC
Updated:
25 Mar 2026 at 21:50 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
finnsky commentedComment #5
finnsky commentedComment #6
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 #7
finnsky commentedComment #8
smustgrave commentedDrupal\FunctionalJavascriptTests\Ajax\DialogTest seems to be failing which seems related.
Comment #9
finnsky commentedI would probably have approach review before.
Comment #10
finnsky commentedComment #11
finnsky commentedAll works same as with jquery UI
https://github.com/jquery/jquery-ui/blob/7571b739fbe227a9f47c1bbbd1d9f18...
but without :)
please review.
Comment #12
finnsky commentedComment #13
smustgrave commentedFull disclosure wasn't 100% how to best test this one. So I went with the view approach
Applied the MR.
Edited the generic content view
opened dialogs
Resized my screen
Closed dialogs
Saved them
Whatever I could think of
And it still seems to be working as before. So going to take a swing and mark it.
Comment #14
nod_haha yeah views is a good way to know if we broke the JS usually.
We already take over jquery ui _focusTabbable to make it use tabbable library: https://git.drupalcode.org/project/drupal/-/blob/11.x/core/misc/dialog/d... how is this MR different?
Comment #15
finnsky commentedWell, I'd say that in that file you're still working with a jQuery instance.
Here, pure vanilla does the same thing. And when the time comes, we can simply replace the classes and get a native dialog.
Comment #16
smustgrave commented@nod_ thoughts on that?
Comment #17
smustgrave commentedGoing to go on a limb and say feedback was addressed @nod_ still would like your thoughts though.
Comment #18
finnsky commentedRebased.
Comment #20
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 #21
finnsky commentedComment #22
smustgrave commentedGoing to restore status..
Comment #25
longwaveI read through dialog.jquery-ui.js and https://github.com/jquery/jquery-ui/blob/839ff8fae666e44d2633db81b1ae548... and this change matches the existing behaviour and makes sense to me.
As a followup should we deprecate the
_focusTabbable()override somehow? Or is the idea that all of dialog.jquery-ui.js can go away once these conversions are done?Committed and pushed 62adbdfd4cb to main and 3f9882e3de9 to 11.x. Thanks!
Comment #28
finnsky commented@longwave
We can add deprecations message right here
https://git.drupalcode.org/project/drupal/-/blob/main/core/misc/dialog/d...
Comment #29
claudiu.cristeaThis MR/change triggers random failures, see https://git.drupalcode.org/issue/drupal-3566890/-/jobs/8878676