Skip to content

fix issue with cascade not showing on mobile#255838

Merged
eokoneyo merged 5 commits intoelastic:mainfrom
eokoneyo:fix/resolve-issue-with-cascade-no-rendering-on-mobile
Mar 23, 2026
Merged

fix issue with cascade not showing on mobile#255838
eokoneyo merged 5 commits intoelastic:mainfrom
eokoneyo:fix/resolve-issue-with-cascade-no-rendering-on-mobile

Conversation

@eokoneyo
Copy link
Copy Markdown
Contributor

@eokoneyo eokoneyo commented Mar 3, 2026 •
edited by kibanamachine
Loading

Summary

Fixes issue with cascade experience not displaying on mobile.

Visuals

Screenshot 2026-03-22 at 21 48 05

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 #246968

@eokoneyo eokoneyo self-assigned this Mar 3, 2026
@eokoneyo eokoneyo added the Team:SharedUX Platform AppEx-SharedUX (formerly Global Experience) t// label Mar 3, 2026
@eokoneyo eokoneyo linked an issue Mar 3, 2026 that may be closed by this pull request
Cascade experience doesn't show on mobile #255839
Closed
@eokoneyo eokoneyo mentioned this pull request Mar 3, 2026
Closed
@eokoneyo
Copy link
Copy Markdown
Contributor Author

eokoneyo commented Mar 5, 2026

/deploy-oblt

@eokoneyo
Copy link
Copy Markdown
Contributor Author

eokoneyo commented Mar 6, 2026

/oblt-deploy

@eokoneyo
Copy link
Copy Markdown
Contributor Author

eokoneyo commented Mar 11, 2026

@elasticmachine merge upstream

@eokoneyo
Copy link
Copy Markdown
Contributor Author

eokoneyo commented Mar 11, 2026

/oblt-deploy

@eokoneyo
Copy link
Copy Markdown
Contributor Author

eokoneyo commented Mar 19, 2026

@elasticmachine merge upstream

@eokoneyo eokoneyo force-pushed the fix/resolve-issue-with-cascade-no-rendering-on-mobile branch from c318d1a to e8ad378 Compare March 22, 2026 20:43
@eokoneyo eokoneyo marked this pull request as ready for review March 22, 2026 20:52
@eokoneyo eokoneyo requested review from a team as code owners March 22, 2026 20:52
@elasticmachine
Copy link
Copy Markdown
Contributor

elasticmachine commented Mar 22, 2026

Pinging @elastic/appex-sharedux (Team:SharedUX)

@eokoneyo eokoneyo added backport:version Backport to applied version labels v9.3.3 release_note:skip Skip the PR/issue when compiling release notes labels Mar 22, 2026
@eokoneyo eokoneyo force-pushed the fix/resolve-issue-with-cascade-no-rendering-on-mobile branch from e504d62 to c178c93 Compare March 22, 2026 22:59
@elasticmachine
Copy link
Copy Markdown
Contributor

elasticmachine commented Mar 22, 2026

⏳ Build in-progress, with failures

Failed CI Steps

History

cc @eokoneyo

@eokoneyo eokoneyo force-pushed the fix/resolve-issue-with-cascade-no-rendering-on-mobile branch from c178c93 to 5e18d04 Compare March 23, 2026 01:00
@eokoneyo eokoneyo force-pushed the fix/resolve-issue-with-cascade-no-rendering-on-mobile branch from 5e18d04 to 7926098 Compare March 23, 2026 10:33
@AlexGPlay
Copy link
Copy Markdown
Contributor

AlexGPlay commented Mar 23, 2026

general question, what is it that doesn't show on mobile? I'm testing cascade with a small screen before this PR and it's showing for me - other than the "Group by" button content being slightly broken it's looking the same for me

@eokoneyo
Copy link
Copy Markdown
Contributor Author

eokoneyo commented Mar 23, 2026

general question, what is it that doesn't show on mobile? I'm testing cascade with a small screen before this PR and it's showing for me - other than the "Group by" button content being slightly broken it's looking the same for me

We had it working previously, but there was a revert, so now If you make the screen small enough on main the cascade experience doesn't render. Fixed the issue with the "Group by" button here 7ef08b4

@AlexGPlay
Copy link
Copy Markdown
Contributor

AlexGPlay commented Mar 23, 2026

