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?
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | 372217-1.patch | 1.23 KB | les lim |
Comments
Comment #1
sheise commentedComment #2
les limThis 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).
Comment #3
les limComment #4
nicholas.alipaz commentedpatch works great! Please commit!!!
Comment #5
ergophobe commentedConfirming 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).
Comment #6
rsvelko commentedYes - 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
Comment #7
quicksketchThanks 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.