From Bugzilla Helper: User-Agent: Mozilla/5.0 (Macintosh; U; PPC; en-US; rv:0.9.6) Gecko/20011120 BuildID: 2001112011 I use Mozilla 0.9.6 on MacOS 0.9.1 Japanese on a network iMac client. Printer Epson LP-8700 (ESC/Page) is connected to the same LAN. FTP is an AppleShare 6.3 Japanese. 1. Connect Mozilla browser to AppleShare FTP. Mozilla displays correctly. 2. Try to print the page. You will see strings of meaning letters on the first page and many blank papers coming out of the printer. 3. I followed the same procedures with Mozilla 0.9.6 on Win98; no problem. Reproducible: Always Steps to Reproduce: 1.(see above) 2. 3.
dup of bug 27740?
No; thats the XUL widget. this is probably going to be dealt with with my other cleanup work, though, fixing send page, and so on, too)
Severity: critical → major
Kazuyoshi, are you able to print other pages using this configuration?
Dear Greg, I can print any page whose address is "http://www. . . . " I cannot print any page whose address is "ftp://ftp.jime.or.jp" "ftp://ftp.jime.or.jp" is NOT accessible from outside; this ftp is AppleShare 6.3 Japanese and is for internal use only. I'm sorry but I haven't tried to print public ftp connection.
Kazuyoshi, "ftp.jime.or.jp" doesn't resolve as a valid host name. How about <ftp:// ftp.mozilla.org/>, can you print that?
I downloaded the Mozilla Full Installer with TalkBack and re-installed (clean install) Mozilla 0.9.6. I tried to print several public ftp servers in the US and Japan, and found that I can display and print any page correctly on Mozilla browser now. Although I didn't mean to disturb you at all with evil mind, I do apologise for wrong report. However, TalkBack does not work this time, either! I should report this to somewhere else. . .
Resolving WorksForMe per Reporter. Kazuyoshi, should you encounter this problem again in the future, please reopen this bug. As for TalkBack, be aware it doesn't run after every type of crash.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → WORKSFORME
VERIFIED, per reporter.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.