Hi,

Can somebody help me in resolving this issue. I am getting the below error upon clicking on a button in a page when checked in Microsoft Edge browser.

Error:Object doesn't support property or method 'showModalDialog'.

I have even tried placing the below meta tag but it did not worked.

<meta http-equiv="X-UA-Compatible" content="IE=edge">

'showModalDialog' is working when checking in IE9 and IE 11 modes.

Kindly help me in this.

Thank you.

MPaladi

I am trying to use glyphicons as a font within my site and they do not display after a "cache-clearing refresh" (ctrl+F5), or hitting the 'Back' button. If I browse within the site, the icons will display.

Since the site is on a private intranet, I can not link to it here, but I am seeing the same quirkiness on well-known sites such as glyphicons.com and getbootstrap.com/components/#glyphicons.

If it helps, I am using IE11 (11.0.9600.17959) on Windows 7 Enterprise, Service Pack 1

I Wish:

 add a meta label to solve the problem of Microsoft edge Silverlight ?

I have recently been converting some html files to MHT for convenience of storage & display (versus HTML and additional 'files' folder) and as an alternative to PDF.

MHTML format is very unforgiving when editing, so I would like to understand the format and viewing mechanism, to ensure usability.

tia

I have taken the sample code on MSDN and adapted it slightly for my purpose ( my code below). When I execute the code in IE 11 on my Windows 8.1 box (IE 11, v11.0.9600.17905), it works sometimes (i get the prompt to save, and my file appears in DOWNLOADS). However without changing ANYTHING at all, I run it again and it gets on error (the mssaveblob returns TRUE), however, no save occurs and the code completes. On another box running Windows 7 with IE 11 (v11.0.9600.17959), it never succeeds. Debugger shows me that everything is working and no FALSE returns in anything. Just, no file. I am at wits end.

Working with SharePoint Online I often use the console in IE to test JS.

However, the lovely new autocomplete feature often hangs the machine if it finds too many options, which it regularly does being run against a SharePoint page.

Is there a way of turning this off, assuming that this won't be fixed in the near future?

Thanks

Will

There is an extremely confusing note following the code shown in an article on the MSDN website entitled "Specifying Legacy Document Modes" - https://msdn.microsoft.com/en-us/library/jj676915(v=vs.85).aspx.

In the section, "Specifying multiple content attribute values," following the code <meta http-equiv="X-UA-Compatible" content="IE=7,9,10" >, it says: "Note: The previous example is provided for illustrative purposes only; don't use it in a production environment."

If we shouldn't actually use it, why even show it?  Why even implement support for a certain code syntax, if no one should use it on production websites?

I want to achieve this exact type of result (rendering only one specific version of IE in Compatibility Mode -- in my case I want IE9 to render in IE8 document mode -- but have all other IE versions use their highest supported 'edge' document mode) -- and -- I want to use it on our production website.  So I figured out the actual code I want to use is:  <meta http-equiv="X-UA-Compatible" content="IE=8, IE=10, IE=11, chrome=1" />

This method would work perfectly for me, and I even tested it in IE6-11 and it does — so my only concern is that bothersome note, "don't use it in a production environment".  What would even be the repercussions (if any) of using it?  If I shouldn't use it, then what should I use to do the same thing?

We really need this meta tag combination for our site to work right in all versions of IE, and appears to be the only reasonable solution at the moment.  It is because we have a JQuery slideshow on our site which we found to work fine in all versions of IE except for IE9 — in native IE9 doc mode, the layout falls apart.  However, it was discovered that it displays normally in IE9 if we "Force IE9 to IE8 Compatibility Mode" (IE9 running in IE8 Document Mode).  Currently, we are using the more simple Compatibility Mode meta tag:  <meta http-equiv="X-UA-Compatible" content="IE=8" />.  But the problem with this is, it renders ALL versions of IE in Compatibility Mode (IE8 document mode).  This is bad for 2 reasons:  It makes the newer IE versions (10 and 11) run slower because they are emulating IE8, and additionally, the newer IE versions don't display all of our intended CSS3 styles (rounded corners, drop shadows) because again, they are emulating IE8.  

I am fully aware that the most ideal solution is to figure out a CSS and/or JS fix for the IE9 layout problem which would make the X-UA Compatible meta tag unnecessary — but this would require far too much trial and error, development time, and testing for us at this time — and we would not even know if we could figure out a solution.

