-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Ingest Manager] The long name breaks the UI structure for the Host details table under the Fleet tab. #85374
Comments
Pinging @elastic/ingest-management (Feature:Fleet) |
Pinging @elastic/ingest-management (Team:Ingest Management) |
@manishgupta-qasource Please review! |
Reviewed & assigned to @EricDavisX |
@nchaulet and @hbharding another UI / UX consideration for long strings, not urgent to me. I'll leave it to you. |
Hi @EricDavisX Today, while performing regression testing on 7.11 BC2 Kibana cloud build we tested this ticket again. Please find our observations below: Build details:
Observations:
However, as per reference to #84434, it is expected that:
Please let us know if anything else is required. Thanks |
@EricDavisX Request you please see the latest observation provided above by @amolnater-qasource & consider this bug |
reviewed - if easy, we could target 7.12 else, a later release |
@dikshachauhan-qasource this should be available in the BC4 build - please reset with crazy chars and long names here, and again anywhere else in the UI that they show, thanks for the diligence! |
Hi @EricDavisX
Observations:
Please let us know if anything else is required. |
Describe the bug
The long name breaks the UI structure for the Host details table under the Fleet tab.
Build Details:
Browser Details
All
Preconditions
Steps to Reproduce
Test data
N/A
Impacted Test case(s)
N/A
Actual Result
For a long name, the table structure is disturbed.
Expected Result
For any length of name, the table structure should retain.
What's Working
For a short name, the structure is preserved:
What's not Working
Screenshots
Logs
N/A
The text was updated successfully, but these errors were encountered: