My website is broken in IE11. We found that it’s broken due to XSLTProcessor and XPathEvaluator since they are not supported any more in IE. I did some R&D and found that it’s also not supported in IE9 and IE10 but my website is working fine in IE9 and IE10. May I know why it is broken in IE11?
In below screenshot, we can see that document mode is Quirks. Don’t we have same behavior for IE11?
EDIT
We also have meta tag in our master page and it was working fine until IE10 but it’s broken in IE11.
<meta http-equiv="X-UA-Compatible" content="IE=8" />
Do we have to use different meta tags for IE11?
I changed meta tag to <meta http-equiv="X-UA-Compatible" content="IE=5" /> and it started working fine.
Related
In Firefox 53 on macOS, a simple video autoplay attribute isn't working. No problem in any other browser, on macOS or Windows 10. The page code couldn't be simpler:
<!DOCTYPE html>
<html>
<head>
<meta charset='UTF-8'>
<title>Video Autoplay</title>
</head>
<body>
<h1>HTML5 Video<br>This should autoplay in all browsers</h1>
<video src='../media/wildlife.mp4' width='640' height='360' controls poster='../media/wildlife.jpg' autoplay></video>
</body>
</html>
Anyone have any idea what the issue is? To be clear, I'm not talking about iOS or Android - this is a laptop/desktop issue only.
It seems that I had done some tinkering in about:config, which disabled the video autoplay. A "refresh" of Firefox cured the problem.
User error. ;)
This is a kinda generic question so I don't have any specific code to post. Our ASP.NET 3.5 application has to support multiple browsers, including IE8+. And it does so - if the backend IIS server is below 8. If we try to browse a site installed on IIS 8 (Windows Server 2012) from IE8 - page renders incorrectly, styling is wrong, dimensions screwed etc.
This is not happening if IIS8 site is browsed with any other browser (including IE9 & IE10) OR if IE8 browses sites installed on IIS 7.5 and below. So the only combination IIS8/IE8 doesn't work. I understand that those 2 are quite a few years apart, but what could be the reason for this behavior - feel free to downvote, but I could use a few starting pointers.
Tracing HTTP calls shows that all pages, CSS and JS load normally. All our pages have <!DOCTYPE html> and <meta http-equiv="X-UA-Compatible" content="IE=Edge" />. No errors are thrown either server-side or client-side.
Any help is appreciated.
I am having one widget in which I am trying to display text along with angle quotation mark-right(») character. A text inside this widget is following.
Begin Typing Here »
It's being displayed correctly in Firefox (in windows + Ubuntu), but in one of our Mac machine in Firefox + Chrome, "»" is not being displayed correctly.
I already have verified the default encoding that is set into Firefox in Mac. It's same as my ubuntu and windows machine's firefox.
EDITS:
I have following present in my HTML.
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
Here's screenshot of issue on Mac.
Can someone share some random thoughts on this?
im making hybrid app only for android, and designer gave me 480px(minimum size) layout.
i declared meta view port like this...
<meta name="viewport" content="width=device-width, initial-scale=1.0, minimum-scale=1.0, maximum-scale=1.0, user-scalable=0, target-densitydpi=high-dpi " />
also the my css is
body {min-width:480px; height:100%;}
the problem is when i test on my phone, almost every browser shows perfectly! But Except Mobile Chrome Browser. it shows layout bigger and overflow on the screen...
what did i have wrong ?
To my understanding, Android devices don't use the viewport. iOS devices do. You CSS is actually taking over. So depending on your device's initial width, smaller than 480px, your layout will overflow because of the min-width. Your best bet might be to use the min-width:320px and width:100%.
Try that.
What do you mean by the "mobile Chrome browser". You mean the native browser that comes predownloaded on the phone or the Chrome browser you download from the Play Store?
I have a corporate app with ie8 as the current forced browser. Machines are locked down tight and i can't even test on anything else because I can't install anything else. There are no other version of ie in use. it is 100% ie8. no 7, no 9. And they default to run in ie 7 compat / ie8 quirks mode.
In order to get stuff working right and to force standards mode, i had to use the html 5 DTD (to future-ready the site for mobile dev coming down the pipe instead of xhtml4) and
<meta http-equiv="X-UA-Compatible" content="IE=8">
heading in the template.
I have no information when they might go to ie9... or even skip to ie10.
Whats the best way to future proof this intranet site without being able to test it in ie9 or ie10, or a gecko browser?
I tried to follow tight standards and keep it clean with jquery and css and no in-line markup.
What does an ie9 do when it sees the ie=8 x-ua header? Should i use something else instead of this? I may not be working this app when the move comes. What notes should I leave for a future developer to be aware of?
Leave the X-UA-Compatible set to IE=8. IE9 and IE10 will try to switch to IE8 mode.