How can I stop the popup blocker message from appearing that defeats printing an e-mail?
COMPUTER SETUP A new printer has been installed on my laptop computer. It’s a Brother Laserjet, Model No. HL-2240 running under MS Windows 7. The computer user applications include the Yahoo home page running within a Firefox browser, and the Yahoo e-mail program running within Yahoo home page. That is, these three are "layered" user applications.
PROBLEM When trying to print an e-mail, a window with this message appears: "The new window appears to have been blocked by a popup blocker. For best results, we recommend that you add att.net Mail to your popup blocker's list of allowed sites. Some popup blockers will temporarily allow a window if you hold down the Ctrl key."
Installing the printer, printer driver and the USB cable hookup was done correctly. Proof: the printer works just fine when printing a document in the MS Works word processor. The problem above occurs only in the Yahoo e-mail program.
WHAT WAS DONE The "att.net" was added to the Firefox browser as an allowed site. The path in the Firefox browser is: Tools / Options / Content. Adding "att.net" to the exceptions list did not correct the problem.
POSSIBLE PROBLEM CONDITION It's possible that when trying to print an e-mail, the window that gets blocked is the Print - Mozilla Firefox and the MS Print command window. (This leads to creating a PDF print file that's stored on the hard disk.)
TECH SUPPORT RESPONSE The AT&T Tech Support claimed that there is no popup blocker in Yahoo or Yahoo e-mail programs. The McAfee Tech Support checked their software by a remote online access and claimed that their software is OK.
Kaikki vastaukset (2)
Hello CBradley, go from Firefox button if you have it enable OR Tools menu > Options to access the options window > Content panel > UNCHECK Block Pop-up Windows [ ] > click Ok to save it.
see for more info : Content Settings
thank you
Muokattu
In the Options window / under the Content tab, I UNCHECKED the Block Pop-up Windows box but this DID NOT correct the problem. Still looking for an effective fix.