If you install any module that has more than one word in its title, the name column of admin/build/modules will wrap ugly (see attached screenshot). The attached patch (followup comment) a) adds CSS classes to all columns in that table, b) tweaks Garland to force the Name column to 125 pixels wide.

CommentFileSizeAuthor
#2 _107705_modules_table.patch1.56 KBmorbus iff
#1 _modules_table.patch1.6 KBmorbus iff
wordwrap.jpg105.75 KBmorbus iff

Comments

morbus iff’s picture

morbus iff
they/them
commented
Status: Active » Needs review
StatusFileSize
new _modules_table.patch1.6 KB

The previous behavior of Garland was to force the description table column to 100% (which seems evil to me, but I'm no CSS mastah). This patch removes that and adds a width to the Name column, letting everything else render as the browser sees fit.

morbus iff’s picture

morbus iff
they/them
commented
StatusFileSize
new _107705_modules_table.patch1.56 KB

After installing some more popular modules, like CCK, Views, and ConTemplate, this mix of 20/80 worked better.

morbus iff’s picture

morbus iff
they/them
commented
Assigned: Unassigned » morbus iff
webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented
Status: Needs review » Reviewed & tested by the community

Still applies with offset.

Looks good to me. I had to ask Morbus to clarify what this does, and basically...

When your window is shrunk down very small, and you gradually expand it, before the patch it would only expand the "description" field... now it also expands the name field, so multi-word module names ("project issue tracker" on my install) will not wrap quite so much.

+1.

Steven’s picture

Steven commented

If we want to avoid wrapping, why not set nowrap?

morbus iff’s picture

morbus iff
they/them
commented

We want the ability to let screen width determine the wrapping for elements, not "don't allow wrapping evah". The display of text on a site should be as malleable as possible based on a resizing window - allowing only one element to wrap (what this patch fixes) or disallowing wrap at all (what you suggest) is bad form. While I could certainly see some benefit in forcing Name not to wrap, I can equally see myself complaining about how 10 lines of description looks like ass when I happen to have my window set to 750px wide (which, yes, I occasionally do when I'm reading).

Steven’s picture

Steven commented

But the page looks a lot neater if module names are always next to the checkbox :P. It is the primary column in the table after all.

morbus iff’s picture

morbus iff
they/them
commented

So, you'd advocate a patch that a) gave all the columns class names (as the previous patch did), b) set nowrap on the 'name' column and c) ???. c) could be either leave description at 100% (as before) or don't give it a width at all, and let the browser figure it out (potentially causing odd displays with Version and Throttle columns).

drumm’s picture

drumm
he/him
Location NY, US
commented
Version: 5.x-dev » 6.x-dev
moshe weitzman’s picture

moshe weitzman commented

dunno if is related, but this page shows empty module list in Safari right now.

dww’s picture

dww
we/he/they
commented

@moshe: no, that's a separate bug, and is specific to jQuery badness: http://drupal.org/node/134307

morbus iff’s picture

morbus iff
they/them
commented
Status: Reviewed & tested by the community » Needs work

Steven's comments in #8 need to be addressed.

jody lynn’s picture

jody lynn
she/her
Primary language English
commented
Version: 6.x-dev » 7.x-dev
sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Version: 7.x-dev » 8.x-dev

This might be part of #1790280: Module page redesign 2.0 already, but not sure.

mgifford’s picture

mgifford
he/him
Primary language English
commented
Assigned: morbus iff » Unassigned
Issue summary: View changes

I kinda assume this has been fixed as part of the responsive theming work that has been done. Not sure though.

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

quietone’s picture

quietone commented
Version: 8.9.x-dev » 7.x-dev
Issue tags: +Bug Smash Initiative

I tested this on a standard install of drupal 7.79-dev and Drupal 8.9.0 by navigating to /admin/modules

On Drupal 8.9.0 the modules of more than one word do not wrap but some do on Drupal 7.

Therefor, moving to the Drupal 7 issue queue.

Status: Needs work » Closed (outdated)

Automatically closed because Drupal 7 security and bugfix support has ended as of 5 January 2025. If the issue verifiably applies to later versions, please reopen with details and update the version.