Steps to reproduce the issue

Audit finding

In a small viewport, opening the editor's three-dot menu to display additional toolbars causes the editor to disappear when the page is scrolled.

The report describes the result as an empty space where the editor should be. It states that the editor reappears only after scrolling fairly close to the top of the page.

The report's recommendation is that the editor should not be hidden at any time.

User impact

People editing an article on a narrow viewport may lose access to the content they are editing after expanding the toolbar.

They may see only blank space and be unable to tell whether the editor has failed, whether they need to scroll, or whether their content is still present.

Keyboard users may lose their editing context if the editor area disappears while they are interacting with its controls. This can make article editing impractical at the tested viewport size.

The failure affects the core task of creating or editing article content, rather than a secondary preference or optional control.

Remediation plan

Keep the editor and its controls available and operable after reflow and scrolling

• Ensure that the editor remains visible and usable when the toolbar is expanded at a 320 CSS-pixel-wide viewport
• Prevent the editor from being replaced by empty space during vertical scrolling
• Ensure that expanded toolbar content does not create a layout state in which the editor is hidden or inaccessible
• Preserve the association between the editor, its toolbar, and the article content being edited
• Ensure that keyboard focus remains in a sensible location and that the focused control remains operable
• Avoid horizontal scrolling as the remedy
• Ensure that scrolling does not require returning to the top of the page to restore the editor
• Test both mouse or touch scrolling and keyboard-driven scrolling
• Verify that the editor remains available after opening and closing the three-dot menu
• Ensure that the fix applies to the shared editor container or relevant component behaviour rather than only one article

Preconditions

• Use Joomla 6.2 with the Atum administrator template
• Sign in with an account permitted to edit articles
• Use a test article containing enough content to require scrolling
• Use an editor configuration that provides the three-dot toolbar control
• Record the exact editor plugin or editor configuration if more than one is available
• Record the exact Joomla build, browser name and version, operating system, viewport dimensions, and browser zoom
• Start with a viewport of 320 by 256 CSS pixels at 100% browser zoom
• Record the active appearance and any template overrides or custom CSS
• Use a disposable test article so that editing actions do not affect production content

Steps to reproduce

1. Open the Joomla administrator interface at the site's base URL followed by /administrator/
2. Open Content → Articles
3. Open an existing test article for editing
   • Alternatively, navigate to /administrator/index.php?option=com_content&view=article&layout=edit&id=11 on a test installation containing that article
   • Record the article ID and editor configuration used
4. Set the browser window or responsive-emulation viewport to 320 by 256 CSS pixels
5. Confirm that the page is rendered at 100% browser zoom
6. Locate the WYSIWYG editor and confirm that its content is visible
7. Locate the three-dot menu used to reveal additional toolbar controls
8. Activate the three-dot menu
9. Confirm that the additional toolbar is displayed
10. Scroll the page vertically
11. Observe whether the editor remains visible
12. Record whether it is replaced by empty space
13. Continue scrolling and record whether the editor remains absent
14. Scroll back toward the top and record when, if at all, the editor reappears
15. Capture the expanded-toolbar state, the scrolled state showing the empty area, and the state in which the editor returns
16. Repeat using keyboard navigation where practical
17. If the editor does not reproduce the issue, record the editor configuration, viewport, and scrolling method used

Verification after remediation

1. At the same 320 by 256 CSS-pixel viewport, open the test article
2. Expand the toolbar using the three-dot menu
3. Scroll down and back up
4. Confirm that the editor remains visible and operable throughout
5. Move keyboard focus into the editor and through its toolbar controls
6. Confirm that focus remains visible and that controls remain operable
7. Close and reopen the three-dot menu
8. Repeat the scrolling checks
9. Confirm that no horizontal scrolling is required
10. Record the editor configuration and viewport used for the verification

Version

6.2

Expected result

At a 320 by 256 CSS-pixel viewport, the article editor remains visible and operable after its toolbar is expanded and the page is scrolled.

Users can continue editing without the editor being replaced by empty space or requiring them to scroll back to the top to restore it.

Actual result

At a small viewport, after opening the three-dot menu to show additional toolbars, scrolling the page causes the editor to disappear.

The editor area becomes empty space. According to the report, the editor reappears only after scrolling fairly close to the top of the page.

The current Joomla 6.2 build needs to be checked to establish whether the issue persists and under which editor configurations it occurs.

What device were you using? (eg, phone, laptop)

Desktop web

What web browser were you using? (eg, Chrome, Safari)

Chrome, Firefox, Edge, Safari

Assistive Technology?

N/A

Additional Comments

The browser entries above are carried forward from the original issue and do not represent a new verification of every browser against Joomla 6.2.

Development is the responsibility tag in the original report.

The report's screenshot and attached video document the audited configuration. The current build, editor plugin, and template configuration need to be checked before attributing the exact behaviour to Joomla 6.2.

The issue is distinct from colour-contrast findings. It concerns whether the editor remains visible and operable after reflow and scrolling.

MS2a is proposed for the shared editor container and responsive behaviour, with MS3b covering the documented backend edit-form integration.