Closed (fixed)
Project:
Drupal core
Version:
6.x-dev
Component:
menu system
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
25 Nov 2007 at 05:51 UTC
Updated:
22 Jan 2008 at 11:34 UTC
Jump to comment: Most recent file
Comments
Comment #1
Rowanw commentedComment #2
senpai commentedWorks as advertised, with no ill effects. Before I RTBC, I wanted to ask the Collective if disabling the Expanded checkbox for menu items who have no children would be a good idea.
We could do this at drupal_render time by checking for the existence of child elements, and setting the checkbox to 'disabled' inside the theme function so that it can be overridden by designers if necessary. Good idea, or bad idea?
Comment #3
Crell commented-1 to removing the "expand" checkbox if a menu item has no children. Just because it doesn't now doesn't mean it won't have them added in the course of using the site. I may want to set up menus that should expand once content gets added. I don't want to have to come back and set it again.
Comment #4
Rowanw commentedDitto for #3, that was the whole reason I made the change.
Comment #5
senpai commentedI wasn't referring to removing the 'expanded' checkboxes, but merely disabling them if the menu item doesn't have any children. Ok then. No support for that idea.
Since that doesn't fly, how about moving the 'enabled' column to position #1? It makes a LOT of sense from a user interface perspective that if the first column is a known width then we could have the two most important things on the page, the 'enabled' boxes and the 'draggable' icons, right next to each other. Yeah?
Comment #6
Crell commentedMight that be confusing for the DnD functionality? You'd have an extra checkbox sitting between you and the label you're targeting for the drop-target.
Comment #7
senpai commentedHmmm, possibly, but probably not. I might just do this and see how it looks. I'm betting that with the proper theming, it won't be bad at all. Functional is the point here, after all.
Comment #8
Rowanw commentedUpdated patch to latest release (had 2 lines offset).
I tried Senpai's idea to put the enabled column first, but since it sits between the move icons and the menu names it looks quite confusing, see attached PNG. If the checkbox was before the move icon it might look a little better, but that opens up inconsistencies with other D&D areas within Drupal. For this reason I think the columns should stay as they are in the current patch.
Patch summary again:
Comment #9
scoutbaker commentedWhile, in theory, I like the idea of having the Enabled column first, I agree with Rowanw that it looks a little odd from a usability perspective. It's easier for me to visualize what I'm moving when the Enabled column is second.
Comment #10
pancho+1 The patch in #8 seems to be good.
I wouldn't move the enabled checkbox to the front either. Aside from D'n'D drawbacks this would also imply, disabled menu items wouldn't play any role, which is not the case.
Comment #11
Rowanw commentedRTBC?
Comment #12
gábor hojtsyCommitted, thanks.
Comment #13
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.