Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Long text not wrapped properly in modals

Description

I noticed an issue when I was testing but it turned out to be a global problem - it occurs for all error modals (this is especially visible when the error message contains stack trace), confirmation modals and others. Examples are the following:

  • The confirmation modal for processing schedules ("Do you want to save the Processing Schedule X?") breaks when one enters a very long processing schedule name without spaces (screenshot). With spaces, it works fine;

  • The same happens in the modal enabling one to add a processing period ("Add Processing Period for X schedule") when the processing schedule code is very long, with or without spaces;

  • The confirmation modal for processing periods ("Do you want to add the X Processing Period?") when the processing period's name is very long and without spaces; with spaces, it doesn't break.

Environment

None

Attachments

2

QAlity Plus - Test Management

Checklists

Activity

Joanna Szymańska 
January 2, 2019 at 10:12 AM

I checked again and now text wraps correctly.

Joanna Szymańska 
December 31, 2018 at 12:05 PM
(edited)

When I added processing schedule with a very long code or name, the text was displayed correctly. However, when I clicked the "Edit" button next to the newly created processing schedule with a very long code, the text didn't wrap properly.
Please take a look at the screenshot.

Mary Jo Kochendorfer 
December 17, 2018 at 11:23 PM

would be great to get this done.

Joanna Bebak 
November 15, 2018 at 9:44 AM

I checked, and the issue is still valid.

Nick Reid 
February 2, 2018 at 5:03 PM

If you are suggesting using overflow-wrao: break-work, it should work fine — I'd worry a little that no version of IE supports it (word-break:break-all has slightly better support)

I'd need to double check how select2 and our popovers work — but visually, I'd suggest we turn on overflow:hidden; in modals — as the example that Joanna showed is something we really want to discourage (long names like that don't do anyone any good).

If that specific period name was shown in a table.... it would just be gross all the way around — I would argue that breaking the word encourages unusable language, and will cause visual issue in many other parts of OpenLMIS-UI.

Done
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Labels

Story Points

Original estimate

Time tracking

6h logged

Components

Sprint

Fix versions

Priority

Parent

Time Assistant

Created January 23, 2018 at 12:32 PM
Updated November 22, 2020 at 2:09 PM
Resolved January 2, 2019 at 10:13 AM