Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Problem/Motivation:
Currently the "meta" fieldsets on the node form are kept open when you open another one. In the extreme, you could come to a situation like this:
They should be open only one at a time. The current beavior is basically Drupal 6 and something that was meant to be moved away from: fieldsets that open and stack upon the other.
Since the seperating titles are not very strong as seperators, the situation becomes hard to handle if you open more than one fieldset. One has a hard time to seperate the fieldsets visually, which is worse because they have a grey background and tend to become one block.
It is an issue similar to #2009930: Do not keep meta fields of node form open when they have a value, even though this applies more to the meta fieldsets itself and not the balance with the contend edit part.
Personally, I find it hard to fucus on the thing I just wanted to edit.
I think there was a plan to implement accordion behavior here which should not be too hard technically. Because the open fieldsets have a darker background than the closed ones, this fact could then be used to keep focus of the currently open fieldset.
Proposes Solution:
Implement Accordion behavior.
| Comment | File | Size | Author |
|---|---|---|---|
| accordion-meta-fieldsets.png | 120.87 KB | eigentor |
Comments
Comment #1
klonosI think that this is a matter of personal preference. If we have it one way, people that like it the other way will complain (count me as one of them - I prefer these fieldsets expanded so I can preview changes in one sweep before saving*). I believe that no matter which is chosen as the default for core after all, it would be best to have this be optional with a setting someplace or a contrib module perhaps.
* with the vertical tabs in D7 we had the ability to see a summary of the settings as a hint along with the tab label. Now that we've switched to fieldsets, this "overview in a glimpse" feature is gone :/
Comment #2
klonosThese kind of issues are what make me push for #1273344: Establish heuristics for core feature evaluation / #1439316: Provide means for module maintainers to collect heuristics on certain settings of their modules. / #1274766: Collect stats on enabled sub-modules, not just projects / #1036780: Drupal.org should collect stats on enabled sub-modules and core modules so that we can come to better conclusions when it comes to deciding what would be the best for default. That way we could have metrics gathered and if more people seem to turn a certain setting/feature/module on or off, then in a next release we switch the default to what most people want and expect out of the box.
Comment #3
eigentor CreditAttribution: eigentor commentedGood point, Klonos. So how would I collect heuristics before the core release? I think you definitely got a point for a solid and longer-term solution, but fine-tuning and evaluation of the new node form somehow fell of the radar.
Comment #4
yannickooComment #5
klonos@eigentor, #3: Sorry Thomas, this one fell completely out of my radar...
Changing the default of a certain setting does not imply any API change, so I guess it can happen post-release.