to see this: 1. go to Edit > Preferences... 2. look at the left pane in the Prefs, where the category tree is displayed 3. for the Composer category, there's a widget (dunno the name here --is called a "tree widget"?) to expand/collapse that category. 4. click on the tree widget expected: the tree widget implies that there are subcategories which should be displayed when toggling it to expand. result: the widget toggles back and forth, but there aren't any subcategories --only a pane (right side, o'course) which has a section for Author Name and another for Default Page Colors. if subcategories won't be added for beta1 (or post beta1), this widget should be removed so as to avoid potentially confusing users.

set target for M14 (beta1) for something to be done about this. :-)

oops --okay, i'm not the person to set the target milestone. my bad. :-)

clearing the milestone

reassign to myself the specification for prefs is not finalized yet

related to bug #17854

updated summary due to typo: there *shouldn't* be a tree widget if there's no subcategory.

change summary

Charley: do you have a list of the prefs we wanted to add? I remember these: * background image for new pages * table editing (maintain structure) I'd like to see the prefs divided based on "New page prefs" and "editing prefs" Author, Colors, and Image would be on the "new page" panel. Table Editing, helper apps (if we need to have these), autosave (if we do this?) and others on an "editing" panel. Suggestions for the names of these panels? Maybe the "editing" ones are the main Composer panel and "New Documents" is the other panel?

Check the newsgroup topic: "Composer Preferences" -- you've noted most of them. What about "Default for New Page"? I guess that depends on whether we will have a Netcenter wizard or New Page from Template. I would hope we could squeeze that into the "New Page" panel. As to titles, "Editing" is good, and maybe "New Page" (I think we should consistantly use "page" or "document", and our last decision on this was to use "page").

moving to M14 and adding keyword for beta1 Bij and I are going to work on the spec this week

*** Bug 27246 has been marked as a duplicate of this bug. ***

hmmm... for some reason my milestone change didn't take... try again

Putting on the PDT- radar for beta. This would be great to do by beta. But will not hold is not complete.

move to M15; Bij and I probably aren't going to be able to finalize these prefs by tomorrow

*** Bug 26901 has been marked as a duplicate of this bug. ***

remove 'beta1' keyword and PDT- from status whiteboard we can ship beta1 with preferences as they are

change summary to cover implementation now that the spec has been finalized.

updating keyword and status whiteboard to reflect that this is a beta 2 feature work bug that the Composer team deems a must fix for beta 2.

note: I have implementations for "Use Default Colors" and "Use Navigator Colors" in my tree for the Composer panel. Will land this weekend with the rest of the prefs widget conversion work.

nsbeta2+

I assume the prefs are finalized now

will verify after 38986 is fixed...

comes up very sluggishly ....verified in 5/19 build.