Support

Account

Home Forums General Issues Possible iframe editor scrollbar/focus bug with ACF Blocks v3

Unread

Possible iframe editor scrollbar/focus bug with ACF Blocks v3

  • **Possible iframe editor scrollbar/focus bug with ACF Blocks v3**

    We are encountering what appears to be an iframe editor compatibility issue involving ACF Blocks v3 and editable ACF fields.

    ### Environment

    – WordPress 6.9.4
    – ACF Pro 6.8.0.1
    – Custom ACF Blocks using:
    apiVersion: 3
    acf.blockVersion: 3
    – Occurs across:
    – Chrome
    – Safari
    – Firefox
    – Reproduced on:
    – macOS
    – Windows

    ### Issue

    When the block editor is running in iframe mode, clicking the editor scrollbar causes the page to jump downward unexpectedly.

    This appears to happen because Gutenberg creates/focuses the trailing default paragraph block (“Type / to choose a block”) at the bottom of the editor.

    The issue:
    – occurs both when clicking the scrollbar thumb and scrollbar track
    – is reasonably reproducible (happens most of the time)
    – only seems to occur after interacting with an ACF block field
    – occurs even with a simple plain text ACF field
    – does not require WYSIWYG fields
    – does not appear related to supports.mode

    ### Important observations

    The issue only occurs:
    – in iframe-enabled editor mode
    – when the page contains an ACF block with editable fields

    The issue does NOT occur:
    – in non-iframe editor mode
    – on pages without editable ACF block fields

    ### Additional notes

    We tested removing:

    `json
    “mode”: false
    `

    from block supports and the issue still occurred.

    We also confirmed the issue with a minimal field setup using only a basic text field.

    Example block configuration:

    `json
    {
    “apiVersion”: 3,
    “acf”: {
    “blockVersion”: 3,
    “renderTemplate”: “tiles.php”
    }
    }
    `

    At this stage it appears to be related to focus/selection handling between:
    – the iframe editor
    – Gutenberg insertion point logic
    – ACF editable block fields

    rather than a specific field type or block configuration issue.

    Has anyone else encountered this, or is this a known iframe compatibility issue?

Viewing 1 post (of 1 total)

You must be logged in to reply to this topic.