Repository navigation
[Search Profiler] Quick style fix up including dark theme - #33445
Conversation
|
Pinging @elastic/kibana-design |
|
Pinging @elastic/es-ui |
💔 Build Failed |
8634f90 to
9a76564
Compare
💚 Build Succeeded |
9a76564 to
51f86b7
Compare
|
I've updated based on your comment @bmcconaghy |
💚 Build Succeeded |
|
@cchaos looking great. the only thing I noticed was the flyout header looks a little cramped: |
|
I had to start a custom 7.0 backport here #33664 Because the tabset directive was removed only down to 7.x which I will be updating shortly |
b375456 to
df464b6
Compare
|
@bmcconaghy Flyout title is fixed up and same with the new tabset. |
💚 Build Succeeded |
|
@bmcconaghy This is ready for final review or 👍 |
|
Sorry for the delay, was on PTO until today. |
bmcconaghy
left a comment
There was a problem hiding this comment.
LGTM, thanks for the major improvement!
df464b6 to
5cec956
Compare
snide
left a comment
There was a problem hiding this comment.
I did a very quick code only scan of this. The CSS looks ok to me. Using the EUI css directly will likely cause us some trouble one day, but the components used are pretty stable and I don't see a quick solution other than converting this to React (which hopefully gets done by engineering later).
|
@cchaos any reason you have this with a skip label for release notes? seems like an enhancement even if it's just visual? |
|
Because I'm confused by the release_note labels... Changed it |
💚 Build Succeeded |
Summary
I noticed that the search profiler hadn't been updated in a while and was especially broken in dark mode. This fixes that up. Here's a quick gif of it all together in dark mode:
The only major change is that the details view has turned into a "pseudo"-flyout (since it's not React, this is just using the .euiFlyout classes).
It would be great to get this in for 7.0 so that it's not broken for those trying to use it in dark mode.
Fixes #21741, #18509, #18426, #18355, #18041
Checklist
Use
strikethroughsto remove checklist items you don't feel are applicable to this PR.[ ] 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[ ] This was checked for keyboard-only and screenreader accessibilityFor maintainers
[ ] This was checked for breaking API changes and was labeled appropriately[ ] This includes a feature addition or change that requires a release note and was labeled appropriately