Fix wrapping of inline code within paragraphs
What does this MR do and why?
Fix wrapping of inline code within paragraphs
References
Screenshots or screen recordings
| Before | After |
|---|---|
 |
 |
How to set up and validate locally
- check out this branch
- in the GDK, edit markdown to have the following content:
Inline code example goes here at the end of this long sentence: `codecodecodecodecode`
`` [21:18:51]: Initializing match for GitLab project foobar/baz [21:19:00]: Couldn't find a valid code signing identity for development... creating one for you now +------------------+-------------------------------------------+ | Lane Context | +------------------+-------------------------------------------+ | DEFAULT_PLATFORM | ios | | PLATFORM_NAME | ios | | LANE_NAME | ios buildcicorp | | KEYCHAIN_PATH | ~/Library/Keychains/fastlane_tmp_keychain | +------------------+-------------------------------------------+ [21:19:00]: No code signing identity found and can not create a new one because you enabled `readonly` ``
`foo bar maz`
`foo `?
```
diff --git a/app/assets/stylesheets/framework/typography.scss b/app/assets/stylesheets/framework/typography.scss
index e536cd4f6c32..0ceabcca8b3a 100644
--- a/app/assets/stylesheets/framework/typography.scss
+++ b/app/assets/stylesheets/framework/typography.scss
@@ -25,7 +25,7 @@
> code {
font-weight: inherit;
- @apply gl-break-all gl-whitespace-break-spaces;
+ @apply gl-break-normal gl-whitespace-break-spaces;
}
}
```- You will see that the inline code elements that are inside paragraphs wrap appropriately, and the codefence is not affected by this MR's changes.
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Related to #561290 (closed)