I am using Prime faces form and the exe was being launched on button click through Javascript using ActiveX Object.This functionality was working fine in IE(Internet Explorer) but Edge is not supporting ActiveX Object.
Anybody know the alternate of it?
Earlier We have tried with ActiveXObject and was working fine.
Except VGR's solution, I think there's no programmatical way to open exe file in a modern browser. But if you're using Edge, you can open that page in IE mode. Edge IE mode supports ActiveX controls.
Edge IE mode is designed for organizations that still need IE 11 for backward compatibility with existing websites but also need a modern browser. If you're in an organization, you can configure IE mode policies to make that page always open in IE mode. Or you can just use Edge settings to configure IE mode pages.
Related
Google Chrome has #types/chrome for extension developing. Is there same thing for MS Edge? I find some mismatches between chrome and edge browsers and was hoping that types could help a bunch.
You don't need it. Edge is based on Chromium, and the same Chromium extension can be submitted to the Edge extension store.
https://learn.microsoft.com/en-us/microsoft-edge/extensions-chromium/
If you've already developed an extension for another Chromium-based browser, you can submit it to the Microsoft Edge Add-ons website. You don't need to rewrite your extension, and must verify it works in Microsoft Edge. When you migrate an existing Chromium extension to other Chromium browsers, make sure the same APIs or alternatives are available for your target browser.
For compatibility, make sure the API you use is supported by Edge (Supported APIs for Microsoft Edge extensions)
Traditional browsers such as Chrome and IE have mechanisms to see Javascript errors as either a notification implemented through a plugin in the case of Chrome and as a popup in the case of IE. However, in the newly introduced Edge Chromium browser, I was not able to figure out such a mechanism. Therefore please enlighten me should such mechanism be available in Edge Chromium, thank you.
There's no browser built-in approach to achieve this, but you can use extensions to achieve this in Edge Chromium. As Edge Chromium uses the same rendering engine as Chrome, you can use the same plugin which is used in Chrome.
For example, I find JavaScript Errors Notifier can achieve what you want. You can click on "Add to Chrome" to install this extension in Edge Chromium.
I have Old ASP Project that depends on ActiveXObject
and now I want to make my project cross-browser and work on chrome in additional to ie
Can I Find any Plugin that makes chrome support ActiveXObject
Note I tried to use DOMParser() instead of ActiveXObject but it's not working fine
ActiveX is only supported by IE - the other browsers use a plugin architecture called NPAPI. However, there's a cross-browser plugin framework called Firebreath that you might find useful.
Chrome doesn't support ActiveXObject. You could use IE Tab in Chrome.
IE Tab exactly emulates IE by using the IE rendering engine directly within Chrome. This will enable you to use ActiveX controls and test your web pages with different versions of IE.
I have written a bootstrap page and it works just perfectly on all browsers i have tested....except ie11 with enterprise mode on.
It seems to stretch everything to full width as if my screen is a giant phone. Im sure other things are broken in it but thats the first thing you see.
Anybody have any ideas if Bootstrap and Enterprise mode dont play well? I see some posts asking the question and some responses saying to force ie9 10 or edge mode but that wont work with enterprise mode as it overrides that...ie think.
From MSDN:
Enterprise Mode, a compatibility mode that runs on Internet Explorer 11 on Windows 8.1 Update and Windows 7 devices, lets websites render using a modified browser configuration that’s designed to emulate either Windows Internet Explorer 7 or Windows Internet Explorer 8, avoiding the common compatibility problems associated with web apps written and tested on older versions of Internet Explorer.
And from Bootstrap:
On Windows, we support Internet Explorer 8-11
So if you are running Enterprise mode in IE7 mode, Bootstrap will do all sorts of odd things. The solution would be to run in IE8 mode which may fix a lot of issues or don't add this site to the list.
I am getting a very weird kind of error with IE9. When I use a DOMParser from within a jsp page on localhost, it runs perfectly fine and gives the proper result.
But Shockingly, when I use DOMParser inside a normal HTML file (Not on the server. From the file system), I get this annoying message of "DOMParser is undefined" .. What is this and how can I make it work? Thank You.
P.S. It works fine on FF and Chrome
I would say that this is almost certain to be the browser running in compatibility mode when browsing local URLs.
You can check this by opening the dev tools (press F12) and looking in the top right corner; if it says it's in IE7 mode, then you've found the problem. Switch it back to normal IE9 mode and it should come right.
IE7 didn't support the DomParser object, so if IE9 is in IE7 compatibility mode, it's natural that it will stop supporting it too.
Ok, so that's what it's doing. But why is it doing this? There is a config setting in IE (both IE8 and IE9) which specifies that the browser should fall into compatibility mode when browsing sites on the local intranet. The reason for this setting existing is to allow companies who have internal sites designed for older versions of IE to upgrade to a new version without breaking those sites. It's intended to make like easier for corporate types who would rather not spend money fixing something when the broken version is good enough.
But it's a pain in the rear for the rest of us.
Obviously, if your site is on the public internet, it won't be affected by this flag, except when you're trying to work on it from localhost on your own PC. Therefore, the solution for you is to simply turn off this config setting in the browser and forget about it.
Of course, the fact remains that users of IE7 will still have this problem with your site, as their browser doesn't support the feature you're using. You could just drop support for IE7, and tell those users to upgrade. But if you want to support IE7 users, I believe that Dean Edwards' IE7.js script allows the browser to emulate this feature (along with a bunch of other stuff that Microsoft forgot).
Hope that helps.
I received this error, "DOMParser is undefined", on IE9 and it turned out to be an add-on that was disabled.
Name XML DOM Document
Publisher Microsoft Corporation
Status Enabled
Tools – Manage Add-ons – Microsoft Corporation