Skip to content

[Dashboard][A11y] Improve usability of dashboard in 400% zoom#228978

Merged
cqliu1 merged 13 commits intoelastic:mainfrom
cqliu1:a11y/dashboard-400-zoom-usability
Aug 4, 2025
Merged

[Dashboard][A11y] Improve usability of dashboard in 400% zoom#228978
cqliu1 merged 13 commits intoelastic:mainfrom
cqliu1:a11y/dashboard-400-zoom-usability

Conversation

@cqliu1
Copy link
Contributor

@cqliu1 cqliu1 commented Jul 22, 2025

Summary

Closes #182848.

This PR improves the usability of dashboard up to 400% zoom. The unified search bar is no longer sticky on small viewports. I also force a min-height of the available height on a maximized panel.

1280x1024 @ 400% zoom (equivalent of 320x256)

Scrollable unified search bar
Jul-29-2025.09-27-34.mp4
Maximized panel
Jul-29-2025.09-32-11.mp4

Notable changes:

  • Allow unified search bar to scroll when the viewport width is < 768px
  • Add min-width of the viewport to maximized panels when viewport width is < 768px

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, uses sentence case text and includes i18n support
  • Documentation was added for features that require explanation or tutorials
  • Unit or functional tests 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
  • 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 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
  • Review the backport guidelines 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.

@cqliu1 cqliu1 force-pushed the a11y/dashboard-400-zoom-usability branch from 5745b38 to a9c71fc Compare July 29, 2025 15:44
@cqliu1 cqliu1 added Project:Accessibility Team:Presentation Presentation Team for Dashboard, Input Controls, and Canvas t// Feature:Dashboard Dashboard related features impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. loe:medium Medium Level of Effort impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. v9.2.0 release_note:enhancement and removed impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. labels Jul 29, 2025
@cqliu1 cqliu1 marked this pull request as ready for review July 29, 2025 16:38
@cqliu1 cqliu1 requested a review from a team as a code owner July 29, 2025 16:38
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-accessibility (Project:Accessibility)

@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-presentation (Team:Presentation)

@cqliu1 cqliu1 requested a review from a team July 29, 2025 16:38
@bhavyarm bhavyarm added the ci:cloud-deploy Create or update a Cloud deployment label Jul 29, 2025
@cqliu1 cqliu1 requested a review from bhavyarm July 29, 2025 16:49
Copy link
Contributor

@ThomThomson ThomThomson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Changes LGTM! Simple style fixes so code only review. Nice work!

@cqliu1 cqliu1 added v9.0.5 v9.1.1 backport:version Backport to applied version labels labels Jul 29, 2025
Copy link
Contributor

@andreadelrio andreadelrio left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Design changes LGTM.

Copy link
Contributor

@bhavyarm bhavyarm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the change @cqliu1 Do you know if we can fix the field values pop-up getting disconnected from search bar -

search_disconnected.mp4

Thanks,
Bhavya

Co-authored-by: Marta Bondyra <4283304+mbondyra@users.noreply.github.com>
Copy link
Contributor

@bhavyarm bhavyarm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@elasticmachine
Copy link
Contributor

elasticmachine commented Aug 4, 2025

💚 Build Succeeded

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
dashboard 620.0KB 620.2KB +186.0B
unifiedSearch 343.4KB 343.9KB +540.0B
total +726.0B

History

@cqliu1 cqliu1 merged commit 98bfa05 into elastic:main Aug 4, 2025
12 checks passed
@kibanamachine
Copy link
Contributor

Starting backport for target branches: 9.0, 9.1

https://github.com/elastic/kibana/actions/runs/16732560761

kibanamachine pushed a commit to kibanamachine/kibana that referenced this pull request Aug 4, 2025
…c#228978)

## Summary

Closes elastic#182848.

This PR improves the usability of dashboard up to 400% zoom. The unified
search bar is no longer sticky on small viewports. I also force a
min-height of the available height on a maximized panel.

#### 1280x1024 @ 400% zoom (equivalent of 320x256)

##### Scrollable unified search bar

