User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008052906 Firefox/3.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008052906 Firefox/3.0 Hi, On File, Print and selecting "Fax" the dialog box does not bring the fax information dialog box. Other applications including openOffice can do the fax. It started happening after upgrade to Firefox 3.0 Thanks Raj Reproducible: Always Steps to Reproduce: 1.on any webpage go to File manu 2.Select Print 3.Select "fax" as Printer name 4. Click OK. The same use to work in earlier release of Firefox and still works in other applications. Actual Results: as above Expected Results: The dialog box should bring the "Send Fax Wizard"
This regressed between 2008-01-14 and 2008-01-16. In the 2008-01-15 build it started crashing. Bonsai link between 2008-01-14 and 2008-01-15: http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=all&branch=HEAD&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2008-01-14+04&maxdate=2008-01-15+07&cvsroot=%2Fcvsroot Bonsai link between 2008-01-15 and 2008-01-16: http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=all&branch=HEAD&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2008-01-15+04&maxdate=2008-01-16+07&cvsroot=%2Fcvsroot My best bet is that this is a regression from bug 352791, since that one has caused bug 413200, which seems related.
9 years ago
We won't block 188.8.131.52 on this, but it's definitely wanted and something we should take for 184.108.40.206.
How do you expect it to get fixed if it's not assigned to anyone, exactly? What will happen to get it assigned?
Boris, I intended on circling back around to find an owner after code freeze for 220.127.116.11.
If it helps as an additional data point, I ran into this problem recently on an older (slower) Pentium III computer running Fx 3.0 and Windows XP Pro SP3. After selecting the "fax" printer device in the printer properties dialog, the "send fax" wizard did in fact appear for a split second before disappearing. I could find nothing in the system event log, and Firefox kept right on running.
Johnny, can you look at this since you fixed bug 413200?
Boris, why do you think this should block 1.9.1 at this point?
Damon, I think we need to fix this regression. Note that I made the blocking request in July... It does seem unlikely that we'll block for 1.9.1 on this now that we're here and not in July, but I don't think we want to just lose track of this bug. We have a regression range and such; we just need someone on Windows to sit down and take a look at what's happening.
I am having this same problem. Has there been any fix yet? As soon as i choose my 'fax' from my list of printers, the fax dialog box appears for a split second, then disappears. This started happening to me right after i upgraded firefox.
If it's not blocking1.9.1 we're not going to get the developer resources to be able to block1.9.0.x -- we'll look at a fix when it's fixed on trunk.
Any updates on this bug? This is unfortunately delaying implementation of Firefox 3 in my environment.
Due to the long delay in any fix for this problem, I've decided to uninstall firefox and try google chrome.
Grrr. Yeah, we really should fix this. I'm going to find a dev to dig into this.
We should have a release note so that people trying to use Firefox to fax from XP aren't confused. This one got me.
I'm seeing this same behaviour. A workaround is to open the same URL in Internet Explorer ;) Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:18.104.22.168) Gecko/2009060215 Firefox/3.0.11
Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1) Gecko/20090624 Firefox/3.5 fwiw, selecting fax works for me on the release 3.5 running Vista.
Faxing is working correctly with Firefox 3.5 on Windows XP Looks like the bug was fixed for that release?
Hmm, so either this was fixed by some other bug fix, or this problem is specific to a specific Fax driver or something else. Raj, can you test again and let us know what fax driver etc you're using, to maybe see if others with the same setup can reproduce as well?
I can test this again on multiple systems. I will report working/not working with 3.0.x and 3.5 I'll try to uncover Shared Fax Driver versions as well.
I can still see the bug in current trunk build.
We won't block 22.214.171.124 on this but will consider a fix should one appear.
This bug is definitely also in the latest 3.5.1 release build. I have Windows XP SP3 and am using the Microsoft Fax that comes with the operating system. If I print to the fax, I can see the usual first form "Send a fax" appear briefly, it is totally empty, and then it disappears.
Any progress towards a fix for this issue?
CC-ing some windows developers.
I did just discover a single system in my office that is not affected by the bug for some reason. Here is what I found. Doesn't work Firefox 3.5.2 Fax SHRFAX: Driver ver.5.2.2600.5512 (xpsp.080413-0852) Works XP SP2 Firefox 3.0.12 Fax SHRFAX: Driver ver.5.2.2600.2180 (xpsp_sp2_rtm.040803-2158) Doesn't work after Firefox upgrade XP SP2 Firefox 3.5 Fax SHRFAX: Driver ver.5.2.2600.2180 (xpsp_sp2_rtm.040803-2158) After upgrading the working machine to Firefox 3.5 faxing ceased to function.
Hi, I'm running Firefox 3.5.3 On XP SP3 Fax SHRFAX: Driver 5.2.2600.5512 The wizard comes up, but the first time after I set it up, it showed up underneath Firefox. Now, every subsequent invocation, have the dialog showing up fine.
Hi A simple work around is to install IE tab plug in. The issue doesnt crop up then.
Any hope here? I'm getting pressure to get a more advanced browser in house, and IE8 looks like it might be the only option.
I found a really good work-around. I use the "Coral IE Tab" add-in. It allows a Firefox tab to be rendered using the IE engine. It can be set up so that you can click on the firefox icon at the bottom right, which turns the icon into an IE icon, and the page is rendered using the IE engine. Then you can print using Microsoft Fax and it works perfectly.
I am aware of the IE Tab work-arounds. Unfortunately I support about 300 users, and the time and effort it would take to install the extension and educate them on what to do negates the benefit of using the work-around. Thanks though
I have another work around when you click with the mouse on the printing progress screen (small pop up) for about 3-4 seconds the fax dialog does appear and you can fax from Microsoft as usual.
I have confirmed that holding the Printing Progress screen does allow faxes to be sent. Maybe this will help the devs figure out what is causing the issue.
Johnny, any progress here?
Yes! But no patch in sight yet. What I've learned here is that the fax dialog that appears after the progress dialog disappears appears to be parented at the progress dialog, and when we tear down the progress dialog, the fax dialog goes along with it, which is why it only flashes on the screen momentarily. The suggested workaround makes the progress dialog stay around longer (since the mouse holds it alive), long enough that the fax dialog gets established enough to hold the progress dialog alive (yeah, I'm hand waving a bit here). Another workaround is to click in another window after the progress dialog is opened, but before the fax dialog is opened, doing that gives focus to whatever window you click in (can even be the desktop), and makes the fax dialog survive us tearing down the progress dialog here. So it seems like this is due to an odd interaction between the currently focused window and the Windows XP fax dialog. I've been unable to reproduce this on Vista or Windows 7. Jim Mathies, Rob Strong, or anyone else, if anything stands out as obvious to you guys as far as fixing this, please let me know :) I'll be digging in a bit deeper here tomorrow, but I don't immediately know how to get around this, short of figuring out a way to re-order things here so that the progress dialog goes away sooner to not be the currently active window when the fax dialog is brought up by Windows...
Hmm. I see nothing in the ranges from comment 1 that would be related to window parenting on Windows, offhand. There are some widget/ changes, but they're gtk2 and cocoa. And nothing obviously touching the relevant cross-platform code. Martijn, can you confirm that regression range, just to double-check?
(In reply to comment #37) > Hmm. I see nothing in the ranges from comment 1 that would be related to > window parenting on Windows, offhand. There are some widget/ changes, but > they're gtk2 and cocoa. And nothing obviously touching the relevant > cross-platform code. FWIW, my money's on bug 352791. In particular, if we have any code anywhere that uses the context stack, then bug 352791 could very well have caused us to run some code on a different context, which could very well cause us to use the context as the parent for something instead of whatever it was we did before. jst, do you hit a breakpoint in GetContextFromObject just before the Fax dialog comes up?
So my bet is that this has to do with us running JS on a different context, which affects how windows are closed (sync vs not), which does explain why this worked before, but not after the fix for bug 352791, which changed exactly that. I have a fix for this, and I'm convinced that this just happened to work before the fix for bug 352791 went in by pure accident. And ultimately, this is a bug in Windows XP's fax dialog, no question about that in my mind.
Created attachment 410638 [details] [diff] [review] Fix. See the big comment in the patch for explanation.
8 years ago
Thanks for the hard work everyone. Imagine that... A bug in a Windows UI element... :)
Fixed on trunk. http://hg.mozilla.org/mozilla-central/rev/bcd91fc6969b
Fixed for 1.9.2. http://hg.mozilla.org/releases/mozilla-1.9.2/rev/f36f5199be3d
How do I install the fix
Download the nightly build or wait till rv 1.9.2 is released. The current release 3.5.5 is rv 126.96.36.199.
Comment on attachment 410638 [details] [diff] [review] Fix. Approved for 188.8.131.52, a=dveditz for release-drivers
Marking the 14 bugs that are both: * nominated for blocking1.9.3:? * fixed on the 1.9.2 branch (according to status1.9.2) as blocking1.9.3:alpha1, so that we don't have to go through the nominations individually. They're all fixed already (so there's no work to do), and being fixed on 1.9.2 means they probably do block 1.9.3.
Created attachment 423908 [details] [diff] [review] Fix that actually works on 1.9.1 Turns out there's no focus manager on 1.9.1, so we'll need to use the window mediator there.
Created attachment 423913 [details] [diff] [review] Fix that actually works on 1.9.1
Comment on attachment 423913 [details] [diff] [review] Fix that actually works on 1.9.1 r+, god help me for reviewing focus+printing code! :)
Comment on attachment 423913 [details] [diff] [review] Fix that actually works on 1.9.1 approved for 184.108.40.206, a=dveditz
http://gsfn.us/t/pj59 states seeing this issue with thunderbird 3.0.2 thru 3.0.4, which have this fix
Wayne, if this now happens with tbird but not Firefox, we should file a separate bug to track that... That will make sure it doesn't get lost.
Issue is Resolved - removing QA-Wanted Keywords - QA-Wanted query clean-up task