Closed Bug 76986 Opened 24 years ago Closed 24 years ago

Fizilla can't create menus more than 4 levels deep

Categories

(Core :: XUL, defect)

PowerPC
macOS
defect
Not set
minor

Tracking

()

RESOLVED INVALID
Future

People

(Reporter: lordpixel, Assigned: mikepinkerton)

Details

(Whiteboard: OSX)

Use the bookmarks menu in the personal toolbar (XPMenus). Go Mozilla Project->Technology Demonstration->Smart Find Queries->Bookmarks starting with 'M'->Mozilla Project ... ie, you can get an infinitely deep tree. Now try the same in the main menubar, with native menus. You can get 4 sub menus but no more. Are changes needed or is this a limitation for Mac OS 9 that's accidentally being used on Mac OS X also?
this is so trivial, it's almost not worth worrying about, but i think this restriction has been removed.
Target Milestone: --- → Future
Its still there in the 4/17 build I tried last night. Oh, or do you mean "the restriction was removed from the OS in Mac OS X" If its trivial to fix point me in the right direction and I'll do it. Sure its a pretty trivial problem, but you know how people get if they can't organise their bookmarks just the way *they* want them...
Whiteboard: OSX
I can't get an infinitely deep tree in the personal toolbar either. I don't this bug is reproducible any longer.
Clearly one could expose this bug - just use the bookmarks manager to make > 4 levels of nested folder in your bookmarks. Its not a question of infinitely deep trees, just trees with a depth greater than 4.
beard and i were able to repro this with current builds...i've fired off an email to apple asking about limitations. i don't see anything in the OSX menu code that restricts us like with os9. lordpixel, do you see anything?
from Eric Schlegel: > It's still 5 max (4 hierarchicals). I intend to remove that limit, but > more important things keep getting in the way.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
Component: XP Toolkit/Widgets: Menus → XUL
QA Contact: jrgmorrison → xptoolkit.widgets
You need to log in before you can comment on or make changes to this bug.