I've seen Vertical Tabs used incorrectly in a lot of places, but Nodewords' usage really takes the cake. The purpose of Vertical Tabs is to do the following (I know you've probably heard it before, but here we are again):
- Collapse infrequently changed options, usually ones that a user will see frequently (such as when creating a node) that don't need to be changed each time.
- Provide a summary of the contents of each group so the user doesn't need to open each tab to verify its contents.
- Each tab is intended to be a short form that can be viewed without scrolling, so the user can quickly tab through each one if necessary.
Nodewords literally gets ALL of these points wrong.
- It uses Vertical Tabs on the *unique* settings page. There's no way the user will know what's inside of these tabs because they'll only use the form once.
- There's no summary provided at all for any tab.
- And finally, the form is so long inside of each tab, that you have to click on a tab, scroll down, then when you finish the tabs have moved outside the browser window so you have to scroll back up, click the next tab, then scroll down again. Then you have scroll up again to click the next tab, then scroll down again! If you want to check all of your settings, you'll likely scroll up and down the main Nodewords setting page (admin/content/nodewords) 5 or 6 times.
Vertical Tabs are not a global substitute for fieldsets and they are not always an immediate improvement. Nodewords use of Vertical Tabs on its settings page actually makes the module harder to use. Patches forthcoming.
Comments
Comment #1
dave reidNot going to disagree at all. We should likely just remove the vertical tabs after 6.x-1.12.
Comment #2
quicksketchI'm going to merge this request with #950716: Combine similar tables on the admin/content/nodewords settings page..