When you go to the admin/content/comment/settings you are confronted with two collapsed fieldsets and not a clue what either one of them does until you click on it.
Pre-collapsed fieldsets should be for optional/advanced information only, and since these are the only fieldsets on that page, they should be expanded by default.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | consistent-fieldsets.patch | 19.23 KB | webchick |
| comment-settings.patch | 853 bytes | webchick |
Comments
Comment #1
webchickpatch.
Comment #2
webchickActually, filter.module's configure form does this too.
So I figured while I'm doing this, now seems like as good a time as any to standardize on some UI conventions surrounding fieldsets in the admin area.
This patch goes through each admin page and sets all fieldsets to collapsible but NOT collapsed by default. This way, users can see all of the settings available to them when they originally go to a settings page, but with a simple click can hide information that isn't relevant.
I'm happy to document this as well as a UI standard; the only thing is I'm not sure where to do so.
Comment #3
drummI'd like to consider these on a more case-by-case basis. And I think I've reviewed a similar patch to this.
Comment #4
drummPatches to fix pages with only collapsed fieldsets (like comment settings) are straightforward and probably the best place to start.
Comment #5
webchickOk cool. I'll mark this one as a dupe of http://drupal.org/node/30038 and roll separate patches for comment/filter settings.