kibana
kibana copied to clipboard
[Security Solution]Random Symbol showing in the global search bar
Describe the bug Random Symbol showing in the global search bar
Build Details
Version:8.2.0-SNAPSHOT
Commit:2a93e80574f9c1052c541bc4083a440a623899e8
Build:51328
Steps
- Login to Kibana
- Observed that random character been there showing in the global search bar
Screen-Shoot

Pinging @elastic/security-solution (Team: SecuritySolution)
Reviewed & assigned to @MadameSheema
@karanbirsingh-qasource is this happening just on fleet page or in all the different pages?
@karanbirsingh-qasource can you please provide the information asked above? Thanks
Hi @MadameSheema ,
@karanbirsingh-qasource is this happening just on fleet page or in all the different pages?
Yes, This is happening on all the different pages.
Screencast:
https://user-images.githubusercontent.com/61860752/159846566-628a465a-3ff6-407b-9491-2c143f8b672e.mp4
Thanks!!
Pinging @elastic/kibana-app-services (Team:AppServicesSv)
I believe this is intentional - it is showing a keyboard shortcut ctrl + / I believe to open up the search bar. Perhaps the caret symbol is what is confusing non-macOS users. @cchaos I see this was added in https://github.com/elastic/kibana/pull/127903, pinging for visibility.
I am going to re-assign this to the core team since they own that code - feel free to re-assign though!
Pinging @elastic/kibana-core (Team:Core)
I agree with @jloleysens, I think it's the keyboard shortcut hint. On macOS, the symbol shown refers to the Cmd + / shortcut:

Tagging the Platform Design team just in case they want to revisit the design to avoid this confusion.
Correct this is a symbol based visual for introducing the keyboard shortcut. I concluded this from PCMag that states:
The caret symbol is a common symbol for Control; for example, ^Y means Ctrl-Y.
If it's truly that confusing, for Windows users we could spell out CTRL but we have the full text in the footer of the search dropdown.
@elastic/appex-sharedux is it ok to close this issue since it's by design?
is it ok to close this issue since it's by design?
I'll assume so. Closing.