# \[Bug\] Visualizations: Data table with image

**URL:** <https://discuss.elastic.co/t/bug-visualizations-data-table-with-image/271427>\
**Category:** Kibana\
**Created:** [April 27, 2021, 6:03pm UTC](https://discuss.elastic.co/t/bug-visualizations-data-table-with-image/271427 "2021-04-27T18:03:24Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![cceyda](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cceyda/32/87806_2.png) [@cceyda](https://discuss.elastic.co/u/cceyda)\
**Post date:** [April 27, 2021, 6:03pm UTC](https://discuss.elastic.co/t/bug-visualizations-data-table-with-image/271427/1 "2021-04-27T18:03:24Z")

</div>

I opened an issue : [[Bug] Visualizations: Data table image weirdness · Issue #98257 · elastic/kibana · GitHub](https://github.com/elastic/kibana/issues/98257)  
but no one replied so posting here too

**Kibana version:** 7.12.0

**Elasticsearch version:** 7.12.0

**Server OS version:** ubuntu 18.04

**Browser version:** Chrome / Firefox latest

**Original install method (e.g. download page, yum, from source, etc.):** docker

**Describe the bug:**  
Data table rows used to fit to image height, now it doesn't.  
Normal in 7.11.1  
Broken in 7.12.0

**Steps to reproduce:**

1. data table visualization
2. Index pattern with url field set as below;  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/3/2/32920d436cfd215d01975ddb0cd7ba10f7098050.png)
3. terms query with url

**Expected behavior:**  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/8/1/81afa60437dabf925fe981497579a3cfc4d6c8db.png)

**Screenshots (if relevant):**  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/7/3/73ba68ed7fc199917e8dbed3969c08a61b27e605.png)

\*\*Errors in browser console (if relevant):\*\*None

\*\*Provide logs and/or server output (if relevant):\*\*None

