Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Tatuya Kamada
gitlab-ce
Commits
eed6bfe2
Commit
eed6bfe2
authored
Jan 19, 2017
by
Eric Eastwood
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Remove rogue scrollbars for some issue comments
Fix
https://gitlab.com/gitlab-org/gitlab-ce/issues/25989
parent
1bb0191a
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
6 additions
and
2 deletions
+6
-2
app/assets/stylesheets/pages/notes.scss
app/assets/stylesheets/pages/notes.scss
+2
-2
changelogs/unreleased/25989-fix-rogue-scrollbars-on-comments.yml
...ogs/unreleased/25989-fix-rogue-scrollbars-on-comments.yml
+4
-0
No files found.
app/assets/stylesheets/pages/notes.scss
View file @
eed6bfe2
...
@@ -195,10 +195,10 @@ ul.notes {
...
@@ -195,10 +195,10 @@ ul.notes {
}
}
.note-body
{
.note-body
{
overflow
:
auto
;
overflow-x
:
auto
;
overflow-y
:
hidden
;
.note-text
{
.note-text
{
overflow
:
auto
;
word-wrap
:
break-word
;
word-wrap
:
break-word
;
@include
md-typography
;
@include
md-typography
;
// Reset ul style types since we're nested inside a ul already
// Reset ul style types since we're nested inside a ul already
...
...
changelogs/unreleased/25989-fix-rogue-scrollbars-on-comments.yml
0 → 100644
View file @
eed6bfe2
---
title
:
Remove rogue scrollbars for issue comments with inline elements
merge_request
:
author
:
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment