Wayfinder conflict with new GenerateBlocks 1.7

@themolitor, I’ve heard back from the GenerateBlocks team. Here’s their reply, which might give you insight into what has changed in GenerateBlocks and why Wayfinder is now conflicting with it. Their example is with their Button block, but the same is true for their Container block.

The old GenerateBlocks Button block used to always be inside the Buttons wrapper block, so they had this selector:
.gb-button-wrapper .gb-button {
/* CSS */
}

Now that the Button block can be by itself, it has a simpler selector:
.gb-button {
/* CSS */
}

Unfortunately, this makes it less specific and can leave it prone to being overwritten by more specific selectors. This is what’s happening with the Wayfinder plugin – they’re using a very specific selector. It may be worth reporting to them to see if they can lower the specificity.

People who use GenerateBlocks usually use it as their primary block package, so it’s used on every page and post. Therefore, if Wayfinder was incompatible with GenerateBlocks, there would be no reason to install it. So really, I don’t think a disable feature is needed. I’ve been testing the Editor Block Outline plugin by Kalimah Apps, and while it is compatible with the new GenerateBlocks, I don’t like it as much as Wayfinder.