I’m just saying that the builder element has unintended adverse affects on the functionality of the plugin, which it was specifically created to make it easier to add to the page. It just seems that the builder element is failing in its purpose. If a full time wordpress developer uses a builder element, then that developer has to go the theme’s support because it breaks something, then they exchange messages for five days trying to fix the problem, I am incapable of calling that easier.
Furthermore I see no reason that the builder element should have that deficiency, as the raw content works just fine. Basically why can’t the grid builder element just be a clone of the raw content element with a grid selector?
Also activating the load grid library globally feature is kind of brute forcing the problem. I get why the plugin developers added the feature, but it isn’t optimal. You wouldn’t suggest loading images, styles, or scripts that don’t appear on a page. But that is what this is doing. It slows down the site.
Using the raw content element OR activating load grid library globally will fix the problem, but its a problem that needn’t exist in the first place.