"XUL-based specification of size,title, resizability, modality." 3 days danm 0% "Add support for a XUL-based specification of size, title, resizability, modality...."

Mass changing all XPToolkit M9 feature 'bugs' to target as p2 for M9

Mass changing all M9 feature 'bugs' to 'enhancement severity.

(Added close, min and max widgets, and removed size and title, which are already done.)

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

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

9327 was closed as a dup of this, and that bug was a prerequisite for 7146. Does the fix(es) sort of referenced here include the capability to fix 7146, too?

No, the changes envisioned to close this bug don't plan to address bug 7146.

I think this should be closed out. We don't need to be putting all of this on the XUL window tag. People can just do it on window.open.

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

code level fix, marking verified. reopen if i'm wrong here...

This stuff is verifiable by playing with the "features" argument in a call to JavaScript window.open(). There's a fairly complete test case for trying out combinations of these things in resource:/res/samples/dexopenchrome.xul .

Bug #9327 was closed as a duplicate of this one. Bug #7146 was made dependent on that one. Unfortunately, this feature does nothing to fix bug #7146. I need another feature flag (or something) to suppress certain dialogs getting added to the Windows task bar. Maybe "dependent=yes" will do the trick? The find dialog might could be made dependent on its "parent" browser window.

Clearing Fixed resolution due to reopen.

clearing target milestone so dan can reconsider this

Well, OK. I've considered it and decided that since the "dependent" flag keeps the associated window out of the window list, then if you don't mind using that flag, we're done. Note that currently, this is platform-specific behaviour. On Windows, dependent windows aren't mentioned in the taskbar. On Linux, they are. However, on my machine, Nav 4 behaves the same way (though I think I saw it behave differently on another box using a different window manager.) So this is a rather ill-defined bug. Does "dependent" work for you, Bill? Are we there yet?

Not getting much action. Bounce.

Sorry, this isn't my top priority so I haven't tried using "dependent=yes" for the find dialog yet. I'll do it soon, promise!

Targetting M11 so this puppy has a home.

dependent=yes works, marking FIXED.

marking verified