Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
The operations table looks to small, as agreed upon by Leisa this needs to be larger. Depending on the implementation this can be done as a whole, or on a per table setting.
Comments
Comment #1
Bojhan CreditAttribution: Bojhan commentedTags
Comment #2
Stefan Nagtegaal CreditAttribution: Stefan Nagtegaal commentedWe can make all the white space from the links, inside the operations columns white-space: no-wrap;, right?
This would imo deal with the problems described here.
Comment #3
Bojhan CreditAttribution: Bojhan commentedCould you provide a screenshot, with your solution?
Comment #4
Stefan Nagtegaal CreditAttribution: Stefan Nagtegaal commentedNope, this requires a core patch which adds a class to the operations columns.
And, I'm currently busy with other things than this.. Sorry, I was just jumping in to give some advise.
This isn't that hard you know...
Comment #5
Gábor HojtsyI've been doing "research" and trying to summarize where operations columns are used and how different their role are: providing primary actions (on taxonomy vocabulary tables for example) vs. on the side related information (on the watchdog tables for example). I think we cannot possibly have a general solution for this but this needs to be considered on a page per page basis. My analysis is here: http://drupal.org/node/484860#comment-1865232
Comment #6
Bojhan CreditAttribution: Bojhan commentedMoving to the approiate component.
Comment #7
Jeff Burnz CreditAttribution: Jeff Burnz commentedIf this is still relevant in some way, which I doubt, you know the drill.