Confluence Cloud search/input fields show selection toolbar during Japanese IME composition

[Naoto Isobe]

In Confluence Cloud, when entering Japanese text with an IME in a search/input field, pressing Space to
convert text causes Confluence's floating selection toolbar to appear.

The toolbar includes actions such as "Ask Rovo", "Define", and "Comment". This appears to treat IME
composition text selection as a normal page text selection.

This breaks Japanese input because Space is used for IME conversion, but Confluence reacts as if text was
selected on the page.

Environment:
- Product: Confluence Cloud
- Browser: Google Chrome on macOS
- Language/Input: Japanese IME
- Affected field: Confluence page/search input field

Steps to reproduce:
1. Open a Confluence Cloud page.
2. Focus a Confluence search/input field.
3. Type Japanese text using Japanese IME.
4. Press Space to convert the composing text.
5. Observe that the Confluence floating selection toolbar appears with actions like Ask Rovo / Define /
Comment.

Expected:
During IME composition, Confluence should not show the floating selection toolbar or treat composing text as
page text selection.

Actual:
The floating selection toolbar appears during IME conversion and interferes with Japanese input.

Impact:
This makes Japanese input unreliable in Confluence search/input fields.

Additional note:
This is not the search suggestion dropdown. It is the floating selection toolbar normally shown when
selecting text on a page.

The issue seems to be that Confluence treats the highlighted IME composition text inside the input field as a
normal page text selection.

I will also test with browser extensions disabled / in an incognito window to rule out extension
interference.

[Tomislav Tobijas]

Hey @Naoto Isobe ,

I know there's this feature request for completely disabling the floating menu: CONFCLOUD-81716: Ability to disable floating menu options/selection toolbar when text is highlighted 

However, this does feel like an issue with the tool/editor itself. 
What I would suggest in this case is reaching out to Atlassian Support (note that you need to be an app admin; if you cannot do it, you can ask your admin to raise a request/ticket and add you as a participant) for the support team to take a look at it and potentially escalate it to the product team(s). 👈

Cheers,
Tobi