Closed
Bug 96475
Opened 23 years ago
Closed 23 years ago
Maximized state not preserved
Categories
(Core :: XUL, defect)
Tracking
()
RESOLVED
FIXED
mozilla0.9.5
People
(Reporter: coen, Assigned: danm.moz)
References
Details
Attachments
(2 files)
385 bytes,
text/html
|
Details | |
2.53 KB,
patch
|
Details | Diff | Splinter Review |
1: Maximize browser window 2: Choose a link with target="_blank" 3: New window opens, but isn't maximized. expected: A new maximized browser window
Sorry, build = 2001082203 In 2001082111 the problem didn't exist
XP I think. Problem still there in 2001082403
Component: Browser-General → XP Toolkit/Widgets
Don't think so. This problem first occurred in Aug. 21 builds.
Comment 6•23 years ago
|
||
->XP Apps
Assignee: asa → pchen
Component: XP Toolkit/Widgets → XP Apps
QA Contact: doronr → sairuh
Updated•23 years ago
|
QA Contact: sairuh → claudius
Comment 7•23 years ago
|
||
confirmed with 2001082803 build on Win98 - does not seem to be a problem with a 2001082808 linux build
Assignee: pchen → trudelle
Status: UNCONFIRMED → NEW
Component: XP Apps → XP Toolkit/Widgets
Ever confirmed: true
QA Contact: claudius → jrgm
Comment 8•23 years ago
|
||
See also related bug 96393 -- "Some localstore.rdf persistence is broken (post 8/17)"
Assignee | ||
Comment 10•23 years ago
|
||
Hmph. Someone must have altered initial window visibility, and the window's zoom state was dependent on its visibility. That's no longer necessary, since all widgets have had to learn how to not act on zoom state until they're visible anyway. The patch below removes this dependence and fixes this bug.
Assignee | ||
Comment 11•23 years ago
|
||
Assignee | ||
Comment 12•23 years ago
|
||
.
Reporter | ||
Comment 13•23 years ago
|
||
Is it possible to check this in, in the 0.9.4 branch ? The problem is highly visible.
Assignee | ||
Comment 14•23 years ago
|
||
That question has been forwarded to the 0.9.4 authorities. Note to self and authorities: if this patch is copied to the branch, also included should be the patch for bug 98701, which was caused by this checkin.
Comment 15•23 years ago
|
||
*** Bug 99017 has been marked as a duplicate of this bug. ***
You need to log in
before you can comment on or make changes to this bug.
Description
•