**Any additional context:**  
Updated from 7.11.1 to 7.12.0  
New visualization also created within 7.12.0 also have the same problem. (so it is not a migration issue)  
7.12.1 still has problem

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [April 28, 2021, 5:42am UTC](https://discuss.elastic.co/t/bug-visualizations-data-table-with-image/271427/2 "2021-04-28T05:42:26Z")

</div>

Hi @cceyda Thanks for joining the community and filing the bug.

Looks to me that someone took a look and it is marked for triage.

I would suggest checking in to see when it may get addressed / how it progresses

---

<div class="post-metadata">

**Author:** ![matw](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/matw/32/13913_2.png) [@matw](https://discuss.elastic.co/u/matw)\
**Post date:** [April 28, 2021, 9:29am UTC](https://discuss.elastic.co/t/bug-visualizations-data-table-with-image/271427/3 "2021-04-28T09:29:51Z")

</div>

Hi  
We are currently discussing this issue, we migrated to a new component recently :

> <https://github.com/elastic/kibana/pull/70801>
>
> \## Summary
> 
> Resolves https://github.com/elastic/kibana/issues/64444
> Resolves https://github.com/elastic/kibana/issues/2516
> Resolves https://github.com/elastic/kibana/issues/2128
> 
> \*\*This converts the \`Data table\` visualization into \`React\` + EUI \`DataGrid\` component.\*\*
> 
> By default a new version of visualization will be used. Discussed with @timroes .
> To turn on the legacy one, include \`vis\_type\_table.legacyVisEnabled: true\` setting in \`kibana.yml\`.
> 
> \*\*Single table mode:\*\*
> 
> !\[image\](https://user-images.githubusercontent.com/31325372/100612519-2d7df200-3324-11eb-9c1f-42c81c2bca3f.png)
> 
> \*\*Split table mode (several grids displayed):\*\*
> 
> !\[image\](https://user-images.githubusercontent.com/31325372/100612851-a8dfa380-3324-11eb-86a4-f89d3a35110d.png)
> 
> The split table mode could have performance issue while a lot of data grids render at once.
> Despite this, the PR is good to go, since:
> 1. the feature is not widely used;
> 2. the legacy vis also has the inherent performance issue;
> 
> A separate issue is created to track and potentially solve the problem: https://github.com/elastic/kibana/issues/84509
> 
> \---
> 
> \### Changes include:
> \- either the legacy or the new visualization implementation is lazy loaded once \[depending on the feature flag\](https://github.com/elastic/kibana/pull/70801/files#diff-79003809e2d3517001d3be825d7d01f7cad641024117a5915cb1557ce9b2a4ebR61) \`legacyVisEnabled\`;
> \- legacy functional tests were adapted to check the new grid implementation, \[few of them\](https://github.com/elastic/kibana/pull/70801/files#diff-d672646828c4ca3e4e6f345e5ccce50cc040ff7ed4b8a334d1108a2b1264ac38) were saved to check the legacy data table in a separate \[thread\](https://github.com/elastic/kibana/pull/70801/files#diff-4e407c67fa238b7f6590efe3b7af0786cc0cafde9a679e26cae1c96f2284599d) (\[was discussed here\](https://github.com/elastic/kibana/pull/70801/files#r512640540))
> 
> \---
> 
> \### Release notes:
> \- \`Show toolbar\` option adds an ability to \`show/hide\` the visualization toolbar, where the only \`Export\` button currently live (the toolbar will be expanded in future releases).
> By default, a new visualization will have the toolbar disabled. Saved objects will be migrated to have the toolbar enabled initially.
> ( \[feature commit\](https://github.com/elastic/kibana/pull/70801/commits/0a90debc877405468293c18f6705c5483b3bec51), \[migration script commit\](https://github.com/elastic/kibana/pull/70801/commits/aac4c2df092e6059874646a5022e1322eca661a9) )
>   
>   
> !\[export\_table\](https://user-images.githubusercontent.com/31325372/101786483-09ce5f00-3b0f-11eb-8133-e73291fddbdf.png)
> 
> \- Exported as CSV tables will preserve the sorting by column direction!
> 
> \- Customizing a column \`width\` option is in. The value is saved into the \`uiState\` - that means columns width will be saved even after page reload. While using \`Split table\` mode, columns width will be synchronized between tables.
> 
> \*\*Single table mode\*\*
> !\[column\_resize\](https://user-images.githubusercontent.com/31325372/101787026-ad1f7400-3b0f-11eb-960f-d11cc69e93a2.gif)
> 
> 
> \*\*Split table mode\*\*
> !\[column\_resize\_split\_table\](https://user-images.githubusercontent.com/31325372/101787325-04254900-3b10-11eb-9b61-4d093b16c37a.gif)
> 
> 
> \- Expand a cell to see a collapsed content - hover over the cell to see the expand button:
> 
> !\[expand\_cell\](https://user-images.githubusercontent.com/31325372/101786722-4ef29100-3b0f-11eb-8546-4a4232646978.png)
> 
> 
> \### Checklist
> 
> Delete any items that are not applicable to this PR.
> 
> \- \[x\] 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/master/packages/kbn-i18n/README.md)
> \- \[x\] \[Documentation\](https://github.com/elastic/kibana/blob/master/CONTRIBUTING.md#writing-documentation) was added for features that require explanation or tutorials
> \- \[x\] \[Unit or functional tests\](https://github.com/elastic/kibana/blob/master/CONTRIBUTING.md#cross-browser-compatibility) were updated or added to match the most common scenarios
> \- \[x\] This was checked for \[keyboard-only and screenreader accessibility\](https://developer.mozilla.org/en-US/docs/Learn/Tools\_and\_testing/Cross\_browser\_testing/Accessibility#Accessibility\_testing\_checklist)
> \- \[x\] This renders correctly on smaller devices using a responsive layout. (You can test this \[in your browser\](https://www.browserstack.com/guide/responsive-testing-on-local-server)
> \- \[x\] This was checked for \[cross-browser compatibility\](https://www.elastic.co/support/matrix#matrix\_browsers)
> 
> \### For maintainers
> 
> \- \[\] This was checked for breaking API changes and was \[labeled appropriately\](https://github.com/elastic/kibana/blob/master/CONTRIBUTING.md#release-notes-process)

By setting `vis_type_table.legacyVisEnabled: true` setting in `kibana.yml` you can still use the old one.  
And here is the issue to track where we discuss to support multiline content in the new grid:

> <https://github.com/elastic/eui/issues/4634>
>
> Right now, the datagrid doesn't display the entire content if the content is long enough. Here is an example of how...

Best,  
Matthias

---

<div class="post-metadata">

**Author:** ![cceyda](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cceyda/32/87806_2.png) [@cceyda](https://discuss.elastic.co/u/cceyda)\
**Post date:** [April 28, 2021, 12:48pm UTC](https://discuss.elastic.co/t/bug-visualizations-data-table-with-image/271427/4 "2021-04-28T12:48:51Z")

</div>

Thank you @matw adding `vis_type_table.legacyVisEnabled: true` to `kibana.yml` solved the issue~

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [May 26, 2021, 12:49pm UTC](https://discuss.elastic.co/t/bug-visualizations-data-table-with-image/271427/5 "2021-05-26T12:49:37Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
