Adding an extra container to localize the horizontal scroll to the input file #17
Conversation
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Hi @gtribello
Hopefully this should help in having a better visualization for the problem we are talking in plumed/plumed2#1273. It is a workaround rather than a solution, because the text still exits the
<pre>borders, but at least the scrollbar now is localized to the box with the "Click on the labels of the actions for more information on what each action computes " and the plumed inputThe tootips are cut on the upper edge of the "Click on the labels of the actions for more information on what each action computes" text and on the lower part of the input file because of how the overflow kw works, the lower cut might be a lesser problem, since it looks like the pre element carves some extra space under itself.
If you do not want to use the extra div in any sub-project I think you can simply override its css rule and hopefully it will behave as it is not there