Closed
      
        Bug 82804
      
      
        Opened 24 years ago
          Closed 24 years ago
      
        
    
  
window state not persistent in -turbo mode
Categories
(Core Graveyard :: Cmd-line Features, defect, P1)
Tracking
(Not tracked)
        VERIFIED
        FIXED
        
    
  
        
            mozilla0.9.2
        
    
  
People
(Reporter: bugzilla3, Assigned: law)
References
Details
(Whiteboard: free (with fix for bug 81712))
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9+) Gecko/20010524
BuildID:    2001052420
First browser window is always not maximised, even if I had maximised it in the
previous session. 
Reproducible: Always
Steps to Reproduce:
1. run "mozilla.exe -turbo"
2. Open the browser and maximise its window.
3. Close browser ("x" button) and re-open it
Actual Results:  Browser window isn't maximised. Size is the same as when
opening link in a new window (it also doesn't remember maximised state, since
the landing of turbo mode).
Expected Results:  Browser should remember maximised state
|   | ||
| Updated•24 years ago
           | 
QA Contact: sairuh → paw
verified it's not remembering browser window size on next launch when in -turbo 
mode.
|   | ||
| Comment 2•24 years ago
           | ||
Not sure if related, but since this has landed I've found that *on occasion*
right-clicking a link and opening it in a new window opens the new window in a
non-maximized state as well.  I always browse with maximized windows and
sometimes it works, sometimes not.  Hard to specifically reproduce.  Win2k,
nightly builds.
Summary: -turbo mode: first browser window can't be maximised → window state not persistent in -turbo mode
need this for -turbo
set target milestone 0.9.2
Target Milestone: --- → mozilla0.9.2
See comments under bug 81712.  The suggested fix there will take care of this 
problem as well.
Whiteboard: free (with fix for bug 81712)
Fixed by patch for bug 81712.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
          You need to log in
          before you can comment on or make changes to this bug.
        
Description
•