general question, what is it that doesn't show on mobile? I'm testing cascade with a small screen before this PR and it's showing for me - other than the "Group by" button content being slightly broken it's looking the same for me

We had it working previously, but there was a revert, so now If you make the screen small enough on main the cascade experience doesn't render. Fixed the issue with the "Group by" button here 7ef08b4

just trying to understand the fix, in main for me it's looking good:

cascade.mov

btw, maybe not related to this but i've got this for a couple of fields too

image

@kibanamachine
Copy link
Copy Markdown
Contributor

kibanamachine commented Mar 25, 2026

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 255838 locally
cc: @eokoneyo

jeramysoucy pushed a commit to jeramysoucy/kibana that referenced this pull request Mar 26, 2026
@eokoneyo @jeramysoucy
fix issue with cascade not showing on mobile (elastic#255838)
d5fe4ed 
## 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)
- [ ] ...


-->
@kibanamachine
Copy link
Copy Markdown
Contributor

kibanamachine commented Mar 26, 2026

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 255838 locally
cc: @eokoneyo

1 similar comment
@kibanamachine
Copy link
Copy Markdown
Contributor

kibanamachine commented Mar 27, 2026

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 255838 locally
cc: @eokoneyo

@kibanamachine kibanamachine mentioned this pull request Mar 30, 2026
Merged
1 task
@kibanamachine
Copy link
Copy Markdown
Contributor

kibanamachine commented Mar 30, 2026

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 255838 locally
cc: @eokoneyo

2 similar comments
@kibanamachine
Copy link
Copy Markdown
Contributor

kibanamachine commented Mar 30, 2026

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 255838 locally
cc: @eokoneyo

@kibanamachine
Copy link
Copy Markdown
Contributor

kibanamachine commented Mar 31, 2026

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 255838 locally
cc: @eokoneyo

@kibanamachine kibanamachine mentioned this pull request Apr 1, 2026
Merged
@kibanamachine
Copy link
Copy Markdown
Contributor

kibanamachine commented Apr 1, 2026

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 255838 locally
cc: @eokoneyo

8 similar comments
@kibanamachine
Copy link
Copy Markdown
Contributor

kibanamachine commented Apr 2, 2026

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 255838 locally
cc: @eokoneyo

@kibanamachine
Copy link
Copy Markdown
Contributor

kibanamachine commented Apr 4, 2026

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 255838 locally
cc: @eokoneyo

@kibanamachine
Copy link
Copy Markdown
Contributor

kibanamachine commented Apr 4, 2026

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 255838 locally
cc: @eokoneyo

@kibanamachine
Copy link
Copy Markdown
Contributor

kibanamachine commented Apr 6, 2026

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 255838 locally
cc: @eokoneyo

@kibanamachine
Copy link
Copy Markdown
Contributor

kibanamachine commented Apr 6, 2026

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 255838 locally
cc: @eokoneyo

@kibanamachine
Copy link
Copy Markdown
Contributor

kibanamachine commented Apr 7, 2026

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 255838 locally
cc: @eokoneyo

@kibanamachine
Copy link
Copy Markdown
Contributor

kibanamachine commented Apr 7, 2026

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 255838 locally
cc: @eokoneyo

@kibanamachine
Copy link
Copy Markdown
Contributor

kibanamachine commented Apr 8, 2026

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 255838 locally
cc: @eokoneyo

@kertal
Copy link
Copy Markdown
Member

kertal commented Apr 8, 2026

@eokoneyo do you want to backport this?

@eokoneyo
Copy link
Copy Markdown
Contributor Author

eokoneyo commented Apr 8, 2026

@eokoneyo do you want to backport this?

Yes! I will be backporting this along a whole bunch of other PRs too

@kibanamachine
Copy link
Copy Markdown
Contributor

kibanamachine commented Apr 9, 2026

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 255838 locally
cc: @eokoneyo

2 similar comments
@kibanamachine
Copy link
Copy Markdown
Contributor

kibanamachine commented Apr 10, 2026

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 255838 locally
cc: @eokoneyo

@kibanamachine
Copy link
Copy Markdown
Contributor

kibanamachine commented Apr 13, 2026

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 255838 locally
cc: @eokoneyo

eokoneyo added a commit to eokoneyo/kibana that referenced this pull request Apr 13, 2026
@eokoneyo
fix issue with cascade not showing on mobile (elastic#255838)
185695a 
## 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 mentioned this pull request Apr 13, 2026
Merged
@eokoneyo
Copy link
Copy Markdown
Contributor Author

eokoneyo commented Apr 13, 2026

💚 All backports created successfully

Status Branch Result
✅ 9.3

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation

@kibanamachine
Copy link
Copy Markdown
Contributor

kibanamachine commented Apr 14, 2026

Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync.
cc: @eokoneyo

eokoneyo added a commit that referenced this pull request Apr 14, 2026
@eokoneyo
[9.3] fix issue with cascade not showing on mobile (#255838) (#262753)
b10a877 
# Backport

This will backport the following commits from `main` to `9.3`:
- [fix issue with cascade not showing on mobile
(#255838)](#255838)

<!--- Backport version: 11.0.1 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Eyo O.
Eyo","email":"7893459+eokoneyo@users.noreply.github.com"},"sourceCommit":{"committedDate":"2026-03-23T16:45:48Z","message":"fix
issue with cascade not showing on mobile (#255838)\n\n##
Summary\n\nFixes issue with cascade experience not displaying on mobile.
\n\n### Visuals\n<img width=\"606\" height=\"927\" alt=\"Screenshot
2026-03-22 at 21 48
05\"\nsrc=\"https://github.com/user-attachments/assets/e1dd4607-c279-4d43-a79c-3d3b569cbad2\"\n/>\n\n\n\n_Cascade
experience on mobile_\n\nP.S. It should be noted that there's an open
issue to refine the mobile\nview for the cascade component itself,
see\nhttps://github.com//issues/246968\n\n","sha":"772f5f6a0247900b598f357d84b97ffb1578e796","branchLabelMapping":{"^v9.4.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport
missing","Team:SharedUX","backport:version","v9.4.0","v9.3.3"],"title":"fix
issue with cascade not showing on
mobile","number":255838,"url":"https://github.com/elastic/kibana/pull/255838","mergeCommit":{"message":"fix
issue with cascade not showing on mobile (#255838)\n\n##
Summary\n\nFixes issue with cascade experience not displaying on mobile.
\n\n### Visuals\n<img width=\"606\" height=\"927\" alt=\"Screenshot
2026-03-22 at 21 48
05\"\nsrc=\"https://github.com/user-attachments/assets/e1dd4607-c279-4d43-a79c-3d3b569cbad2\"\n/>\n\n\n\n_Cascade
experience on mobile_\n\nP.S. It should be noted that there's an open
issue to refine the mobile\nview for the cascade component itself,
see\nhttps://github.com//issues/246968\n\n","sha":"772f5f6a0247900b598f357d84b97ffb1578e796"}},"sourceBranch":"main","suggestedTargetBranches":["9.3"],"targetPullRequestStates":[{"branch":"main","label":"v9.4.0","branchLabelMappingKey":"^v9.4.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/255838","number":255838,"mergeCommit":{"message":"fix
issue with cascade not showing on mobile (#255838)\n\n##
Summary\n\nFixes issue with cascade experience not displaying on mobile.
\n\n### Visuals\n<img width=\"606\" height=\"927\" alt=\"Screenshot
2026-03-22 at 21 48
05\"\nsrc=\"https://github.com/user-attachments/assets/e1dd4607-c279-4d43-a79c-3d3b569cbad2\"\n/>\n\n\n\n_Cascade
experience on mobile_\n\nP.S. It should be noted that there's an open
issue to refine the mobile\nview for the cascade component itself,
see\nhttps://github.com//issues/246968\n\n","sha":"772f5f6a0247900b598f357d84b97ffb1578e796"}},{"branch":"9.3","label":"v9.3.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
@kibanamachine kibanamachine added v9.3.4 and removed backport missing Added to PRs automatically when the are determined to be missing a backport. labels Apr 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@AlexGPlay AlexGPlay AlexGPlay approved these changes

@kowalczyk-krzysztof kowalczyk-krzysztof kowalczyk-krzysztof approved these changes

Assignees

@eokoneyo eokoneyo

Labels

backport:version Backport to applied version labels release_note:skip Skip the PR/issue when compiling release notes Team:SharedUX Platform AppEx-SharedUX (formerly Global Experience) t// v9.3.3 v9.3.4 v9.4.0

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Cascade experience doesn't show on mobile

6 participants

@eokoneyo @elasticmachine @AlexGPlay @kibanamachine @kertal @kowalczyk-krzysztof