Jahirul Islam

Hi @bigvibes ,

That’s not the intended behaviour. With the filter active, an unsynced pattern should act like a normal group of blocks, so the separator should be clickable directly.

What you’re describing (text editable, separator locked) is exactly how content-only mode works: text and images stay editable, design blocks like separators and spacers are locked. So content-only is still active for that pattern. Two usual reasons:

1. The snippet isn’t loading in the editor

Open a post, press F12 → Console, paste this and press Enter:

wp.data.select( 'core/block-editor' ).getSettings().disableContentOnlyForUnsyncedPatterns

If it returns undefined, the code isn’t running in wp-admin. Common causes: the snippet plugin is set to “Frontend only” (it needs “Run everywhere”), the snippet isn’t activated, or the mu-plugin file is inside a subfolder (WordPress only loads files placed directly in wp-content/mu-plugins/). Reload the editor after fixing it.

2. It returns true, but the pattern is still locked

Then the lock comes from the pattern itself, which this setting doesn’t override:

• The pattern’s wrapper block has "templateLock":"contentOnly" saved in its markup (common in theme and plugin patterns). Open ⋮ → Code editor and look at the first wp:group line. Remove "templateLock":"contentOnly" along with the comma next to it, then switch back to the Visual editor. To stop it coming back on new inserts, remove it from the original pattern too.
• Or it’s a synced pattern (toolbar shows “Edit original”) or it sits inside a template part like the header/footer. Those stay locked by design; Detach is the way for synced patterns.

If you share what the console check returns and where the pattern comes from (your own saved pattern, the theme, or a plugin), I can narrow it down further.

Hi @genepine,

I checked your sample page and found the cause. The Breadcrumbs block draws the separator with this CSS:

.wp-block-breadcrumbs li:not(:last-child)::after { content: var(--separator, "/") / ""; }

The / "" part tells screen readers to skip the separator. Safari only understands it from version 17.4, and iOS 16.7 has an older Safari engine, so the whole rule is ignored. Every browser on an iPhone uses Safari’s engine, which is why Chrome and Firefox there fail too, while iOS 26 and Android work.

iOS 16 is outside WordPress’s supported browsers, but a small CSS fallback fixes it. Add this under Appearance → Editor → Styles → ⋮ → Additional CSS:

@supports not (content: "a" / "") {
	:root .wp-block-breadcrumbs li:not(:last-child)::after {
		content: var(--separator, "/");
	}
}

It only kicks in on browsers that don’t support that syntax, so newer browsers keep the default behaviour. The :root makes sure it overrides the core rule.