[Discover] Update layout for unified histogram

[davismcphee]

Summary

This PR adds support for resizing the histogram in Discover, and moves the view mode tabs below the histogram in preparation for the unified histogram project.

A la carte build: https://davismcphee-pr-139446-enhancement-discover-unified-histogra.kbndev.co

Flaky test run for new functional test: https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/1179

Resolves #138697.

Checklist

• 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
• Any UI touched in this PR is usable by keyboard only (learn more about keyboard accessibility)
• Any UI touched in this PR does not create any new axe failures (run axe in browser: FF, Chrome)
• If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
• This renders correctly on smaller devices using a responsive layout. (You can test this in your browser)
• This was checked for cross-browser compatibility

For maintainers

• This was checked for breaking API changes and was labeled appropriately

[kertal]

@kertal Fixed the whitespace and resizable issue when using non time based data views. I also fixed a flexbox issue where the document explorer would overflow the container after resizing the window when the fixed panels layout was shown. Commit: 03cf671.

great thx!

One thing to consider when thinking about the hits row for non time based data views is that sometimes it also shows a reset button if it's a saved search:

For me this looks ok!

[kertal]

thx a lot for sharing and documenting!

[kertal]

LGTM 👍 thx for inlining lots of explanations, this is very helpful! Tested locally with Chrome, Firefox, Safari. Thanks for taking care of the performance impact!

[andreadelrio]

@davismcphee Amazing work here Davis! Happy to see this become a reality. Just a comment, when I resize and I let go of the cursor, is it possible to go back to the initial state of the resize handler instead of staying with the blue bar on? Right now the only way to get rid of the blue bar is by doing an extra click outside and that feels a bit off.

@kertal when will we be able to get rid of the beta badge for Field Statistics? that tab would look a lot better without it.

[kertal]

@kertal when will we be able to get rid of the beta badge for Field Statistics? that tab would look a lot better without it.

Thx Andrea, this is a good question, if I remember I hink it was less a technical choice to add beta than a design choice ... so, are we there now in a post-beta world? Interested also in @ryankeairns opinion here. FYI @ninoslavmiskovic

[andreadelrio]

@kertal when will we be able to get rid of the beta badge for Field Statistics? that tab would look a lot better without it.

Thx Andrea, this is a good question, if I remember I hink it was less a technical choice to add beta than a design choice ... so, are we there now in a post-beta world? Interested also in @ryankeairns opinion here. FYI @ninoslavmiskovic

Design-wise I think that feature has been available long enough that we'd be ok to remove the badge.

[ryankeairns]

+1 what Andrea said; design has been in place for some time. I suppose it's ultimately a product decision at this point

The only nitpick I have is whether should use small tabs as opposed to the the default size. The font seems a bit heavy, visually, relative to the rest of the content on the screen.

Here's a sneak peek at the small size:

[kertal]

@kertal when will we be able to get rid of the beta badge for Field Statistics? that tab would look a lot better without it.

Thx Andrea, this is a good question, if I remember I hink it was less a technical choice to add beta than a design choice ... so, are we there now in a post-beta world? Interested also in @ryankeairns opinion here. FYI @ninoslavmiskovic

Design-wise I think that feature has been available long enough that we'd be ok to remove the badge.

ok, any objections removing beta of the field statistics dear @ninoslavmiskovic @ghudgins @qn895?

[ninoslavmiskovic]

+1 what Andrea said; design has been in place for some time. I suppose it's ultimately a product decision at this point

The only nitpick I have is whether should use small tabs as opposed to the default size. The font seems a bit heavy, visually, relative to the rest of the content on the screen.

Here's a sneak peek at the small size:

I agree with @ryankeairns regarding using a lighter font for the tabs.

Regarding removing the "beta" label. I am not aware of what the process is. I am used to look at performance, scalability, user feedback etc. before removing the beta.

When I look at Fullstory on how many users clicked on "Field Statistics" in Discover past 90 days, then it is 8%.

Before removing the beta - I would ask the team: Do we have enough user feedback? If that is a "no", then we should keep it and get some more. In my opinion getting user feedback is one of the main purposes running "Beta" programs, and "alpha".

[davismcphee]

@andreadelrio The resize button is now blurred after resizing with a mouse which gets rid of the focus styles.

@ryankeairns I've updated the layout to use small tabs instead:

Regarding the badge, I can make the change whenever we come to a decision, but it would be best if we could decide soon since the goal is to get this in before feature freeze on Sept 20.

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[andreadelrio]

Thanks for making those updates, LGTM.

[kertal]

@elasticmachine merge upstream

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: e957982

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
discover	472.7KB	477.1KB	+4.4KB

History

• 💚 Build #72936 succeeded 1da083e
• 💔 Build #72863 failed 8c461ae
• 💔 Build #72724 failed 5f4ac30
• 💚 Build #71509 succeeded f81bb09
• 💚 Build #71458 succeeded b506306
• 💚 Build #71411 succeeded fbbc618

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @davismcphee