Allow patch notes on tags page to word wrap (!20135) · Merge Requests · GitLab.org / GitLab

Allow patch notes on tags page to word wrap

What does this MR do?

This MR does the following to a project's tags view page:

Allows the patch notes text to line wrap.
Reduces the whitespace between the patch notes and the action buttons to make better use of the available space.

Note that this change only affects the tags list view:

http://localhost:3000/<user>/<project>/-/tags

but does not affect the individual tag view:

http://localhost:3000/<user>/<project>/-/tags/<tagname>

Screenshots

Before (text gets cut off, excessive whitespace between text and buttons)	After

Does this MR meet the acceptance criteria?

Yes

Conformity

Changelog entry
[-] NOT REQUIRED Documentation (if required)
Code review guidelines
Merge request performance guidelines
Style guides
[-] NO DB CHANGES Database guides
[-] NO SEPARATION NEEDED Separation of EE specific content

Availability and Testing

CSS only change, minimal risk to product. Cross-browsing testing required.

[-] CSS ONLY Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
Tested in all supported browsers

Security

No security-related changes.

Closes #33482 (closed)

## What does this MR do?

This MR does the following to a project's tags view page:

1. Allows the patch notes text to line wrap.
2. Reduces the whitespace between the patch notes and the action buttons to make better use of the available space.

Note that this change only affects the tags list view:

`http://localhost:3000/<user>/<project>/-/tags`

but does not affect the individual tag view:

`http://localhost:3000/<user>/<project>/-/tags/<tagname>`

## Screenshots

| Before (text gets cut off, excessive whitespace between text and buttons) | After |
| ------ | ------ |
| ![Selection_001](/uploads/6278346bdd0690f5b4005f6d638d21c1/Selection_001.png) | ![Selection_002](/uploads/5e63665fafeaf5137fe4b2d6e71941cd/Selection_002.png) |

## Does this MR meet the acceptance criteria?

Yes

### Conformity

- [x] [Changelog entry](https://docs.gitlab.com/ee/development/changelog.html) 
- [-] **NOT REQUIRED** [Documentation](https://docs.gitlab.com/ee/development/documentation/workflow.html) ([if required](https://docs.gitlab.com/ee/development/documentation/workflow.html#when-documentation-is-required))
- [x] [Code review guidelines](https://docs.gitlab.com/ee/development/code_review.html)
- [x] [Merge request performance guidelines](https://docs.gitlab.com/ee/development/merge_request_performance_guidelines.html)
- [x] [Style guides](https://gitlab.com/gitlab-org/gitlab-ee/blob/master/doc/development/contributing/style_guides.md)
- [-] **NO DB CHANGES** [Database guides](https://docs.gitlab.com/ee/development/README.html#database-guides)
- [-] **NO SEPARATION NEEDED** [Separation of EE specific content](https://docs.gitlab.com/ee/development/ee_features.html#separation-of-ee-code)

### Availability and Testing

CSS only change, minimal risk to product. Cross-browsing testing required.

- [-] **CSS ONLY** [Review and add/update tests for this feature/bug](https://docs.gitlab.com/ee/development/testing_guide/index.html). Consider [all test levels](https://docs.gitlab.com/ee/development/testing_guide/testing_levels.html). See the [Test Planning Process](https://about.gitlab.com/handbook/engineering/quality/test-engineering).
- [x] [Tested in all supported browsers](https://docs.gitlab.com/ee/install/requirements.html#supported-web-browsers)

### Security

No security-related changes.

Closes #33482

Edited Nov 25, 2019 by Daniel Tian