Skip to content

Fixing issue where long, unbroken strings in resource name cell URLs breaks layout #1166

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 25, 2017

Conversation

rhamilto
Copy link
Member

@rhamilto rhamilto commented Jan 20, 2017

Fixes #1161

screen shot 2017-01-24 at 10 17 45 am
screen shot 2017-01-24 at 10 17 59 am
screen shot 2017-01-24 at 10 18 08 am
screen shot 2017-01-24 at 10 18 20 am
screen shot 2017-01-24 at 10 18 44 am
screen shot 2017-01-24 at 10 19 02 am
screen shot 2017-01-24 at 10 21 10 am
screen shot 2017-01-24 at 10 21 54 am
screen shot 2017-01-24 at 10 22 24 am
screen shot 2017-01-24 at 10 22 31 am
screen shot 2017-01-24 at 10 25 14 am

Plus bonus bug fix for Pods table where colspan was incorrect

screen shot 2017-01-23 at 4 24 22 pm

@jwforres or @spadgett, PTAL. cc: @sg00dwin

@spadgett
Copy link
Member

Should we apply the break-all styles to just the columns that need it? Some columns like status and relative times shouldn't need break-all.

@spadgett spadgett self-requested a review January 22, 2017 17:30
@spadgett spadgett self-assigned this Jan 22, 2017
@rhamilto
Copy link
Member Author

Should we apply the break-all styles to just the columns that need it? Some columns like status and relative times shouldn't need break-all.

@sg00dwin, I was following your lead on this fix. What do you think?

@sg00dwin
Copy link
Member

There is a .word-break-normal class that can be set on individual <td>, so we can isolate in those cases.

As for whether we should apply word-break-all by default... I assume it would depend on whether we think there's a greater risk of breaking content when it's not intended or not breaking long strings where needed. Either way we approach it, will require individual examination of a tables column content.

@spadgett
Copy link
Member

I feel like we have the default backwards: we should only apply the style to the few columns that need it, not the whole table. I'd rather add word-break-all to the td elements that need it and remove the class that adds it to the whole table.

@rhamilto
Copy link
Member Author

I switched the default to opt-in to word-break. PTAL @spadgett.

@rhamilto
Copy link
Member Author

@spadgett, changed so that all td, th elements in .table-layout-fixed get word-break by default.

@spadgett
Copy link
Member

I'm seeing at least one place (deployments page) where we have overlapping text, likely because we have a min-width on the column.

openshift_web_console

@spadgett
Copy link
Member

Suggest we give less width to "Last Build" and more to "Created."

We might want duration value and unit to wrap together. (Doesn't have to be in this PR, but noticed while testing.)

@jwforres We might have too many columns in some of our tables :/

openshift_web_console

@spadgett
Copy link
Member

We should consider updating build-config.html, deployment-config.html, deployment.html, and other-resources.html, too.

@rhamilto
Copy link
Member Author

I'm seeing at least one place (deployments page) where we have overlapping text, likely because we have a min-width on the column.

I think it should be better now.

Suggest we give less width to "Last Build" and more to "Created."

Done. And now we hide "Source" at small viewport sizes. And fixed the th wrapping issue by removing word-break for th elements.

We should consider updating build-config.html, deployment-config.html, deployment.html, and other-resources.html, too.

Done:

  • deployment.html
    screen shot 2017-01-24 at 2 44 46 pm
  • other-resources.html
    screen shot 2017-01-24 at 3 59 53 pm

Not done as I don't think it's necessary (am I overlooking something on these?):

  • build-config.html
    screen shot 2017-01-24 at 3 57 48 pm
  • deployment-config.html
    screen shot 2017-01-24 at 3 57 26 pm

Let's give this another whirl, @spadgett?

@spadgett
Copy link
Member

[merge]

@openshift-bot
Copy link

Evaluated for origin web console merge up to a8426d2

@openshift-bot
Copy link

openshift-bot commented Jan 25, 2017

Origin Web Console Merge Results: SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin_web_console/986/) (Base Commit: a506596)

@openshift-bot openshift-bot merged commit e202d9f into openshift:master Jan 25, 2017
@rhamilto rhamilto deleted the issue-1161 branch January 25, 2017 20:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Long, unbroken names in route table pushes rest of content off-screen
4 participants