Thank you in advance to anyone who can shed some light on this.

I have numerous personal web pages that I have had on line for around 20 plus years.  I am finding that when using Microsoft Edge to view them that the embeded audio player does not work.  Works fine with older versions of Internet Explorer and all other browsers but not Edge.  It appears I am going to have to change the code in over 100 entries in order to get it to work with Edge.  Anyone know if Edge developers are planning on addressing this issue or will I have to change all my pages?  

We are usingnavigator.msLaunchUri method as protocol handler in our application. As per the MSDN documentif the user's system does not have a program registered to handle a specific protocol, the Internet Explorer will invoke thenoHandlerCallback. It is the fallback mechanism which the developer can define to handle when such scenarios happen. But in case of EDGE thenoHandlerCallback is not executed. It is automatically redirecting to the default fallback mechanism of opening the Windows Store dialog to open the program. Can someone confirm if such issue is happening in EDGE? If yes, can we expect a fix sometime soon?

Thanks.

Hi,

I am using Picker control in my web application. As application is compatible in IE 5, I have changed my browser document mode to IE5. After changing my Picker control is not working(It gets slow).

I have 25000 rows in Picker control.

Control is working fine in IE 11 with document mode Edge but my site is not working.

Control is working fine for low data like 1000 rows in IE 11 with Document mode 5 and my site is also working fine.

Control not working for 25000 rows in IE 11 with document mode 5 and my application is working fine.

Please help me with best option.

Thank You,

Abhay

I do not want any kind of videos or animations to play unless I choose to click on the "Play" button.

This includes Flash, HTML5, GIF, MP4, or any type of video that may be invented.

What would be ideal is to have a new set of controls in Internet Options that would allow the user to control/override the video controls in all web pages.

For example, HTML5 has the <video> ... </video> element that has certain attributes:
autobuffer
autoplay
controls
loop

The user should be able to control each these attributes on a global basis for all web pages. For example:

Control Panel
Internet Options
Advanced tab
Video options (new category)
autobuffer - yes or no (new option)
autoplay - yes or no (new option)
controls - yes or no (new option)
loop - yes or no (new option)

$.ajax({
    url: "http://10.13.22.150/req_path",
    success: function(result){
        console.log(result);
    }
});

I'd like to send Cross-Domain XMLHttpRequest to an ip address in the private network.

However, the following error is shown in console of developer tools:

SCRIPT7002: XMLHttpRequest: Network Error 0x2efd, Could not complete the operation due to error 00002efd.

According to Wireshark, the packet is not sent from client side. I guess the request is blocked by Microsoft Edge

Furthermore, I found that the requests are only blocked if the url of XMLHttpRequest and Edge client are in the same CIDR of private network.

Other browsers like IE11 / Chrome / Firework work just fine. This circumstance is only shown in Microsoft Edge.

Is there any workaround or solution about this issue?

I am using below code and it is working for all browse except IE10 can you please help me for proper solution.

When I change the cursor by JS in IE10, it will not be effective unless I move the mouse.  PLEASE HELP...

function AjaxProcessingIndicator() {
            $('html, body').addClass('busy');
        }
function AjaxCompletionIndicator() {
            $('html, body').removeClass('busy');
            document.body.style.cursor = 'default';
        }

Hi,

Currently my javascript crypto library is working quite consistently in Chrome and Firefox, but the same operations are often behaving differently when executing them in the context of Internet Explorer 11. Here is a simple example of what I'm talking about:

First I generate a key using

