Open Bug 148892 Opened 22 years ago Updated 2 years ago

Clicking on link in mail loaded page in print preview

Categories

(Core :: Print Preview, defect, P3)

defect

Tracking

()

Future

People

(Reporter: mpatterson, Unassigned)

References

()

Details

In an e-mail message in mozilla's e-mail client I clicked on a link. I had a
print preview open, and the page loaded over the top of my print preview. The
browser page from which I had started the print preview was still showing the
original page, but the url in the navigation toolbar had changed to be the one I
had wanted to load from the e-mail message.
When I click on the mail link, the page appears in both the print preview window
and the main browser window.  I think that this is bad usage: the browser window
should load the link, but the print-preview window should keep the original page. 

Please change the component of this bug to "Print-Preview".
Status: UNCONFIRMED → NEW
Ever confirmed: true
.
Assignee: Matti → rods
Component: Browser-General → Print Preview
QA Contact: imajes-qa → sujay
Priority: -- → P3
Target Milestone: --- → Future
*** Bug 146720 has been marked as a duplicate of this bug. ***
As noted in bug 146720, trying to click on a link in mail while in print preview
mode in the browser now brings up a dialog saying "The document cannot change
while printing or print preview." Personally, I don't consider that an optimal
solution to the problem. ;-)
*** Bug 188395 has been marked as a duplicate of this bug. ***
Steve Chapel in comment #4:
> noted in bug 146720, trying to click on a link in mail while in print preview
> mode in the browser now brings up a dialog saying "The document cannot change
> while printing or print preview." ... I don't consider that an optimal solution 

in that case, don't you want to file new bug to have the modal behavior reversed and set to block this bug?
Assignee: rods → printing
OS: Windows 98 → All
QA Contact: sujay
Hardware: PC → All
Assignee: printing → nobody
QA Contact: printing
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.