🇺🇸United States @hooroomoo

hooroomoo → created an issue.

wim leers → credited hooroomoo → .

hooroomoo → made their first commit to this issue’s fork.

Noticed this when working on sections too.

hooroomoo → created an issue.

Yep #2 is correct, it was refetching itself after the DELETE call.

It looks like after the layer expands, it freezes when I try to drop the item in.

bnjmnm → credited hooroomoo → .

@omkar-pd Are you using chrome?

Looks like it works on Chrome after testing it, but I just tested it on Firefox (my default browser) and it looks like the preview canvas is receiving the drag event and not the layers menu so the preview is scrolling instead of the layers menu.

Marking stable blocker because it's a long and disruptive console warning

hooroomoo → created an issue. See original summary → .

A huge roadblock with replacing the div wrappers around the region with the HTML comments is that there is no way to initialize SortableJS (drag and drop functionality) for a region without a parent element aka if a twig template only prints out {{content}} or it has no root parent element.

This is because SortableJS requires a parent element to be passed in.

@jessebaker and I talked about this and he said that 📌 Investigate drag-and-drop solution that removes the need to drop items into the preview iFrame Active should unblock this so therefore marking this issue as postponed.

hooroomoo → made their first commit to this issue’s fork.

Left a suggestion

Tested manually and I also can't reproduce the issue anymore :D

@wimleers

So in my MR I am using the HTML comments to create a map of the region id to it's corresponding <div region region--{regionId}> from the markup returned from the backend.

But when in Olivero, neither <div region region--primary-menu/> nor <div region region--header/> exist in the markup returned by the backend. But it exists for the rest of the regions.

And in Claro, the markup does contain <div region region--header/>

Is this a known bug that the header and primary menu don't come with the

Another thing I noticed is the comment

is after

Paired with @balintbrews and we got a working solution :)) Setting a unique key to the component list onDragEnd instead of an individual list item works.

The above didn't work for me. I wasn't able to find a good solution.

1. Calling something like evt.clone.replaceWith(evt.item) would require changes to usePreviewSortable.ts where it changes the innerHTML to the rendered markup (updateData()) so it can render in the preview and want to avoid changes to that file if possible.

2. Tried #16 and similar things as the above to try to trigger a re-render of but I couldn't get it to work.

3. Confusing React by passing in a Math.random() like <ListItem key={Math.random()} .../> kinda works but is bad practice and also causes SortableJS errors 😛 lol

Updating title because this affects any item under the Components list, not just exposed code components.

I think what's happening is when an item is dragged out of the Components list, a clone from SortableJS replaces it in the list. But that clone doesn't have any of the React event handlers that the original item had which is why the component preview no longer works onMouseEnter.

So that's why it works when you close and re-open the Components list, since in that state, only the originals are there, no clones.

Will continue tomorrow.

hooroomoo → created an issue.

Nevermind! I am able to reproduce it. I was clicking to insert instead of dragging.

Hm i'm not able to reproduce this issue

hooroomoo → made their first commit to this issue’s fork.

wim leers → credited hooroomoo → .

balintbrews → credited hooroomoo → .

Adding credit for @jessebaker for pointing me to the manualRetch that might not be necessary anymore and removing it fixed the regression i was looking at

I may have found a regression so am looking into it. Clicking publish all changes shows the happy green smiley but then flashes back to show "Publish all changes" again

Yay!

(I removed sprint-candidate tag)

hooroomoo → made their first commit to this issue’s fork.

wim leers → credited hooroomoo → .

wim leers → credited hooroomoo → .

larowlan → credited hooroomoo → .

hooroomoo → made their first commit to this issue’s fork.

wim leers → credited hooroomoo → .

wim leers → credited hooroomoo → .

wim leers → credited hooroomoo → .

hooroomoo → made their first commit to this issue’s fork.

I think this could benefit from having a storybook story for the different kinds of but we can always add that later if we want. Think it's valuable to get this in right now so it's easier to test backend changes i.e. 🐛 Once previewed in XB an entity with no changes will still show up in "Review x changes" Active

Assigning back to Jesse for screenshot/cast

hooroomoo → made their first commit to this issue’s fork.

wim leers → credited hooroomoo → .

This is ready for initial round of feedback, please see MR description

e2e test are passing after merging with 0.x 👍

e2e tests failing, unit tests are also failing but the same files are failing on 0.x

Hoping merging w 0.x resolves the e2e

hooroomoo → made their first commit to this issue’s fork.

hooroomoo → made their first commit to this issue’s fork.

hooroomoo → made their first commit to this issue’s fork.