# Kibana 9 - Detail pane is a bad replacement for Expandable row for my use cases

**URL:** <https://discuss.elastic.co/t/kibana-9-detail-pane-is-a-bad-replacement-for-expandable-row-for-my-use-cases/390555>\
**Category:** Kibana\
**Created:** [September 21, 2026, 12:00pm UTC](https://discuss.elastic.co/t/kibana-9-detail-pane-is-a-bad-replacement-for-expandable-row-for-my-use-cases/390555 "2026-09-21T12:00:16Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![poifir](https://avatars.discourse-cdn.com/v4/letter/p/9dc877/32.png) [@poifir](https://discuss.elastic.co/u/poifir)\
**Post date:** [September 21, 2026, 12:00pm UTC](https://discuss.elastic.co/t/kibana-9-detail-pane-is-a-bad-replacement-for-expandable-row-for-my-use-cases/390555/1 "2026-09-21T12:00:16Z")

</div>

In Kibana 8 we continued to use the "old" UI that offered to expand each row individually to show it's detail values.

This works good as the full width of the windows is also available to the detailed attributes and so no artificial line breaks are e.g. introduced in stack-traces.

With Kibana 9 the old UI is not available any longer and the new one is honestly a downgrade:

Instead of "Expandable row" the "Detail pane" pattern is used for visualization of detail entries.

This introduces several problems:

- only one detail entry can be opened at a time
- the detail pane is now limited to ~30% of the screen width, so it show artifical line breaks when the offered width is not sufficient

I'd vote for an option to make it customizable if the details are opened in

- Expandable Row
- Detail Pane

(Note that I'm using terms from the Clarity UI Framework to describe the detected patterns - unfortunately I'm not allowed to post links to their documentation but you'll find the detail in the "Datagrid" section in their documentation)

Thanks!

---

<div class="post-metadata">

**Author:** ![carly.richmond](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carly.richmond/32/104935_2.png) [@carly.richmond](https://discuss.elastic.co/u/carly.richmond)\
**Post date:** [October 5, 2026, 8:14am UTC](https://discuss.elastic.co/t/kibana-9-detail-pane-is-a-bad-replacement-for-expandable-row-for-my-use-cases/390555/2 "2026-10-05T08:14:33Z")

</div>

Thanks so much for your feedback @poifir. We appreciate it. Have you raised a GitHub issue with your suggestion at all?

Let us know!

Carly

---

<div class="post-metadata">

**Author:** ![poifir](https://avatars.discourse-cdn.com/v4/letter/p/9dc877/32.png) [@poifir](https://discuss.elastic.co/u/poifir)\
**Post date:** [October 5, 2026, 8:42am UTC](https://discuss.elastic.co/t/kibana-9-detail-pane-is-a-bad-replacement-for-expandable-row-for-my-use-cases/390555/3 "2026-10-05T08:42:02Z")

</div>

No - not yet, wasn't aware of a Github repo for feedback ...

---

<div class="post-metadata">

**Author:** ![carly.richmond](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carly.richmond/32/104935_2.png) [@carly.richmond](https://discuss.elastic.co/u/carly.richmond)\
**Post date:** [October 5, 2026, 8:57am UTC](https://discuss.elastic.co/t/kibana-9-detail-pane-is-a-bad-replacement-for-expandable-row-for-my-use-cases/390555/4 "2026-10-05T08:57:00Z")

</div>

If you want to suggest an enhancement you can raise an issue at [@elastic/kibana](https://github.com/elastic/kibana).