hover info should not be broken within word#106885
Merged
mjbvz merged 1 commit intomicrosoft:masterfrom Nov 7, 2020
Merged
Conversation
Zuckjet
force-pushed
the
fix-hover-style
branch
from
3e58472 to
56eaef8
Compare
Contributor
Author
|
CI error " ##[error]PowerShell exited with code '1' " seems is not relevant my changes |
Member
|
I did a quick blame on the CSS and it looks like it was introduced via #74582 |
|
The PR reserves the fix that rectified issue #74579 so does that need reopening/addressing? Is there a solution to fix both? |
Contributor
Author
the issue you posted is about adding word-wrap:break-word CSS property, but this PR is about removing word-break:break-all CSS property. I think they can work together. |
rheh
approved these changes
Nov 7, 2020
Collaborator
|
Thanks. Let's see how this goes in insiders |
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 participants
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.
Fix #105630