Fixes horizontal scrolling originating from <code> blocks. (in nixpkgs manual)
#205
+1
−0
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
See: https://twitter.com/kumbunterland/status/982638331757506567 The `<code>` blocks are normally expected to have a `white-space` property of `normal`, at least I assume docbook would expect the default. Bootstrap (2.3) changes it to nowrap, which isn't helpful for an inline type element.
samueldr
changed the title
<code> blocks.<code> blocks. (in nixpkgs manual)
|
LGTM |
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.
See: https://twitter.com/kumbunterland/status/982638331757506567
The
<code>blocks are normally expected to have awhite-spaceproperty of
normal, at least I assume docbook would expect thedefault. Bootstrap (2.3) changes it to nowrap, which isn't helpful for
an inline type element.
This is replaced only for the
docbookpages. If there is somewhere else<code>elements are used and exhibit the same issue, the rule can be expanded.Before
After
cc: @grahamc (in case graham's trying to fix it)