Skip to content

[9.3] fix issue with cascade not showing on mobile (#255838)#262753

Merged
eokoneyo merged 1 commit intoelastic:9.3from
eokoneyo:backport/9.3/pr-255838
Apr 14, 2026
Merged

[9.3] fix issue with cascade not showing on mobile (#255838)#262753
eokoneyo merged 1 commit intoelastic:9.3from
eokoneyo:backport/9.3/pr-255838

Conversation

@eokoneyo
Copy link
Copy Markdown
Contributor

Backport

This will backport the following commits from main to 9.3:

Questions ?

Please refer to the Backport tool documentation

## Summary

Fixes issue with cascade experience not displaying on mobile.

### Visuals
<img width="606" height="927" alt="Screenshot 2026-03-22 at 21 48 05"
src="https://github.com/user-attachments/assets/e1dd4607-c279-4d43-a79c-3d3b569cbad2"
/>

_Cascade experience on mobile_

P.S. It should be noted that there's an open issue to refine the mobile
view for the cascade component itself, see
elastic#246968

<!--
### Checklist

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

- [ ] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [ ] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
- [ ] If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)
- [ ] This was checked for breaking HTTP API changes, and any breaking
changes have been approved by the breaking-change committee. The
`release_note:breaking` label should be applied in these situations.
- [ ] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
- [ ] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
- [ ] Review the [backport
guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)
and apply applicable `backport:*` labels.

### Identify risks

Does this PR introduce any risks? For example, consider risks like hard
to test bugs, performance regression, potential of data loss.

Describe the risk, its severity, and mitigation for each identified
risk. Invite stakeholders and evaluate how to proceed before merging.

- [ ] [See some risk
examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)
- [ ] ...

-->

(cherry picked from commit 772f5f6)

# Conflicts:
#	src/platform/plugins/shared/discover/public/application/main/components/layout/cascaded_documents/blocks/use_table_header_components.tsx
@eokoneyo eokoneyo requested a review from kibanamachine as a code owner April 13, 2026 11:24
@eokoneyo eokoneyo added the backport This PR is a backport of another PR label Apr 13, 2026
@eokoneyo eokoneyo enabled auto-merge (squash) April 13, 2026 11:24
@elasticmachine
Copy link
Copy Markdown
Contributor

💛 Build succeeded, but was flaky

Failed CI Steps

Test Failures

  • [job] [logs] FTR Configs #70 / Rules Management - Prebuilt Rules (Common tests) @ess @serverless @skipInServerlessMKI Review installation using mocked prebuilt rule assets Pagination returns correct rules for a page specified in the request

Metrics [docs]

✅ unchanged

@eokoneyo eokoneyo merged commit b10a877 into elastic:9.3 Apr 14, 2026
17 checks passed
@eokoneyo eokoneyo deleted the backport/9.3/pr-255838 branch April 14, 2026 09:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport This PR is a backport of another PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants