Detect iframed editor before enabling Zoom Out feature

[getdave]

We need to detect that the Editor is iframed before we enable/expose the Zoom Out feature to users (even if it's still behind an experiment).

---

@getdave The easiest step is to enable custom fields, but that might be an issue we already had when the zoom out mode toggle was in a dropdown.

54a730c1ed6c065b2b16ee7fa02421cf.mp4

Originally posted by @t-hamano in #65183 (comment)

[getdave]

@t-hamano if you know how to detect whether the editor is iframed please do let me know otherwise we'll look into it.

[t-hamano]

I haven't explored this in depth yet, but what about forcing an iframe in zoomed-out mode, just like the mobile and tablet views do?

Perhaps it would be a good idea to add a condition __unstableGetEditorMode() === 'zoom-out' to either:

gutenberg/packages/editor/src/components/visual-editor/index.js

Lines 359 to 360 in 7f5e6b2

	const shouldIframe =
	! disableIframe || [ 'Tablet', 'Mobile' ].includes( deviceType );

gutenberg/packages/edit-post/src/components/layout/index.js

Line 347 in 7f5e6b2

disableIframe={ ! shouldIframe }

[t-hamano]

Update: #64351 has been merged, so the logic that determines whether the editor should run as an iframe has been updated. This means that the presence of custom fields/meta boxes is no longer tied to whether the editor is iframed or not.

One way to reproduce this issue is to have the Classic theme and the Jetpack plugin enabled. The Jetpack plugin has custom blocks that are not version 3, which is what prevents the editor from running as an iframe.

[draganescu]

I wonder if we should just disable the experience if there is no iframe?

[getdave]

I wonder if we should just disable the experience if there is no iframe?

Yes. That's the purpose of the Issue so I say 👍