Closed Bug 308298 Opened 19 years ago Closed 17 years ago

window sometimes does not redraw when FireFox maximized

Categories

(Core Graveyard :: GFX: Win32, defect)

1.7 Branch
x86
Windows 98
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: jure.sah, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Win98; sl-SI; rv:1.7.10) Gecko/20050717 Firefox/1.0.6
Build Identifier: Mozilla/5.0 (Windows; U; Win98; sl-SI; rv:1.7.10) Gecko/20050717 Firefox/1.0.6

Occasionally, when browsing with FireFox (and there are other applications that
use up a lot of memory running, cannot confirm this is related), the window
contens will not redraw (I see trough the window to what used to be under it) if
FireFox is maximized. If FireFox is not maximized but enlarged to full screen
the problem does not occur.

Reproducible: Sometimes

Steps to Reproduce:
1. Open FireFox
2. Open a memory-consuming application
3. Resize the FireFox window
4. Maximize FireFox

Actual Results:  
The window did not redraw, I could see parts of the desktop and the remains of
the unmaximized FireFox

Expected Results:  
Behaved as it would when FireFox is enlarged to fill the desktop

Windows 98SE
786 MB of RAM
Coppermine Celeron

Apps with which problem occured so far:
- Paint Shop Pro
- Winamp, modern skin
- ModPlug Tracker P3

No other apps are experiencing such problems as FireFox at the time.
Actually, upon second glance, ThunderBird appears to share this FireFoxes problem.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20050912
Firefox/1.6a1 ID:2005091221

Resized Firefox, opened 10x ieplore.exe (=216.000kB), no problem maximizing
Firefox, redrew instantly. 
Assignee: nobody → win32
Component: General → GFX: Win32
Product: Firefox → Core
QA Contact: general → ian
Version: unspecified → 1.7 Branch
Is this a problem with Firefox 1.5?
reporter mail address is dead
=> incomplete
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INCOMPLETE
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.