Hey there, for what it’s worth I tried the same URL you shared, and the paginated galleries all work responsively on my device. There could be nuance best answered by the developers of the particular block, though, which may possibly be this forum, based on a search. Hope that helps.
Thanks for the suggestion. If you feel strongly enough about it, the most actionable thing you can do is open an issue in the main GitHub repository and explain why.
I personally disagree, however: by leaving that option on by default, it means your tables will be responsive and legible, no matter the content, through allowing a scrollbar to appear. The same table in your example would be illegible on mobile, if that option was not on.
I’m almost certain this is because the social button doesn’t have a link, just like an image placeholder block that doesn’t have an image. Try typing in your Facebook address for that particular button, then previewing again.
If you are building a pattern for others to fill in, you can add # as the link. It will link nowhere, but it will be visible on the frontend.
That is very curious indeed. I assume this is the same user you’re logged in with, that created those patterns? On my end, I see the same patterns listed at both of those URLs:
Absent any other ideas, I’m going to drop this issue as a link in the core WordPress chat, see if any developers might be able to take a look.
Hey, I took a look, and I cannot reproduce this myself, I see all my custom patterns on this URL /wp-admin/site-editor.php?p=%2Fpattern&postType=wp_block&categoryId=my-patterns.
But I did respond on the GH issue you referenced, to see if anyone can take a look at this thread.
Hello! It’s unclear if the following is actually related to your question, but I recently happened upon this PR meant to more dynamically load terms as opposed to load all of them at once, presumably to avoid situations like the one you’re describing. Can you take a look at that PR, as well as some of the linked issues, and see if it’s related?
Hey there, it looks like these have context for why they were introduced here, and that might also be the best place to ask for how they might be disabled, if possible.
