Unable to create a new folder (local or IMAP) Win32 release build, 1999-09-17-13-m11 1) Start Messenger 2) Select an IMAP account's Inbox and log in 3) File | New Folder 4) Enter a folder name and choose from the drop-down list to create a folder on the IMAP account you are logged into 5) Click OK in the new folder dialog Actual results: Dialog does not close and the folder is not created. In the DOS window, it reads: "JavaScript Error: uncaught exception: [Exception... "Component returned failure code: 0xc1f30001 <NS_ERROR_NOT_INITIALIZED> [nsIMessenger.NewFolder]" nsresult:"0xc1f30001 <NS_ERROR_NOT_INITIALIZED>" location: "JS frame :: chrome://messenger/content/widgetglue.js :: NewFolder :: line 365" data: no] Expected results: New folder should be created Notes: Same problem when I try to create a local folder

reassign to Seth after talking to him and David B.

I hate this. I cannot reproduce that JS error I received earlier. After further discussion with Seth, it turns out that the user must have the server selected in the folder pane for a new folder to be created. If the user has a folder selected in the folder pane prior to bringing up the New Folder dialog, the new folder will not get created. I'm going to turn this bug into tracking that case.

marking m11. going to look into this today.

jesus, the html select widget is a mess. this feature depends on the html select widget behaving. I'll go read the existing bugs, and log some more.

Nominate for dogfood

Dogfood bug. M12.

Actually, Lisa's comment is not 100% correct (the horror!) I suspect what she really means is that if you have the INBOX selected, and try to create a folder, it doesn't work because our IMAP server doesn't allow you to create a sub-folder of the inbox. If you have some other folder selected, creating a new sub-folder works just fine, at least on imap, for me. But the widget is pretty horked - it doesn't show you what folder you're creating a sub-folder of.

moving to 12/3, I won't be able to fix this for 11/17

So, I looked into this a bit and probably saw everything that Seth has already seen. Basically, when the html:select gets created from a XUL template it creates it like this: a b c d e f But only the top level items are selectable. Therefore we can only select a server and not a folder. Also since we are searching through the select to find a match for our preselected folder, we never find it because folders aren't at the top level. I'm not sure who on XP Widgets or RDF to ask about this, but would it be possible to make html:select's do correct indenting for child elements, but to also make the individually selectable?

Scott, what's the template in question look like? I'm guessing that the template is just adding a lot of <html:option> tags, one for each child node. Instead, you might try using <html:optgroup> tags for containers, and use <html:options> for leaf nodes. (See the HTML 4 spec for additional details.) [I have simple XUL file which uses optgroup and option tags, and I can individually select either.]

ok I'll look into that. thanks.

So, I tried this last night and there are a couple of problems. The first is that the optgroup is not selectable. According to the spec, disabled is implied. Also optgroups can't be nested in HTML4 which doesn't allow for subfolders. I don't suppose we could make optgroups selectable with a style rule and allow for nesting of optgroups? That would make this feature work.

Why not use a XUL popup with a tree widget in it? It wouldn't look exactly like a "select" box, but we could probably design the widget to look nice anyway, and it would give you all the features you need.

<menu> <titledbutton value="Fill in with selected item when one gets invoked. Style my image based on an attribute you can set on me when an item gets selected."/> <menupopup> <tree allowevents="true" onclick="...set the attribs on the titledbutton and close up the popup" etc.>...</tree> </menupopup> </menu> </menupopup>

Oh, a menupopup is a box, so you'll want to do all the usual tricks with divs etc., or you could just constrain the tree and menupopup to be the exact width and height you want.

Interesting. That is what I want. I'll see if I can get that to work. Thanks David.

Yeah, if you ever run into problems with <select>s, just remember that <menu>s can do everything <select>s can do plus a whole lot more... so if the former is acting up, try using the latter instead.

fixed. I took hyatt's advice and used menu's instead of selects. so much better now/

Wow! A lot progress!! At least I like this improvement!! Used today's build for single profile on both Linux 12-06-08-M12 & Window 12-06-09-M12 can see those improvement!! But I still need to wait for better build for Mac... I will test on Mac either later today or tomorrow...

Verified on Mac 12-07-08-M12 commercial build Can create a new sub-folder for IMAP & Local now. Mark as Verified!!