Closed (fixed)
Project:
Display Builder
Version:
1.0.x-dev
Component:
UI/UX/Islands
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
8 Jun 2025 at 21:32 UTC
Updated:
12 Dec 2025 at 11:39 UTC
Jump to comment: Most recent
Comments
Comment #2
pdureau commentedComment #3
pdureau commentedComment #4
pdureau commentedInteresting things are happening in the #3526267: Remove core/drupal.ajax dependency from big_pipe/big_pipe MR: https://git.drupalcode.org/project/drupal/-/merge_requests/12295/diffs
Comment #5
mogtofu33 commentedComment #6
pdureau commentedComment #7
pdureau commentedSee also: https://www.drupal.org/node/3539472 (For Drupal 11.3)
Comment #8
mogtofu33 commentedWe are close and will probably need to switch to the HTMX in core, but then we will be compatible only with Drupal > 11.3, which is ok for me but some users will be disappointed. IMO to maintain compatibility before 11.3 makes no sense and is a waste of ressources.
As soon as we start this we will be only Drupal 11.x compatible. Unless 11.3 is out, but I think we don't want to wait for that long.
Comment #9
pdureau commentedComment #10
pdureau commentedComment #11
pdureau commentedOnce #3556198: Minimal requirement is now Drupal 11.3.x is merged, we can resume this task.
I guess we will meet the same issue as in #3544108: Support HTMX 1.5.0 and @ipumpkins may be right:
Because of both:
See: https://www.drupal.org/project/display_builder/issues/3544108#comment-16...
Comment #13
pdureau commentedI have just pushed one "naive" commit, as a starting point. The playwright jobs will not be useful until #3556198: Minimal requirement is now Drupal 11.3.x is merged anyway.
Comment #14
pdureau commentedComment #16
pdureau commentedcareful, i have rebased the MR.
It works OK for me.
Next steps:
Follow-up: #3536288: HTMX array rationalization
Comment #17
pdureau commentedHI Jean, we may need your help. It is hard to guess what is causing the playwright fail in
await element.click({ position: { x: 5, y: 10 } })Comment #18
mogtofu33 commentedThe test failing part is about adding a component and a token in this component slot.
It seems it works for other cases doing the same, so perhaps something else, checking.
Comment #19
mogtofu33 commentedHere is how to reproduce the problem (it do not occur on 1.0.x), fresh install theme display_builder_theme_test :
Refresh or edit config anything and it will work. So I guess we just miss the update when something is attached to root.
Comment #20
pdureau commentedIt is not related to root because dropping in a slot do the same and we can reproduce this with other sources .
source_idin the URL querynode_id) in the URL querySo it seems we have the exact opposite situation as before commit e438d783: instead of blocking the other view panel (BuilderPanel for LayersPanel and the other way around) the drop is blocking the same panel.
Because it is the same panel, it may be related to this mechanism from
DisplayBuilderEventsSubscriber::dispatchToIslands():If I comment it, it works OK.
Mikael, do you want to have a look?
Comment #21
just_like_good_vibesplease test again with that new add-on :)
Comment #22
pdureau commentedIt is OK for me (and all tests are green)
Comment #23
mogtofu33 commented