See screenshot, this could well be considered a core issue, but can be themed away quite easily with a number of approaches, either a percentage width or width set based on active sidebars:

vertical-tabs-menu-input.png

CommentFileSizeAuthor
#9 60-col-inputs-833184_2.patch561 bytesJeff Burnz
#8 60-col-inputs-833184.patch500 bytesJeff Burnz
#7 node-add-poll.png24.01 KBJeff Burnz
vertical-tabs-menu-input.png17.45 KBJeff Burnz

Comments

Jeff Burnz’s picture

Jeff Burnz commented
Title: Vertical tabs menu input forces the fieldset too wide when 2 sidebars are enabled » Vertical tabs 60 col inputs forces the fieldset too wide when 2 sidebars are enabled

Note this actually happens for all the inputs that have size="60" in any vertical tab.

bleen’s picture

bleen commented

Related: #748570: Subject line in comment form is too long with both sidebars (no time to reread that issue right now ... but I think its the right one)

Jeff Burnz’s picture

Jeff Burnz commented

@bleen18 - yeah, in effect it is the same issue, both fields have size="60", I think this one is worse since it really smashes the visual display of the vertical tab, it really should be critical in terms of visual display brokenness.

jensimmons’s picture

jensimmons commented
Project: Bartik » Drupal core
Version: 7.x-1.x-dev » 7.x-dev
Component: User interface » Bartik theme
Priority: Normal » Minor
Jeff Burnz’s picture

Jeff Burnz commented
Title: Vertical tabs 60 col inputs forces the fieldset too wide when 2 sidebars are enabled » 60 col fields can overflow the main content column
Priority: Minor » Normal

We need to double check this.

bleen’s picture

bleen commented

still a problem when Bartik is the admin theme:

Only local images are allowed.

Jeff Burnz’s picture

Jeff Burnz commented
StatusFileSize
new node-add-poll.png24.01 KB

Doesn't even have to be set as the admin theme - allowing end users to add content is just par-for-the-course of a Drupal site - for example adding a poll...

node-add-poll.png

Jeff Burnz’s picture

Jeff Burnz commented
Status: Active » Needs review
StatusFileSize
new 60-col-inputs-833184.patch500 bytes

Give this a crack with some CSS3...

Jeff Burnz’s picture

Jeff Burnz commented
StatusFileSize
new 60-col-inputs-833184_2.patch561 bytes

Grrr, forgot about the poll fields, they have some knarly powerful selector applying width auto (nice how core loves to screw you over isn't it?).

BTW I havent test this a hell of a lot, trying to get the ball rolling here, we really need to start closing out some of these minor issues fast...

bleen’s picture

bleen commented

CSS3 awesomeness ... what do we do about non-css3 happy browsers?

Only local images are allowed.

Status: Needs review » Needs work

The last submitted patch, 60-col-inputs-833184_2.patch, failed testing.

Jeff Burnz’s picture

Jeff Burnz commented

That would be IE6 - frankly the UX in IE6 is just so bad in D7 that I would imagine people will be upgrading to Firefox in a heartbeat or running a mile... this doesnt look so hot in IE7 for the poll fields, but then again they don't look very good to begin (I think they're no worse off) with and at least with this they are actually usable.

I tested in a few browsers such as Opera, IE8 and FF and all seems good.

I think the bot is freaking out at the moment, I'm seeing failed patches like this everywhere...

Jeff Burnz’s picture

Jeff Burnz commented
Status: Needs work » Needs review

#9: 60-col-inputs-833184_2.patch queued for re-testing.

amateescu’s picture

amateescu commented
Status: Needs review » Fixed

This is fixed in D7.0.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.