so that we don't bother doing a reflow to 0,0

Setting all current Open/Normal to M4.

per leger, assigning QA contacts to all open bugs without QA contacts according to list at http://bugzilla.mozilla.org/describecomponents.cgi?product=Browser

I don't think anyone is dying for this in the next 36 hours. Moving to M5

Not making these for M5

Moving out to M7

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

Moving to m13 because Joki seems to be distracted.

Hey Joki, you lazy bastard, would you fix this f*cking bug that's been open since February... and its bug # is so damn low that I'm surprised that bugzilla even remembers it.

Moving M16.

Bulk prioritizing bugs for correct milestones.

This is mostly a performance issue, not a feature.

This bug has been marked "future" because the original netscape engineer working on this is over-burdened. If you feel this is an error, that you or another known resource will be working on this bug,or if it blocks your work in some way -- please attach your concern to the bug for reconsideration.

QA contact updated

Would this be contributing to why there's so much disk swapping going on in Windows when I restore a window from the taskbar?

I know Windows tells a program when it is being minimized and would think it is the same for other systems so wouldn't this essentially involve a cross-platform function to tell if being minimized and an if/then style conditional to skip reflow on minimize. However, at least on Windows, reflow will still need done on restore/maximize because it is possible to unminimize by doing a maximize instead of restore as well as possible to change resolution, etc.

reassign

This is the oldest NEW bug in the Browser. Has this been fixed? Does it even need to be fixed? I see a performance hit when I resize the window, but not when I minimize and restore to the same size. I think this is WFM for Win2K at least. -M

-> Current default owner/QA of this component. Looks like these netscape folks are gone.

Lemme go out on a limb here and mark this as wontfix. We're so good with our reflows now that we don't need to ignore a reflow when sizing to 0,0. If this is re-opened, I suggest that the severity be set to Enhancement.