Closed
Bug 68699
Opened 23 years ago
Closed 13 years ago
Attached images loaded in wrong browser window
Categories
(SeaMonkey :: MailNews: Message Display, defect)
SeaMonkey
MailNews: Message Display
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: BenB, Unassigned)
References
Details
(Keywords: regression, Whiteboard: [SmBugEvent])
Regression. From bug 45225: ------- Additional Comments From Ben Bucksch 2001-02-13 08:40 ------- > That might cause the cotnent to get loaded in a browser window where the > user can click save if they want to save it. Sorry for objecting that late, but I had to see it. This is unfortunate. I tried to save a png (called sample.png in the mail), but it loaded in a small pop-browser window. After I realized what happened (most users won't even get that far), I tried to save it via content menu, and the name |foldnername>number|, e.g. |INBOX>5|, has been suggested. Summary of problems: - Wrong browser window chosen (small pop-up window) - No option to control the load, e.g. target a *new* browser window - Wrong default filename [Might be bug 68682] Should I file new a bug or reopen? ------- Additional Comments From Ben Bucksch 2001-02-13 09:02 ------- > - Wrong browser window chosen (small pop-up window) On the next try, it chose this very window where I am typing now, i.e. it nearly caused my comment to be lost. Personally, I don't know why we load in existing windows at all. IMO, we should *always* load in new windows, everywhere (e.g. clicking on links in Mailnews). But maybe that's just subjective. In any case, I need the *option* (in a comfortable way) to load in a new browser window.
Reporter | ||
Updated•23 years ago
|
Keywords: mozilla0.9,
regression
QA Contact: esther → fenella
Comment 1•23 years ago
|
||
> IMO, we should *always* load in new windows, everywhere (e.g. clicking on
> links in Mailnews).
I agree, "reusing" windows is evil and causes dataloss.
QA Contact: trix → stephend
Updated•20 years ago
|
Product: Browser → Seamonkey
Updated•16 years ago
|
Assignee: mscott → nobody
Updated•16 years ago
|
QA Contact: stephend → message-display
Comment 4•15 years ago
|
||
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
Comment 5•15 years ago
|
||
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Comment 6•15 years ago
|
||
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Comment 7•15 years ago
|
||
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Comment 8•15 years ago
|
||
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Comment 9•15 years ago
|
||
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Comment 10•14 years ago
|
||
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago. Because of this, we're resolving the bug as EXPIRED. If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component. Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → EXPIRED
Reporter | ||
Comment 11•14 years ago
|
||
Does it still exist in Seamonkey? (no problem in TB/FF)
Status: RESOLVED → UNCONFIRMED
Resolution: EXPIRED → ---
Comment 12•13 years ago
|
||
> Does it still exist in Seamonkey? (no problem in TB/FF)
Can't reproduce.=>WORKSFORME
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago → 13 years ago
Resolution: --- → WORKSFORME
Whiteboard: [SmBugEvent]
You need to log in
before you can comment on or make changes to this bug.
Description
•