Is there a solution to launch certain links in a different browser?
I would like to deploy Firefox as the default browser in an enterprise, but many enterprise apps are still only compatible with IE due to the use of proprietary plug-ins. Is there a solution which would allow me to specify certain web sites, domains, or zones, which should launch IE instead of Firefox?
P.S. Something like Google Chrome's Legacy Browser Support extension: https://support.google.com/chrome/a/answer/3019558?hl=en
선택된 해결법
I tested out the Open in IE extension with our intranet. Since some of the pages work in Firefox and some do not, I found that putting the login link into the Options for Open in IE gave me the best result. In other words:
- Open the Add-ons page (Ctrl+Shift+a), click Extensions in the left column
- On the right side, find Open in IE, click Options
- Paste the URL in the dialog [http://server/dir/login.aspx] and click Add
- Reload intranet page and test various links
It's great. Wish I had this years ago.
For deployment purposes, the Open in IE domain list is stored in prefs.js like other add-on data in the extensions.openinie.DomainList preference.
As you probably already know, you can distribute preferences using a user.js file in the user's profile folder or an autoconfig file in the program folder. I'm not sure how you keep that up-to-date, or whether it might frustrate the user if they can't add to the list.
Also, the extension is hardcoded to use the 32-bit version of IE on 64-bit Windows. If you have 32-bit Windows or prefer 64-bit IE, you'll need to modify the extensions.openinie.IEPath preference.
문맥에 따라 이 답변을 읽어주세요 👍 1모든 댓글 (3)
If you mean a Favorite (.url file), then it's very difficult to not have it simply open in the default browser.
If you mean a link in a page in Firefox (e.g., on your intranet), there are some extensions that add a context menu item to open the link in IE. For example:
However, it sounds as though the add-ons' feature of automating that for certain domains is not working. You could inquire whether the author plans to update it, or if you have any JavaScript developer resources, you could modify the extension in-house to your needs. (MPL 1.1 license)
선택된 해결법
I tested out the Open in IE extension with our intranet. Since some of the pages work in Firefox and some do not, I found that putting the login link into the Options for Open in IE gave me the best result. In other words:
- Open the Add-ons page (Ctrl+Shift+a), click Extensions in the left column
- On the right side, find Open in IE, click Options
- Paste the URL in the dialog [http://server/dir/login.aspx] and click Add
- Reload intranet page and test various links
It's great. Wish I had this years ago.
For deployment purposes, the Open in IE domain list is stored in prefs.js like other add-on data in the extensions.openinie.DomainList preference.
As you probably already know, you can distribute preferences using a user.js file in the user's profile folder or an autoconfig file in the program folder. I'm not sure how you keep that up-to-date, or whether it might frustrate the user if they can't add to the list.
Also, the extension is hardcoded to use the 32-bit version of IE on 64-bit Windows. If you have 32-bit Windows or prefer 64-bit IE, you'll need to modify the extensions.openinie.IEPath preference.
Do this. Get the full path / filename of the program. Save it in a text file. Now get the full web address. At the end of the filename, add a space. Then add the web address. Save this file as website.BAT A batch file.