[ML] Fix overflowing content in anomalies table cells #20029
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
peteharverson
added
review
v7.0.0
v6.4.0
:ml
Feature:ml-results
|
Pinging @elastic/ml-ui |
💔 Build Failed |
peteharverson
force-pushed
the
ml-anomalies-table-overflow
branch
from
d8791f5
to
2c491ac
Compare
💚 Build Succeeded |
peteharverson
added a commit
to peteharverson/kibana
that referenced
this pull request
Jun 19, 2018
peteharverson
added a commit
that referenced
this pull request
Jun 19, 2018
maryia-lapata
pushed a commit
to maryia-lapata/kibana
that referenced
this pull request
Jun 25, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes overflowing content in the Anomalies table cells (Firefox, Edge, IE) by adding the
eui-textBreakWordclass to the table that was added in elastic/eui#864.Before (Firefox):
After (Firefox):
Note Chrome supports
word-break: break-wordso the content breaks preferentially on words in Chrome (see content indescriptioncolumn), where in FF and IE it falls back toword-break: break-all:Fixes #19948