I've recently been creating views using CVS version of Drupal and views, and have noticed that when I add fields to the view, if the field is rather large, the table row disappears under the DIV. I've included a screenshot from Firefox using the Web Developer extension to show what I mean.

I'm running at a resolution of 1024x768, and what it means is if I add a field and then want to remove it, I can't as the remove button is not viewable on the screen.

CommentFileSizeAuthor
screenshot_31.png62.26 KBtanepiper

Comments

karens’s picture

I've run into this, too, but it may be a core problem rather than anything Views can control. I tried changing the theme to the old standard Blue Marine and the same thing happened there. The problem becomes most obvious if you add CCK fields to the view because their names are so long.

I'd report it somewhere appropriate, but can't figure out where it belongs...

merlinofchaos’s picture

It just means that the fields section has outgrown the table format. I can't make it narrower. I just have to find some better way to display it. :/

karens’s picture

In 4.7 if the table got too big, it would pop out of its container so you could still see it, but that isn't happening in 5.0, so something in the core css has changed, maybe.

What about adding a views ui css and put 'overflow:visible' on the divs and tables?

karens’s picture

Did a little digging around to see what changed and I found the source of the problem, but I'm not sure what the fix is. The 5.0 version of the collapse.js is adding 'overflow:hidden' to collapsible fieldsets. The 4.7 version did not.

webernet’s picture

I opened a core issue about this a couple weeks ago: http://drupal.org/node/92849

karens’s picture

Status: Active » Fixed

I added some info to that issue and hopefully we are on our way to a fix in core. I think that overflow:hidden is the real problem, rather than the large table size, since you should never use overflow:hidden on anything that contains content because of accessibility issues. Even if the table was smaller, how could you ever be sure that someone wouldn't have their text size set too large or their viewing window too small to be able to see it.

I think this is something that needs to be fixed in core, not in Views, so I'm marking this fixed. I'm making it fixed instead of closed so it can be found by others having this problem.

Anonymous’s picture

Status: Fixed » Closed (fixed)