Currently the field area height is automatically set for all of your field areas to be the height of the maximum area in your set. But if you have one very large area with lots of fields then other sets which are very short, on the shorter ones you are left with large amounts of blank space which have to be scrolled through to get all the way to the bottom of the screen to save the node. Can this be replaced with an auto height?

CommentFileSizeAuthor
#2 372217-1.patch1.23 KBles lim

Comments

sheise’s picture

sheise commented
Title: Field are height problem » Field area height problem
les lim’s picture

les lim
he/they
Primary language English
commented
Assigned: Unassigned » les lim
StatusFileSize
new 372217-1.patch1.23 KB

This should do it. I'm able to test it on a PC using FF3, Safari 3, IE7 and IE6 (although I'd especially appreciate it if someone with "real" IE6 could verify that it works).

les lim’s picture

les lim
he/they
Primary language English
commented
Version: 6.x-1.0-beta1 » 6.x-1.x-dev
Status: Active » Needs review
nicholas.alipaz’s picture

nicholas.alipaz commented
Status: Needs review » Reviewed & tested by the community

patch works great! Please commit!!!

ergophobe’s picture

ergophobe commented

Confirming that this works for me too. Tested in FF3, IE7, Chrome 1.0.

Perfect in all cases (some very long and some very short fieldsets).

rsvelko’s picture

rsvelko commented
Title: Field area height problem » Field area height problem - when multi CCK field "add another" used

Yes - this fixed it - 10x.

Please commit.

Can we do sth similar about that similar issue with vocabs? #392212: Multiple Vocabularies/Taxonomy forces tabs down covering save/preview buttons

quicksketch’s picture

quicksketch
he/him
commented
Status: Reviewed & tested by the community » Fixed

Thanks everyone. I've committed the suggested changes thanks to the input here. In the next version of Vertical Tabs, we should use the much better approach kkaefer came up with for the Vertical tabs in core issue.

Status: Fixed » Closed (fixed)

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