Bard Field '+' Icon jumps when trying to select text underneath it

[JorisOrangeStudio]

Bug description

When using a Bard field and selecting texts the UI bugs once you reach the '+' icon, see attached video. This makes it almost impossible to select the first character of a line with your cursor and can be quite frustrating if you are copying/pasting a lot of content.

Possible solution is maybe to move the plus icon to the next/previous line instead of the active one?
Or hide the plus icon when text is being selected (if that is possible)?

record.mov

How to reproduce

Use a Bard field with the + icon set to always visible and select a text (see video)

Logs

Environment

Environment
Application Name: xxx
Laravel Version: 10.48.28
PHP Version: 8.3.16
Composer Version: 2.8.4
Environment: local
Debug Mode: ENABLED
URL: localhost/
Maintenance Mode: OFF

Cache
Config: NOT CACHED
Events: NOT CACHED
Routes: NOT CACHED
Views: CACHED

Drivers
Cache: file
Database: mysql
Logs: stack / single
Mail: mailgun
Queue: sync
Session: file

Statamic
Addons: 6
Sites: 4 (Dutch, English, German, French)
Stache Watcher: Enabled
Static Caching: Disabled
Version: 5.46.1 PRO

Statamic Addons
aerni/advanced-seo: 2.9.3
heidkaemper/statamic-toolbar: 1.3.0
jacksleight/statamic-bard-texstyle: 3.4.1
mattrothenberg/statamic-mapbox-address: 0.9.0
mitydigital/statamic-logger: 2.4.0
statamic/collaboration: 1.0.0

Installation

Fresh statamic/statamic site via CLI

Additional details

No response

[duncanmcclean]

Which browser are you using?

[JorisOrangeStudio]

[jasonvarga]

You could disable the always_show_set_button setting on the bard field.

[JorisOrangeStudio]

You could disable the always_show_set_button setting on the bard field.

Yess I know, but we prefer to have it enabled for our CP users, as it improves the UX. Had some questions before on how to add sets when this was turned off.

[jasonvarga]

Of course, just giving you a temporary workaround.

[liucf]

@JorisOrangeStudio I tested this using the latest version of Chrome and couldn't reproduce the issue — everything seems to be working as expected on my end. Could you please confirm if you're still experiencing the problem?

Chrome is up to date
Version 135.0.7049.85 (Official Build) (arm64)

[JorisOrangeStudio]

Hi @liucf, I just tested again on 135.0.7049.84 (Official Build) (arm64) and the issue still persists like the first screen recording