How do I stop FF from opening everytime I want to use the XPS Viewer,even when FF is not open at the time
This is actually a workaround answer for the question at https://support.mozilla.org/en-US/questions/943960 , which has been archived.
This problem persists for me in FF 27.0.1. The source of the problem can be found in this bug: https://bugzilla.mozilla.org/show_bug.cgi?id=358297 which Mozilla seems to think has been fixed.
Basically, the MS xps reader program thinks it needs to open MS Internet Explorer, but it does this by opening the default browser, which for us is probably FF.
Here is the workaround:
If you want to open an xps file in ms windows:
- First right click on the file in ms explorer to get the context menu.
- Choose "Open with" > "Choose program"
- Instead of the default choices (if any) offered, choose "Internet explorer"
- ALSO, check the check box "Always use the selected program to open this type of file."
This will make Windows go straight to IE, which works for me. However, you will still have to have the underlying handler installed, presumably.
Всички отговори (6)
Hi pb,
I have no idea, but please do not be afraid to share this information with the bug or to file a new one saying that the issue is back in another version. Considering this is a really really old version of Firefox, the code may have changed since then. So please check the about:permissions page and the Preferences/Options > Applications menu to see if there is a preference for this.
1. "this is a really really old version of Firefox" Really? FF 27.0.1 is really old? It's the latest version as of today. Read my post more carefully.
2. The bug was updated relatively recently by someone else, who was told to file a different bug. I do not have time to refile bugs that other people have already filed and updated. Among other things, I will be told to install the latest build and see if the bug persists.
3. The purpose of my post here was to help others who might have the same problem.
4. If you "have no idea", why did you feel the need to respond? I would rather hear responses from those who have some idea.
I think that what Rachel meant is that the bug report you referenced is about the Firefox 2 branch and fixed in a Firefox 3 beta version and wasn't about the version number of the current release.
Take a look at the last report in that bug: https://bugzilla.mozilla.org/show_bug.cgi?id=358297#c79
That is for ff 21.0 in June 2013. Yes, it was first reported a long time ago. And Mozilla thinks they fixed it a long time ago. Maybe they did, maybe they didn't. I don't care. I have a workaround that only takes 30 seconds. Hopefully that's useful to someone. If Mozilla chose not to follow up on the last person to report the bug 9 months ago in 2013 for v 21, then I am not interested in spending my time persuading them they should do otherwise.
BTW, it's not actually FF's bug, it's Microsoft's bug, but again, I don't care; I just have a workaround.
Thank you cor-el, and ya pb, I did not catch the date of the last post.
The post was escalated automatically with no response after 24 hours. This perhaps is a flaw in the system, since the goal of the forum is to answer every thread.