Skip to content

Comments

[8.x] NavigationItemOpenPanel: remove handling of landing page ("four squares" design) (#210893)#218133

Merged
tsullivan merged 2 commits intoelastic:8.xfrom
tsullivan:backport/8.x/pr-210893
Apr 15, 2025
Merged

[8.x] NavigationItemOpenPanel: remove handling of landing page ("four squares" design) (#210893)#218133
tsullivan merged 2 commits intoelastic:8.xfrom
tsullivan:backport/8.x/pr-210893

Conversation

@tsullivan
Copy link
Member

Backport

This will backport the following commits from main to 8.x:

Questions ?

Please refer to the Backport tool documentation

…es" design) (elastic#210893)

## Summary

Part of Epic: elastic/kibana-team#1439
Requires: elastic#212903

Changes:
1. Moves the Solution Side Nav away from the "four squares" design
pattern: where clicking the item label opens a landing page and the item
icon opens the secondary nav panel. This was a custom component
implemented in the Kibana package, not part of the EUI
`EuiCollapsibleNavBeta` component.
2. Changes some usage of `@emotion/css` to `@emotion/react` for better
developer experience

### Screenshots

<details><summary>Before</summary>

![01-security-solution-before](https://github.com/user-attachments/assets/259442a2-6cd5-45f2-be27-1b4e9ef26b04)

</details>

<details><summary>After</summary>

![02-security-solution-after](https://github.com/user-attachments/assets/a8ef8476-e36d-479f-9eba-2450b1df71ac)

</details>

### Checklist

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

- [x] [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
- [x] 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)

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

- [ ] This design pattern was only used in Security Solution. There is a
small risk of regression issues in Security Solution navigation. This
was mitigated by manual testing during development.

(cherry picked from commit 77523f7)

# Conflicts:
#	x-pack/test/security_solution_cypress/cypress/e2e/explore/navigation/navigation.cy.ts
@tsullivan tsullivan added the backport This PR is a backport of another PR label Apr 14, 2025
@tsullivan tsullivan enabled auto-merge (squash) April 14, 2025 14:49
@botelastic botelastic bot added the ci:project-deploy-observability Create an Observability project label Apr 14, 2025
@github-actions
Copy link
Contributor

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

  • /oblt-deploy : Deploy a Kibana instance using the Observability test environments.
  • run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

@elasticmachine
Copy link
Contributor

⏳ Build in-progress

  • Buildkite Build
  • Commit: 9c478b3
  • Kibana Serverless Image: docker.elastic.co/kibana-ci/kibana-serverless:pr-218133-9c478b35e55a

History

@tsullivan tsullivan merged commit 0cc28d0 into elastic:8.x Apr 15, 2025
8 checks passed
@tsullivan tsullivan deleted the backport/8.x/pr-210893 branch April 15, 2025 15:03
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 ci:project-deploy-observability Create an Observability project

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants