Found in 7.0.0-alpha1 {"build":{"hash":"4b34b3f","date":"2018-08-20T07:24:33.371423Z"}
Horizontal scroll is missing from the Anomaly Explorer anomalies table. In the case where category examples are being displayed, it is therefore not possible to scroll to see the full examples.
As a workaround, you can expand the row and view examples.
Chrome

Safari
On safari, horizontal scroll is still missing, but you can drag and cause the details to display "off screen".

Part of #18553.
Pinging @elastic/ml-ui
Keen to hear thoughts on screenshots for:




cc @peteharverson, @walterra, @jgowdyelastic
Was it possible to add a horizontal scroll for the whole table, rather than a column?
i prefer the first example.
We could add an Examples tab to the expanded row where the examples are listed in a more readable format.
Of the two tooltip options, I think the first is probably good enough. Displaying the examples in the tooltip as in the second example seems a bit of a wasted effort as the user can just expand the row to view the full examples. Could there be a link in the tooltip to auto expand the row?
I like the idea of using an Examples tab in the expanded row to make them more readable, using a monospaced font perhaps to list each example, with dividing lines between each one - it can be difficult to tell where each example starts and end in the current view:

Would providing a width prop for the examples column give it a larger width than the rest of the columns as a quick (small) win? And perhaps move it across to the left, say after the detector column?
One of the downsides of the old table, which was scrollable, was that on scrolling across to view the examples, you could lose the context of which examples went with each anomaly as the columns on the left of the table dropped out of view.
Hey there, @alvarezmelissa87 asked me to jump in here with some suggestions.
I think the main struggle here is the amount of columns and content inside each cell. Since you are already using expanding rows, there may be ways to simplify the table. A couple of options:
detector and job ID. Could these be just visible in the expanded section but also pulled into the filter bar as a way for the user to filter down to the ones they want to see?However, if you can't do any of those, I'd suggest using the truncation and displaying the truncated text within the tooltip. You can go further and allow truncated rows or cells to have an onClick that will trigger the row expansion so they can see the full details.
As your content grows, you may also want to consider switching from using expanded rows to flyouts which can give you more space to work with.
As a _side_ note, also try to ensure that the actions column is always the last if nothing more than to be consistent with the rest of the tables within Kibana.
Thank you to everyone for all your comments and thoughts!
After a quick chat with Pete - looks like the best solution here currently is:
Example of separate tab for category examples. Expanding row from category examples column opens with Category examples tab selected.

Category examples tab:

Remove jobId column when only one job is being viewed:

cc @cchaos - keen to hear what you think of what we ended up coming up with. Thanks!