https://github.com/user-attachments/assets/0e69d6bc-5591-423e-b213-d8bd56656218

##### Maximized panel

https://github.com/user-attachments/assets/c9775858-ce72-47b7-9875-d96c093b01ec

Notable changes:
- Allow unified search bar to scroll when the viewport width is < 768px
- Add min-width of the viewport to maximized panels when viewport width
is < 768px

### 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)
- [ ] ...

---------

Co-authored-by: Marta Bondyra <4283304+mbondyra@users.noreply.github.com>
(cherry picked from commit 98bfa05)
@kibanamachine
Copy link
Contributor

💔 Some backports could not be created

Status Branch Result
9.0 Backport failed because of merge conflicts
9.1

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

Manual backport

To create the backport manually run:

node scripts/backport --pr 228978

Questions ?

Please refer to the Backport tool documentation

kibanamachine added a commit that referenced this pull request Aug 4, 2025
…228978) (#230471)

# Backport

This will backport the following commits from `main` to `9.1`:
- [[Dashboard][A11y] Improve usability of dashboard in 400% zoom
(#228978)](#228978)

<!--- Backport version: 9.6.6 -->

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

<!--BACKPORT [{"author":{"name":"Catherine
Liu","email":"catherine.liu@elastic.co"},"sourceCommit":{"committedDate":"2025-08-04T19:40:07Z","message":"[Dashboard][A11y]
Improve usability of dashboard in 400% zoom (#228978)\n\n##
Summary\n\nCloses #182848.\n\nThis PR improves the usability of
dashboard up to 400% zoom. The unified\nsearch bar is no longer sticky
on small viewports. I also force a\nmin-height of the available height
on a maximized panel.\n\n#### 1280x1024 @ 400% zoom (equivalent of
320x256)\n\n##### Scrollable unified search
bar\n\nhttps://github.com/user-attachments/assets/0e69d6bc-5591-423e-b213-d8bd56656218\n\n#####
Maximized
panel\n\n\nhttps://github.com/user-attachments/assets/c9775858-ce72-47b7-9875-d96c093b01ec\n\nNotable
changes:\n- Allow unified search bar to scroll when the viewport width
is < 768px\n- Add min-width of the viewport to maximized panels when
viewport width\nis < 768px\n\n\n### Checklist\n\nCheck the PR satisfies
following conditions. \n\nReviewers should verify this PR satisfies this
list as well.\n\n- [ ] Any text added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n-
[
]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials\n- [ ] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common scenarios\n- [ ] If a plugin
configuration key changed, check if it needs to be\nallowlisted in the
cloud and added to the
[docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n-
[ ] This was checked for breaking HTTP API changes, and any
breaking\nchanges have been approved by the breaking-change committee.
The\n`release_note:breaking` label should be applied in these
situations.\n- [ ] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [ ] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n-
[ ] Review the
[backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand
apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this
PR introduce any risks? For example, consider risks like hard\nto test
bugs, performance regression, potential of data loss.\n\nDescribe the
risk, its severity, and mitigation for each identified\nrisk. Invite
stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See
some
risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n-
[ ] ...\n\n---------\n\nCo-authored-by: Marta Bondyra
<4283304+mbondyra@users.noreply.github.com>","sha":"98bfa0554550f5829ef3fc924989332b9ef77893","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","Feature:Dashboard","Project:Accessibility","Team:Presentation","loe:medium","impact:medium","ci:cloud-deploy","backport:version","v9.2.0","v9.0.5","v9.1.1"],"title":"[Dashboard][A11y]
Improve usability of dashboard in 400%
zoom","number":228978,"url":"https://github.com/elastic/kibana/pull/228978","mergeCommit":{"message":"[Dashboard][A11y]
Improve usability of dashboard in 400% zoom (#228978)\n\n##
Summary\n\nCloses #182848.\n\nThis PR improves the usability of
dashboard up to 400% zoom. The unified\nsearch bar is no longer sticky
on small viewports. I also force a\nmin-height of the available height
on a maximized panel.\n\n#### 1280x1024 @ 400% zoom (equivalent of
320x256)\n\n##### Scrollable unified search
bar\n\nhttps://github.com/user-attachments/assets/0e69d6bc-5591-423e-b213-d8bd56656218\n\n#####
Maximized
panel\n\n\nhttps://github.com/user-attachments/assets/c9775858-ce72-47b7-9875-d96c093b01ec\n\nNotable
changes:\n- Allow unified search bar to scroll when the viewport width
is < 768px\n- Add min-width of the viewport to maximized panels when
viewport width\nis < 768px\n\n\n### Checklist\n\nCheck the PR satisfies
following conditions. \n\nReviewers should verify this PR satisfies this
list as well.\n\n- [ ] Any text added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n-
[
]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials\n- [ ] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common scenarios\n- [ ] If a plugin
configuration key changed, check if it needs to be\nallowlisted in the
cloud and added to the
[docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n-
[ ] This was checked for breaking HTTP API changes, and any
breaking\nchanges have been approved by the breaking-change committee.
The\n`release_note:breaking` label should be applied in these
situations.\n- [ ] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [ ] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n-
[ ] Review the
[backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand
apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this
PR introduce any risks? For example, consider risks like hard\nto test
bugs, performance regression, potential of data loss.\n\nDescribe the
risk, its severity, and mitigation for each identified\nrisk. Invite
stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See
some
risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n-
[ ] ...\n\n---------\n\nCo-authored-by: Marta Bondyra
<4283304+mbondyra@users.noreply.github.com>","sha":"98bfa0554550f5829ef3fc924989332b9ef77893"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","9.1"],"targetPullRequestStates":[{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/228978","number":228978,"mergeCommit":{"message":"[Dashboard][A11y]
Improve usability of dashboard in 400% zoom (#228978)\n\n##
Summary\n\nCloses #182848.\n\nThis PR improves the usability of
dashboard up to 400% zoom. The unified\nsearch bar is no longer sticky
on small viewports. I also force a\nmin-height of the available height
on a maximized panel.\n\n#### 1280x1024 @ 400% zoom (equivalent of
320x256)\n\n##### Scrollable unified search
bar\n\nhttps://github.com/user-attachments/assets/0e69d6bc-5591-423e-b213-d8bd56656218\n\n#####
Maximized
panel\n\n\nhttps://github.com/user-attachments/assets/c9775858-ce72-47b7-9875-d96c093b01ec\n\nNotable
changes:\n- Allow unified search bar to scroll when the viewport width
is < 768px\n- Add min-width of the viewport to maximized panels when
viewport width\nis < 768px\n\n\n### Checklist\n\nCheck the PR satisfies
following conditions. \n\nReviewers should verify this PR satisfies this
list as well.\n\n- [ ] Any text added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n-
[
]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials\n- [ ] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common scenarios\n- [ ] If a plugin
configuration key changed, check if it needs to be\nallowlisted in the
cloud and added to the
[docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n-
[ ] This was checked for breaking HTTP API changes, and any
breaking\nchanges have been approved by the breaking-change committee.
The\n`release_note:breaking` label should be applied in these
situations.\n- [ ] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [ ] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n-
[ ] Review the
[backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand
apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this
PR introduce any risks? For example, consider risks like hard\nto test
bugs, performance regression, potential of data loss.\n\nDescribe the
risk, its severity, and mitigation for each identified\nrisk. Invite
stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See
some
risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n-
[ ] ...\n\n---------\n\nCo-authored-by: Marta Bondyra
<4283304+mbondyra@users.noreply.github.com>","sha":"98bfa0554550f5829ef3fc924989332b9ef77893"}},{"branch":"9.0","label":"v9.0.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.1","label":"v9.1.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Catherine Liu <catherine.liu@elastic.co>
Co-authored-by: Marta Bondyra <4283304+mbondyra@users.noreply.github.com>
szaffarano pushed a commit to szaffarano/kibana that referenced this pull request Aug 5, 2025
…c#228978)

## Summary

Closes elastic#182848.

This PR improves the usability of dashboard up to 400% zoom. The unified
search bar is no longer sticky on small viewports. I also force a
min-height of the available height on a maximized panel.

#### 1280x1024 @ 400% zoom (equivalent of 320x256)

##### Scrollable unified search bar

https://github.com/user-attachments/assets/0e69d6bc-5591-423e-b213-d8bd56656218

##### Maximized panel


https://github.com/user-attachments/assets/c9775858-ce72-47b7-9875-d96c093b01ec

Notable changes:
- Allow unified search bar to scroll when the viewport width is < 768px
- Add min-width of the viewport to maximized panels when viewport width
is < 768px


### 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)
- [ ] ...

---------

Co-authored-by: Marta Bondyra <4283304+mbondyra@users.noreply.github.com>
cqliu1 added a commit to cqliu1/kibana that referenced this pull request Aug 5, 2025
…c#228978)

## Summary

Closes elastic#182848.

This PR improves the usability of dashboard up to 400% zoom. The unified
search bar is no longer sticky on small viewports. I also force a
min-height of the available height on a maximized panel.

#### 1280x1024 @ 400% zoom (equivalent of 320x256)

##### Scrollable unified search bar

https://github.com/user-attachments/assets/0e69d6bc-5591-423e-b213-d8bd56656218

##### Maximized panel

https://github.com/user-attachments/assets/c9775858-ce72-47b7-9875-d96c093b01ec

Notable changes:
- Allow unified search bar to scroll when the viewport width is < 768px
- Add min-width of the viewport to maximized panels when viewport width
is < 768px

### 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)
- [ ] ...

---------

Co-authored-by: Marta Bondyra <4283304+mbondyra@users.noreply.github.com>
(cherry picked from commit 98bfa05)

# Conflicts:
#	src/platform/plugins/shared/dashboard/public/dashboard_renderer/grid/dashboard_grid.tsx
#	src/platform/plugins/shared/dashboard/public/dashboard_top_nav/internal_dashboard_top_nav.tsx
@cqliu1
Copy link
Contributor Author

cqliu1 commented Aug 5, 2025

💚 All backports created successfully

Status Branch Result
9.0

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

Questions ?

Please refer to the Backport tool documentation

delanni pushed a commit to delanni/kibana that referenced this pull request Aug 5, 2025
…c#228978)

## Summary

Closes elastic#182848.

This PR improves the usability of dashboard up to 400% zoom. The unified
search bar is no longer sticky on small viewports. I also force a
min-height of the available height on a maximized panel.

#### 1280x1024 @ 400% zoom (equivalent of 320x256)

##### Scrollable unified search bar

https://github.com/user-attachments/assets/0e69d6bc-5591-423e-b213-d8bd56656218

##### Maximized panel


https://github.com/user-attachments/assets/c9775858-ce72-47b7-9875-d96c093b01ec

Notable changes:
- Allow unified search bar to scroll when the viewport width is < 768px
- Add min-width of the viewport to maximized panels when viewport width
is < 768px


### 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)
- [ ] ...

---------

Co-authored-by: Marta Bondyra <4283304+mbondyra@users.noreply.github.com>
cqliu1 added a commit that referenced this pull request Aug 7, 2025
…228978) (#230604)

# Backport

This will backport the following commits from `main` to `9.0`:
- [[Dashboard][A11y] Improve usability of dashboard in 400% zoom
(#228978)](#228978)

<!--- Backport version: 10.0.1 -->

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

<!--BACKPORT [{"author":{"name":"Catherine
Liu","email":"catherine.liu@elastic.co"},"sourceCommit":{"committedDate":"2025-08-04T19:40:07Z","message":"[Dashboard][A11y]
Improve usability of dashboard in 400% zoom (#228978)\n\n##
Summary\n\nCloses #182848.\n\nThis PR improves the usability of
dashboard up to 400% zoom. The unified\nsearch bar is no longer sticky
on small viewports. I also force a\nmin-height of the available height
on a maximized panel.\n\n#### 1280x1024 @ 400% zoom (equivalent of
320x256)\n\n##### Scrollable unified search
bar\n\nhttps://github.com/user-attachments/assets/0e69d6bc-5591-423e-b213-d8bd56656218\n\n#####
Maximized
panel\n\n\nhttps://github.com/user-attachments/assets/c9775858-ce72-47b7-9875-d96c093b01ec\n\nNotable
changes:\n- Allow unified search bar to scroll when the viewport width
is < 768px\n- Add min-width of the viewport to maximized panels when
viewport width\nis < 768px\n\n\n### Checklist\n\nCheck the PR satisfies
following conditions. \n\nReviewers should verify this PR satisfies this
list as well.\n\n- [ ] Any text added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n-
[
]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials\n- [ ] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common scenarios\n- [ ] If a plugin
configuration key changed, check if it needs to be\nallowlisted in the
cloud and added to the
[docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n-
[ ] This was checked for breaking HTTP API changes, and any
breaking\nchanges have been approved by the breaking-change committee.
The\n`release_note:breaking` label should be applied in these
situations.\n- [ ] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [ ] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n-
[ ] Review the
[backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand
apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this
PR introduce any risks? For example, consider risks like hard\nto test
bugs, performance regression, potential of data loss.\n\nDescribe the
risk, its severity, and mitigation for each identified\nrisk. Invite
stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See
some
risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n-
[ ] ...\n\n---------\n\nCo-authored-by: Marta Bondyra
<4283304+mbondyra@users.noreply.github.com>","sha":"98bfa0554550f5829ef3fc924989332b9ef77893","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","Feature:Dashboard","Project:Accessibility","Team:Presentation","loe:medium","impact:medium","ci:cloud-deploy","backport:version","v9.2.0","v9.0.5","v9.1.1"],"title":"[Dashboard][A11y]
Improve usability of dashboard in 400%
zoom","number":228978,"url":"https://github.com/elastic/kibana/pull/228978","mergeCommit":{"message":"[Dashboard][A11y]
Improve usability of dashboard in 400% zoom (#228978)\n\n##
Summary\n\nCloses #182848.\n\nThis PR improves the usability of
dashboard up to 400% zoom. The unified\nsearch bar is no longer sticky
on small viewports. I also force a\nmin-height of the available height
on a maximized panel.\n\n#### 1280x1024 @ 400% zoom (equivalent of
320x256)\n\n##### Scrollable unified search
bar\n\nhttps://github.com/user-attachments/assets/0e69d6bc-5591-423e-b213-d8bd56656218\n\n#####
Maximized
panel\n\n\nhttps://github.com/user-attachments/assets/c9775858-ce72-47b7-9875-d96c093b01ec\n\nNotable
changes:\n- Allow unified search bar to scroll when the viewport width
is < 768px\n- Add min-width of the viewport to maximized panels when
viewport width\nis < 768px\n\n\n### Checklist\n\nCheck the PR satisfies
following conditions. \n\nReviewers should verify this PR satisfies this
list as well.\n\n- [ ] Any text added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n-
[
]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials\n- [ ] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common scenarios\n- [ ] If a plugin
configuration key changed, check if it needs to be\nallowlisted in the
cloud and added to the
[docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n-
[ ] This was checked for breaking HTTP API changes, and any
breaking\nchanges have been approved by the breaking-change committee.
The\n`release_note:breaking` label should be applied in these
situations.\n- [ ] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [ ] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n-
[ ] Review the
[backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand
apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this
PR introduce any risks? For example, consider risks like hard\nto test
bugs, performance regression, potential of data loss.\n\nDescribe the
risk, its severity, and mitigation for each identified\nrisk. Invite
stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See
some
risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n-
[ ] ...\n\n---------\n\nCo-authored-by: Marta Bondyra
<4283304+mbondyra@users.noreply.github.com>","sha":"98bfa0554550f5829ef3fc924989332b9ef77893"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/228978","number":228978,"mergeCommit":{"message":"[Dashboard][A11y]
Improve usability of dashboard in 400% zoom (#228978)\n\n##
Summary\n\nCloses #182848.\n\nThis PR improves the usability of
dashboard up to 400% zoom. The unified\nsearch bar is no longer sticky
on small viewports. I also force a\nmin-height of the available height
on a maximized panel.\n\n#### 1280x1024 @ 400% zoom (equivalent of
320x256)\n\n##### Scrollable unified search
bar\n\nhttps://github.com/user-attachments/assets/0e69d6bc-5591-423e-b213-d8bd56656218\n\n#####
Maximized
panel\n\n\nhttps://github.com/user-attachments/assets/c9775858-ce72-47b7-9875-d96c093b01ec\n\nNotable
changes:\n- Allow unified search bar to scroll when the viewport width
is < 768px\n- Add min-width of the viewport to maximized panels when
viewport width\nis < 768px\n\n\n### Checklist\n\nCheck the PR satisfies
following conditions. \n\nReviewers should verify this PR satisfies this
list as well.\n\n- [ ] Any text added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n-
[
]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials\n- [ ] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common scenarios\n- [ ] If a plugin
configuration key changed, check if it needs to be\nallowlisted in the
cloud and added to the
[docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n-
[ ] This was checked for breaking HTTP API changes, and any
breaking\nchanges have been approved by the breaking-change committee.
The\n`release_note:breaking` label should be applied in these
situations.\n- [ ] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [ ] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n-
[ ] Review the
[backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand
apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this
PR introduce any risks? For example, consider risks like hard\nto test
bugs, performance regression, potential of data loss.\n\nDescribe the
risk, its severity, and mitigation for each identified\nrisk. Invite
stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See
some
risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n-
[ ] ...\n\n---------\n\nCo-authored-by: Marta Bondyra
<4283304+mbondyra@users.noreply.github.com>","sha":"98bfa0554550f5829ef3fc924989332b9ef77893"}},{"branch":"9.0","label":"v9.0.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.1","label":"v9.1.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/230471","number":230471,"state":"MERGED","mergeCommit":{"sha":"a0b0b7c4c829b3aab3083f81d74c149d044255a6","message":"[9.1]
[Dashboard][A11y] Improve usability of dashboard in 400% zoom (#228978)
(#230471)\n\n# Backport\n\nThis will backport the following commits from
`main` to `9.1`:\n- [[Dashboard][A11y] Improve usability of dashboard in
400%
zoom\n(#228978)](https://github.com/elastic/kibana/pull/228978)\n\n\n\n###
Questions ?\nPlease refer to the [Backport
tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by:
Catherine Liu <catherine.liu@elastic.co>\nCo-authored-by: Marta Bondyra
<4283304+mbondyra@users.noreply.github.com>"}}]}] BACKPORT-->
@wildemat wildemat mentioned this pull request Aug 7, 2025
10 tasks
@mistic mistic added v9.0.6 and removed v9.0.5 labels Aug 12, 2025
NicholasPeretti pushed a commit to NicholasPeretti/kibana that referenced this pull request Aug 18, 2025
…c#228978)

## Summary

Closes elastic#182848.

This PR improves the usability of dashboard up to 400% zoom. The unified
search bar is no longer sticky on small viewports. I also force a
min-height of the available height on a maximized panel.

#### 1280x1024 @ 400% zoom (equivalent of 320x256)

##### Scrollable unified search bar

https://github.com/user-attachments/assets/0e69d6bc-5591-423e-b213-d8bd56656218

##### Maximized panel


https://github.com/user-attachments/assets/c9775858-ce72-47b7-9875-d96c093b01ec

Notable changes:
- Allow unified search bar to scroll when the viewport width is < 768px
- Add min-width of the viewport to maximized panels when viewport width
is < 768px


### 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)
- [ ] ...

---------

Co-authored-by: Marta Bondyra <4283304+mbondyra@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport:version Backport to applied version labels ci:cloud-deploy Create or update a Cloud deployment Feature:Dashboard Dashboard related features impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. loe:medium Medium Level of Effort Project:Accessibility release_note:enhancement Team:Presentation Presentation Team for Dashboard, Input Controls, and Canvas t// v9.0.6 v9.1.1 v9.2.0

8 participants