Accordion buggy

Thanks for posting, I see the issue, I’ll have a bug fix out Monday morning 🙂

Ben

Hey,
Thanks for your follow up, I should have clarified the latest versions of Gutenberg have been changing the way focus works, and what you are seeing is that something (like a button) can’t be clicked until the block is selected. When you create an accordion the inner pane becomes the selected block. To create another accordion you have to reselect the parent accordion block (this is what is happening when you click on the button, the button isn’t being pressed instead you are selecting the parent block.

When you select a block it’s supposed to “come into view” and that is why it’s jumping to the top of the accordion, that parent block is selected so it’s bringing the toolbar into view.

Similarly, when you remove an item the focus leaves the parent accordion and selects the last inner pane. So again when you click – button it’s actually selecting the block, not clicking a button.

I don’t have control over focus to change this, And there is merit to the focus switching to the newly created block.

I don’t have control over the way Gutenberg is not allowing inner actions until the block is selected. That is written into core.

So at the moment to make this “bug” go way I would have to hide the add pane and remove pane buttons when the parent block is not the selected block. That feels like it could create more confusion.

So, for the time being, I’m trying to follow along with the Gutenberg development to see if they will allow for some overriding code to take effect in cases like this.

Otherwise, I’m going to have to get really creative with code.

When I meant I would have the fix out Monday I was talking about the inability to remove the block.

I hope that clarifies and explains if you have suggestions I would love to hear it!

Ben

Do you think this is something that would be fixed in the next 2 months? That’s when I would be training users on it.

Not something I can know for sure since it’s based in WordPress core. (you can see the change made from 5.3 to 5.4. I would hope so, but a “fix” might mean removing the buttons all together and placing them in the sidebar. In which case the training would be the same, the user is going to have to click on the accordion block first then click add block. The “fix” in that case would mean they won’t see where to add an pane if the accordion block is not selected.

I don’t believe a Click event like that would work because it’s being overridden by core. I suggest instead of that kind of hack you are better off hidding the buttons until the accordion is selected, which you could do with css.

.block-editor-block-list__block.has-selected-ui.is-selected > .wp-block-kadence-accordion > .kt-accordion-add-selecter {
    display:flex;
    
}
.block-editor-block-list__block > .wp-block-kadence-accordion > .kt-accordion-add-selecter {
    display:none;
    
}

You can remove the intial select by going into the kadence controls (top right) and clicking on the block defaults, then editing the accordion block defaults. Uncheck “Show Presets”

Ben