Closed Bug 130695 Opened 23 years ago Closed 18 years ago

Cached compose window not remembering the window size

Categories

(MailNews Core :: Composition, defect)

Product:
MailNews Core
Component:
Composition
Version:
1.0 Branch
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
minor

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME
Milestone:
mozilla1.1alpha

People

(Reporter: mgalli, Unassigned)

References

Details

(Keywords: regression)

When I click compose, the new window displays in full screen, not maximized mode, but resized to full screen. Does not matter if I resize,. in the next compose, I have the same problem. Tested with: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020311 PS:The new cached compose window is really fast.
Keywords: regression
Summary: Cached compose window not remembering the window size → Cached compose window not remembering the window size
Which flavor of Linux and which Windows manager are you using?
Blocks: 132191
I'm seeing this too, on RH 7.2 with KDE.
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla1.1alpha
Blocks: RememberPosition
duplicate of bug 113694?
QA Contact: sheelar → esther
Product: MailNews → Core
andrew, does this WFY on linux? (also, not sure if I set the version correct for that time period) seen recently on windows when starting with a corrupted or missing profile. But not under "normal" circumstances (In reply to comment #3) > duplicate of bug 113694? no - reporter copied localstore.rdf from win32 to linux - a dup of bug 66259?
Assignee: ducarroz → nobody
Severity: normal → minor
Status: ASSIGNED → NEW
QA Contact: esther → composition
Version: Trunk → 1.0 Branch
This worksforme with linux seamonkey trunk 20061007
=> WFM per comment 8 this is/was the last open blocker for both bug 132191 and bug 145941
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → WORKSFORME
Product: Core → MailNews Core

I was having the same problem on Thunderbird 68 series (currently 68.1.2 but is started with the first upgrade to 68) running on Windows 10 x64
Deleting localstore.rdf solved the issue here

You need to log in before you can comment on or make changes to this bug.