plone
"Numbered List" toolbar button moves out of view after first click
Describe the bug When I use the RichText widget, the formatting toolbar disappears a bit when clicking "Numbered List".
To Reproduce Steps to reproduce the behavior:
- Go to Edit mode
- Click inside the text input field in the sidebar and select some text.
- Click on "Numbered List".
- Try to click the rightmost option in the toolbar.
Expected behavior The Toolbar should stay fully visable and inside the screen.
Screenshots
Software (please complete the following information):
- OS: Ubuntu 24.04.3 LTS
- Browser: Chrome
- Volto Version [e.g. 18.23.0]
- Plone Version [e.g. 6.2.0]
- Plone REST API Version [e.g. 9.1.0]
Thanks for opening your first issue here! Your engagement is essential for open source projects, including Plone. :hugs:
If you haven't done so already, read Plone's Code of Conduct. Also please follow the issue template, as it helps both you and other community members contribute more effectively.
If your issue is a feature request, others may raise its prominence through feature voting.
Welcome to the Plone community! :tada:
![boring-cyborg[bot] avatar](https://avatars.githubusercontent.com/in/50386?v=4 "Published by a pub.dev verified publisher"){kind=small}
@TimoBroeskamp id like to work on this issue can you assign it to me the other individual has made no update since then so is it ok for me to work?
@BEAST6869 Before contributing, please read: https://6.docs.plone.org/contributing/index.html
@BEAST6869, no. Please read and follow First-time contributors, especially Things not to do, Contributing to Plone, and Contributing to Volto.
Hey @TimoBroeskamp @plone/volto-team,
I tried to reproduce the reported issue with the RichText toolbar. I am unable to see the rightmost buttons moving out of view. What I observe is a slight shift of the toolbar towards the right when clicking "Numbered List," but all buttons remain visible.
Could you please clarify exactly where you see the issue? If possible, sharing a screen recording or specifying the screen width / environment where this happens would be very helpful for reproducing the bug.
