Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[8.x] use info notice for color mode change notification toast (#205364) #205379

Merged
merged 1 commit into from
Jan 2, 2025

Conversation

kibanamachine
Copy link
Contributor

Backport

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

Questions ?

Please refer to the Backport tool documentation

","sha":"c41cf9a2d4d45207d47a7812a8139baca6a6fc4e","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:SharedUX","backport:prev-minor"],"title":"use info notice for color mode change notification toast","number":205364,"url":"https://github.com//pull/205364","mergeCommit":{"message":"use info notice for color mode change notification toast (#205364)\n\n## Summary\r\n\r\nThis PR changes the toast notification for instances when the color mode\r\nchanges from a toast that signifies a success operation to one that\r\ndenotes the presentation of an information.\r\n\r\n### Before\r\n

\"Screenshot

\r\n\r\n\r\n### After\r\n

\"Screenshot

\r\n\r\n\r\n\r\n","sha":"c41cf9a2d4d45207d47a7812a8139baca6a6fc4e"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com//pull/205364","number":205364,"mergeCommit":{"message":"use info notice for color mode change notification toast (#205364)\n\n## Summary\r\n\r\nThis PR changes the toast notification for instances when the color mode\r\nchanges from a toast that signifies a success operation to one that\r\ndenotes the presentation of an information.\r\n\r\n### Before\r\n

\"Screenshot

\r\n\r\n\r\n### After\r\n

\"Screenshot

\r\n\r\n\r\n\r\n","sha":"c41cf9a2d4d45207d47a7812a8139baca6a6fc4e"}}]}] BACKPORT-->

)

## Summary

This PR changes the toast notification for instances when the color mode
changes from a toast that signifies a success operation to one that
denotes the presentation of an information.

### Before
<img width="383" alt="Screenshot 2025-01-02 at 11 28 40"
src="https://github.com/user-attachments/assets/ff1df992-4f9c-4454-8dca-5a816c5ddf55"
/>

### After
<img width="353" alt="Screenshot 2025-01-02 at 11 20 11"
src="https://github.com/user-attachments/assets/f673edcc-ac07-4fdf-ba70-8491d75ffbe8"
/>

<!--
### 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/packages/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)

### 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 c41cf9a)
@kibanamachine kibanamachine merged commit 2060cb5 into elastic:8.x Jan 2, 2025
11 checks passed
@elasticmachine
Copy link
Contributor

💚 Build Succeeded

Metrics [docs]

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id before after diff
core 447.6KB 447.5KB -3.0B

cc @eokoneyo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants