[Fleet] Scroller is given for empty screen under the Endpoint Security Integration tab.

[muskangulati-qasource]

Describe the bug
Scroller is given for empty screen under the Endpoint Security Integration tab.

Build Details:

Version: 7.11.0 BC8
Commit: 3f71ce7177a41e067ddb1e670ec4ace5f6d4f5fe
Build number: 37897
Artifact: https://staging.elastic.co/7.11.0-657c0367/summary-7.11.0.html

Browser Details
All

Preconditions

1. Cloud environment on staging should exist.

Steps to Reproduce

1. Navigate to Kibana URL on Browser.
2. Click on the "Fleet" tab under from the left navigation bar.
3. Click on the Integrations tab and navigate to Elastic Security Integration.
4. Observe that empty screen is displayed if user scrolls down.

Test data
N/A

Impacted Test case(s)
N/A

Actual Result
Scroller is given for empty screen under the Endpoint Security Integration tab.

Expected Result
Scroller should not be given for empty screen under the Endpoint Security Integration tab.

What's Working
N/A

What's not Working
N/A

Screenshots

Logs
N/A

[manishgupta-qasource]

Reviewed & Assigned @EricDavisX

[amolnater-qasource]

Hi @EricDavisX

This issue is occurring only for integrations that are not having image in the description part.
For example:

• Barracuda
• Blue Coat Director
• Cyber Ark
• CylanceProtect etc

Thanks

[EricDavisX]

interesting. @jen-huang @hbharding any interest or ideas? it is low priority.

[jen-huang]

Thanks for the report, not sure how we've never noticed this before! It does indeed seem to happen for integrations without screenshots, and the length of the scroll is based on how long the un-collapsed documentation content is.

I put up a PR yesterday that revamps the overview page: #90887. It should resolve this too since we got rid of the expand/collapse content toggle. Screenshots were moved to the right column too.

[EricDavisX]

It is merged now, so should be testable on 8.0 cloud when you get in @manishgupta-qasource ;)

[muskangulati-qasource]

Hi @EricDavisX,

We tested this ticket on the latest 7.12.0-SNAPSHOT and 8.0-SNAPSHOT builds and found that issue is now fixed. Please find below the complete testing details:

Build Details:

• Version: 7.12.0-SNAPSHOT

Commit: 1fc8122c6d14bc9c988c3f068e2878e07665410f
Build number: 38790
Artifact: https://artifacts-api.elastic.co/v1/search/7.12-SNAPSHOT

• Version: 8.0-SNAPSHOT

Commit: 2f7689882fa43c0b25ff850ad54a1f4556b3aacb
Build number: 40444
Artifact: https://artifacts-api.elastic.co/v1/search/8.0-SNAPSHOT

Refer Screenshot:

• Version: 7.12.0-SNAPSHOT
  

• Version: 8.0-SNAPSHOT
  

Thanks!!