For me -konqueror user- the floats on the "admin groups" of the node edit forms was always annoying. The textfields were inaccessible.
But witth the collapsible parts they becme even moer annyoing: They now jump around on teh page when collapsed or folded out.

This patch simply removes all the floats frolm these groups.

I beleive theis looks and feels much better. It appears more stable on your page. It feels more like one expects: only a single row of collapses, instead of some odd row with columns.

And last but not least: that part was amoungst the hardests to theme. I think this is a good moment to get rid of them.

Oh, and it removes quite some code/cruft from drupal.css :)

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Bèr Kessels’s picture

FileSize
178.97 KB

here is an example of the jumping fieldsets: A complete set of screenshots can be found on my computer: http://webschuur.dyndns.org/DMP/collapsible/

Bèr Kessels’s picture

FileSize
13.07 KB

and here is how it looks with the patch.

Thox’s picture

This seems a fair temporary fix for Konqueror, although it will affect all browsers. In the long term we need to improve the layout of the form itself.

Bèr Kessels’s picture

AllthoughI presented it as a fix for myself and konqueror. I meant it as a fix in general. IMO the floated collapsed forms look and feel strange, on konqueror particularly, bu in firefox too. Having them underneath eachother is much nicer and friendlier. Worpress has that too: one collapse per line.

Bèr Kessels’s picture

This pathc still applies.
IMO we *really* do not ned floating elements with the current new collapsing form elements. So can someone please comment on this patch? If you think you really need the floating form elements, please tell why. And if you dont think you need it, please try and comment on this patch.

moshe weitzman’s picture

I like the compactness of the current approach ... If you feel that themers will not know how to override this, then please add some comments to drupal.css or elswhere.

Bèr Kessels’s picture

Status: Needs review » Reviewed & tested by the community
FileSize
53.75 KB

the curertn floats have not other reason to be there, then leftovers from teh pre-collapsible-era.
If we cannot do bettert then it is now, then at least removing the floats makes it all behave better.

See the att. screenshot: the comment options are "lost", they are hard to be found by a pesron scanning the UI.. The top-element does not fill out the full width (just looks ugly and inconsistent) and collapsing/uncollapsing makes this all behave even stranger.

moshe weitzman’s picture

not sure why your 'author' group is so wide. what browser are you using. try to reproduce in a different browser.

mine is compact and thus all the 3 groups fit nicely in 1 row.

maybe this patch is a good idea. i can't decide.

Bèr Kessels’s picture

I use konqueror. Inded it does not behave this strange for FF/moz, nor for IE6. But I remember that IE pre 6 had troubles with the floats too, Not sure how they do now, with the collapses.

Dries’s picture

Version: 4.6.0 »

This is about CVS, not 4.6.

chx’s picture

Component: base system » node system

Indeed it is about CVS, and should get in.

It is so very strange that we have three collapses in one row. Unless you are used to the old, non-collapsed node edit form, you'll feel this very strange. "I click on this, in the middle of nothing I can see a wad of options... what??"

One collapse per row is better.

Dries’s picture

Shouldn't we clean up the generated HTML a bit too? If the node edit form becomes a 'standard form', we don't have to generate a bunch of CSS-tags. (This is also something the form API will take care of in future so it doesn't hurt to remove the extra tags for now.)

Bèr Kessels’s picture

The patch still applies.

An Dries: No. I think it is not a good idea to remove the CSS classes.
The fact that we offer a decent default does not mean others (Read Chris ;) ) will not make nicer looking and better forms *for certain uses*. I, for example have one site where I style my forum editing pages different from the node/add etc.

I beleive that, untill we have that node wrapper in core, we should certainly not remove classes and IDs.

moshe weitzman’s picture

i withdraw my earlier hesitancy about this patch. is a good idea.

Dries’s picture

Status: Reviewed & tested by the community » Fixed

Committed to HEAD. Thanks.

Anonymous’s picture

Anonymous’s picture

Anonymous’s picture

Status: Fixed » Closed (fixed)