var aesAlgo = {name: 'AES-GCM', length: 256}
webcrypto.subtle.generateKey(aesAlgo, 'true', ['encrypt','decrypt']

The generated key is stored in generatedAesGcmKey variable... I then encrypt some hard-coded string using exported key:

var dataToEncrypt = Util.strToUint8Arr("DEADBEEF")
aesAlgo.iv = webcrypto.getRandomValues(new Uint8Array(12))
aesAlgo.tagLength = 96
webcrypto.subtle.encrypt(aesAlgo, generatedAesGcmKey, dataToEncrypt)

I then try to decrypt this data, using the same algorithm, key as I used for the encrypt call...

webcrypto.subtle.decrypt(aesAlgo, generatedAesGcmKey, encrypted)

but instead of getting my original data after a successful decrypt call (which is what I get in Firefox/Chrome), I get

Error: Invalid argument. at Anonymous function, with a reference to a line in my script that contains the webcrypto.subtle.decrypt call

It's not immediately clear as to what is going wrong or how to troubleshoot it. Am I meant to perform some adjustment/transformation on the result of the encryption before I can decrypt it?

In another location in my code, I'm trying to unwrap AES-GCM key that was wrapped on the server using RSA OAEP and SHA-256. Again, unwrapping is relatively straightforward in Chrome and Firefox, but when using IE11 I seem to encounter puzzling errors without much detail and get even more confused by documentation. e.g.

https://msdn.microsoft.com/en-us/library/dn302335(v=vs.85).aspx

says:

The wrappedKey object must contain a JSON Web Key (JWK) structure encapsulated with JSON Web Encryption (JWE). The content encryption algorithm used in the JWE must be AES-GCM.

In my case the wrapped AES GCM key arrives from the server in 'raw' format... after reading the above mentioned snippet of documentation, I've started trying to convert it to 'jwk' format before invoking webcrypto.subtle.unwrapkey (e.g. via webcrypto.subtle.importKey('raw'...) followed by webcrypto.subtle.exportKey('jwk'...) but to no avail, still am getting on.error event handler triggered with a parameter that doesn't seem to contain anything useful to help with troubleshooting why unwrapping fails.

Any tips/suggestions would be much appreciated,

regards,

Greg

When using JavaScript to get the node value in an XML file, IE 11 and 10 drop all the characters in the string after a hyphen. 

An example of the XML:

<?xml version="1.0"?><ARCHIVE><YEARS>2015-2016</YEARS></ARCHIVE>

An example of the JavaScript:

var xmlhttp = new XMLHttpRequest();
xmlhttp.onreadystatechange = function () {
if (xmlhttp.readyState == 4 && xmlhttp.status == 200) {
var m = xmlhttp.responseXML.documentElement.getElementsByTagName("YEARS");
for (var h=0; h < m.length; h++) {
  {
    try {
     txtYear = m[h].firstChild.nodeValue;
    }
    catch (er) {
     txtYear = " ";
    }
  }
}
}
xmlhttp.open("GET", url + "?nc=" + Math.random(), true);
xmlhttp.send();

IE 11 and 10 will return the value of txtYear as "2015", dropping "-2016" from the string. However, IE 9, Edge, Chrome and Firefox return the full value of "2015-2016". I have tried replace the hyphen in the XML file with the hex code for hyphen, but it still gets the same results. 

This use to work in IE 11, so I don't know if a recent patch has changed this or if I'm doing something wrong.

Hello Team,

We are facing an issue in Edge browser regarding xpath support.

My DOM element which I need to detect using xPath has 2 css classes applied to it.

<ul>

<li class="myClass1 myClass2"></li>

</ul>

If I mention only one class name in the xPath, it works in Edge browser e.g.

".//*[contains(@class,'myClass1')]"

but if I mention both class names (space separated) it doesn't work e.g

".//*[contains(@class,'myClass1 myClass2')]"

although it works well in all other browsers.

Please refer following fiddle link to replicate

https://jsfiddle.net/6L7z66bx/4/

IE 10 would print landscape, however after upgrade to IE 11, IE 11 will not print landscape All other programs print landscape even firefox, so problem must be with IE11. tried the usual setting printer preview to landscape print preview window changes to landscape and displays the page in landscape, but clicking print, the printer prints in portrait with the print running off the page. The print job does not orientate to 11x8.5, it prints the 11x8.5 landscape on a 8.5 x11 portrait paper.

Have not found anything on the web addressing this issue.

Any help would be appreciated.

Steve

body {
	margin: 0;
	padding: 0;
	color: #fff;
	font-family: Arial;
    font-size: 14px;
	line-height: 1.5em;
	background-color: #ccc;
	background-
}


a, a:link, a:visited {
	color: #fff;
	text-decoration: none;
	font-size: 15px;
}

a:hover {
	text-decoration: underline;
}

p {
	margin: 0 0 10px 0;
	padding: 0;

}
p.intro::first-letter {
    color: #fff;
    font-size:50px;

}
img { border: none; }

h1, h3, h4, h5, h6 { color: #fff; font-weight: normal }
h1 { font-size: 34px; margin: 0 0 30px 0; padding: 5px 0; }
h2 { font-size: 26px; margin: 0 0 20px 0; padding: 0;line-height: 1.1em; color:rgb(255,221,0); }
h3 { font-size: 21px; margin: 0 0 15px; padding: 0;line-height:25px; color:rgb(248,151,40); }
h4 { font-size: 18px; margin: 0 0 15px; padding: 0; }
h5 { font-size: 16px; margin: 0 0 10px; padding: 0; }
h6 { font-size: 14px; margin: 0 0 5px; padding: 0; }

.cleaner { clear: both }
.h10 { height: 10px }
.h20 { height: 20px }
.h30 { height: 30px }
.h40 { height: 40px }
.h50 { height: 50px }
.h60 { height: 60px }


fieldset{
	border:3px solid;

}
legend{
	font-size:20px;
	color:rgb(248,151,40);
}


.float_l { float: left }
.float_r { float: right }

.image_wrapper {
	display: inline-block;
	padding: 0px;
	background: #000;
	margin-bottom: 5px;
}

.image_fr {
;
top: 0;
right: 0%;
float: right;
height:100px;
width:220px;
margin: 0px 0px 15px 15px;
}



#header {
	clear:both;
	height:110px;
	margin:0 auto;
	background-image:url(images/86930033.JPG);

}

#site_title {


}

#site_title h2 {
	margin: 0;
	text-align:center;
	padding-top: 30px;
	font-size:28px;
    color:#000;
text-shadow:2px 2px #0093d0;


}


#menu {
	width:960px;
	;
	margin: 0px auto;
	background:#0093d0;
}
#menu {
	;
}
#menu ul {
	margin:0;
	padding:0;
	list-style:none;
}
#menu ul li {
	margin:0;
	padding:0;
	list-style:none;

	;
}
#menu ul li a {
	font:bold 12px Arial;
	text-transform:uppercase;
	color:#fff;
	padding:7px 10px;
	text-decoration:none;
}
#menu ul li:hover > a {
	text-decoration:none;
	color:#fff;
	background:#ccc;
}
#menu ul li a.current {
	background:#fff;
	color:#0093d0;
}
#menu ul ul {
	min-width:200px;
	;
	top:100%;
	z-index:666;
	background:#0093d0;
	display:none;
}
#menu li:hover > ul {
	display:block;
}

#menu ul ul li {
	display:block;
	width:100%;
}
#menu ul ul a {
	padding:7px 10px;
	display:block;
	color:#fff;
	border-bottom:1px solid #ddd;
	text-align:left;
}
#menu ul ul a:hover {
	background:#ccc;
}
#menu ul ul a.current {
	background:#dddd;
	color:#0093d0;
}

#main {
	clear: both;
	width: 900px;
	margin: 0 auto;
	padding: 45px 30px 0;
	background-color: #54534a;
	overflow:hidden;
}

#main a:hover,#main a.current{

	font-size:16px;
	color: #c1d82f;

}
.col_w900 { width: 900px; padding-bottom: 30px }
.col_w420 { width: 420px }
.col_allw280 { float: left; width: 280px; margin-right: 30px }
.col_w900_last { margin: 0; background: none; }
.inner_box { margin-bottom: 50px; padding-bottom: 50px;   }
.last { margin: 0; padding: 0; border: none }

.post_box { clear: both; margin-bottom: 30px }
.post_box .post_header { padding: 10px 0; border: 1px; border-left: none; border-right: none; margin-bottom: 15px }
.post_box h2 { font-size: 20px; margin-bottom: 10px; }
.post_box p.post_meta { margin-bottom: 0; color: #666 }
.post_box p span.cat a { font-weight: 400 }
.post_box img { padding: 9px; border: 1px solid #333; background: #000; margin-bottom: 15px; }
.post_box a.more { float: right; }


.wrapper {
    text-align: center;
	clear: both;
	width: 800px;
	padding: 45px 20px 15px;
	margin: 0 auto;

}

.button {
    ;
	border:solid 4px #c1d82f;
	background-color:#fff;
	font-size:15px;
}

#footer {

	clear: both;
	width:900px;
    /* padding: 25px 30px 0; */
	padding: 45px 30px 15px;
	margin: 0 auto;
	background-color:#0093d0;
	text-align: center;
	color:  #fff;

}