I'm aware, that Enterprise Mode in IE is an emulation of IE8 mode and the goal is to make legacy applications working within IE11 (well, the real goal is to show to the organizations that Windows 10 and IE11 can be adopted as MS is able to handle legacy code without involving numbers of developers to rewrite all web sites to match current standards :-) ). I know this is a setting of IE and IE is controlled by registry/local policy/global policy.
The question is - is there a way to force browser (from code perspective) to render the web site in Default Mode instead of Enterprise Mode no matter what GPO says, no matter if web site is/isn't mentioned in Enterprise Mode IE website list?
Let me also ask in different way - how and what do I need to add/avoid/adjust in the web site code in order to make sure, that this web site is IE11 ready and does not require any Enterprise Mode (emulation)?
I guess I know the answer but I haven't found any relevant source of it.
It's not possible to force IE11 browser to render the site in Standard Mode from code point of view - EM is new feature and it's controlled by GPO (Use the Enterprise Mode IE website list).
I have a ready template that is supposed to support the major browsers and IE versions 9, 10 and 11. The web page looks good on Chrome, Firefox and in my IE 10.
Using the F12 (developer tools) I have tested it using Browser Mode set at IE9, 8 and 7.
In the I have added <meta http-equiv="x-ua-compatible" content="IE=Edge"/> so the "Document Mode" is set to Standards by default. I have choosed Edge because it fixed some issues on 7 and 8, that were not fixed using the content="IE=1E9".
So everything looks nice in my pc, supposing that the "Browser Mode" is actual how it looks on an installed IE9, 8, 7.
When I use some online tools like http://netrenderer.com/ and set my choice to IE8 it shows a messy site, not like the one I see.
Who is the correct? Am I missing something?
Don't test using browser modes, use the actual browser - you can download free virtual machines from modern.ie.
Settings the IE=Edge doesn't guarantee proper browser mode. Check in the VMs or using browserstack to make sure the browser modes are being set correctly in the F12 tools
In my experience I have been mislead on more than one occasion using the IE developer tools when assuring my sites look good on IE variants. If you are familiar with VMs then I would suggest installing a Windows guest machine and install the appropriate browser versions.
If you want to test on your local machine for IE issues I use BrowserStack and I can configure it to run on my local machine so I can see my changes as I go along rather than making changes on local, publishing them, and then going into my VM and seeing if things look good.
Well, it's really that. I have a website, https://www.fagakademiet.no, developed with DotNetNuke and we recently upgraded to V7.
Everything works fine in my PC using Chrome, but some people complain that it does not work in their PC's using also Chrome. When they login, the admin toolbar does not work.
It also doesn't work in IE, Opera, Firefox, etc.
Any thoughts?
Often times issues like this are related to browser caching of the resources (JS,CSS,etc)
You might see if a Hard Refresh works for the users.
Also you might check the host settings to see if you have the client dependancy framework and resource minification enabled. Try disabling that if you do and see if that helps.
I have a Linux box. How do I see how my HTML pages look as rendered in Microsoft Internet Explorer? How do I test JavaScript functionality in Internet Explorer?
I don't want to install a VM and a copy of the Windows OS.
Your best friend as a Linux web developer is IEs4Linux, which uses Wine to run different versions of Internet Explorer.
Check out this page to see how your page will look across browsers and OS'
http://browsershots.org/
To actually interact with your web site though I would suggest something like Wine or a VM like Xen.
Also see this link: How to install internet explorer on Ubuntu or see this page IEs4Linux.
I use Linux at work and do web development that has to support Internet Explorer 6 (and later) and Firefox 2 (and later).
IE4Linux is not really good enough for properly testing Internet Explorer browser rendering as it doesn't work exactly as Internet Explorer does in Windows. You could use something like browsershots, but I would recommend running Windows in a VM and test using that for Internet Explorer testing. I've done that for awhile and it works great as long as you have a spare 512 MB RAM for Windows XP.
Another service similiar to browsershots, but faster, is IE NetRenderer. Otherwise, if you have a copy of Windows lying around, why not use a virtual machine? Suns VirtualBox is nice enough.
Probably your best bet for accurate rendering without paying for a Windows license is using one of the MS provided virtual machines. Below are some links on tutorials for setting up the VMs using VirtualBox.
http://blog.philipbrown.id.au/2009/03/internet-explorer-application-compatibility-vpc-images-under-virtualbox/
http://www.makeuseof.com/tag/installing-windows-7-on-a-virtual-machine/
I've used VirtualBox and these images quite a bit and it works well, the only downside is you have to reinstall every quarter because the images expire.
I agree that browsershots.org is a great place to start, but it only provides a screenshot. If you're using JavaScript or jQuery and need to see how see how things appear when you interact with your page in Internet Explorer (practically any version from Internet Explorer 5 and up), crossbrowsertesting.com is an excellent resource.
Is anyone writing applications specifically to take advantage of google chrome?
Are there any enterprise users who are considering using it as the standard browser?
Yes, I have started to pay very good attention to Google Chrome for my applications. Recent analytics show that between 6%-15% of my users are accessing my applications (varies between 6 to 15 in different applications) on Chrome. And, this number looks on an upward trend.
Thus, I can't really ignore it for testing right now.
As far as taking it as a standard goes, thats a long way off. I still have to test for IE6! :( Though, we have been planning to start using features like Gears (inbuilt in Chrome - downloadable elsewhere) once Chrome crosses the 25% mark. Thats when I believe that we will be looking at Chrome to be our preferred browser. I hope that we have Chrome 1.0+ by then! ;)
I switched to Chrome and haven't looked back except for the occasional site which doesn't work properly, forcing me to load it in Firefox. All my existing web applications work fine on it, and I'm using it for primary testing on my current development project.
I'm not actually targeting chrome, but I have added chrome to my browsers to test sites on. I've found some odd quirks in this product where some plugins cause the browser to hang, or run really slow in some environments, but they are still in beta in active development. But I definately now make sure sites I work on render well in chrome, as well as firefox, latest versions of IE, safari, Konquerer and opera. I usually check out how it looks on lynx as well, that helps me catch "un-alternated text" in images. Yeah, I know that isn't a word, but some people will understand what I'm saying.
Because chrome uses the webkit to render HTML, you can be assured if it works in safari, it'll work under chrome, however it's rendering engine isn't up to scratch quite yet. I think writing applications that take advantage of it is similar to writing iPhone applications, remember chrome is expected to be adopted by android to make it similar to iPhone. That way it pretty much takes advantage of all those iPhone apps.
Would I install it as the browser of choice? not yet - but i'll certainly work on valid web pages that will render across all browsers.
One of our major customers has outlawed Chrome because it installs on the C drive without asking. They deploy a standard image with a small C drive and large D drive so they can easily re-clone the system part of the image on C without destroying the client's personal files on D. Most software allows you to choose the install directory. Anything that violates this is disallowed, and they're a big enough company to have some weight with most vendors.
We have enough headaches trying to support
Firefox
Two versions of IE which have their own iffy bugs
Safari
I'm not sure why we continue to support Safari. Most of our users (corporate) use IE6 or IE7. We try to make sure that things work in both of those.
Maybe not for programming purposes but Chrome w/ Google Reader makes for the most powerful RSS reader. Can handle up to 1500 feeds w/ performance still ok, managing subscriptions still functioning.
I'm using it on my work machine, but that's about it. It's been stable for me, and I like the barebones UI. I'll still switch to Firefox for the web developer extensions however.
I'm liking some of GoogleChrome- the Start page with your 9 most recent is the winner for me. The interface takes a little getting used to, but the speed is impressive, especially with Gmail.
However, it glitches with Java, which rules it out for serious work at the moment. I use FireFox mostly and have Chrome for the "other" websites at work.
I'm considering using GWT on an intranet project and considering suggesting to the users that use Chrome to take advantage of the enhanced Javascript performance. Any AJAX-heavy app would be a great candidate to target Chrome.
At my company, we're not targeting it, but we're definitely paying attention to it. My boss is using it as his primary browser, and I have implemented browser detection for it in our scripts in case we ever to need to target it for some reason.
Chrome has the .png opacity bug where the transparent parts of the .png are a solid color if you try to transition the opacity from 0 to 1. In IE7 the opaque parts are black, and in Chrome, they are white. Today, I decided to go ahead and account for this bug in my JavaScript. I don't really test sites on Chrome that often, but I am actually using it for almost all of my browsing.
I will target Chrome as soon as a stable Linux and OSX client is available.
Targeting Chrome/Chromium right now, I think is like targeting Konqueror web browser. It will get popular, but you should wait to a more stable beta, and/or some Linux and OS X client.
My website statistics shows 3.xx % visitors using Chrome which arrived just few weeks back. And Opera is only 4.xx % which has been around for several years.
Easily you can see that rate at which Chrome is picking up.
You can see how easily Google takes over all areas of your computing world and personal world too.
Since Chrome uses Webkit, it has the same rendering engine and DOM support as Safari (not necessarily the same revision of Webkit though). By testing in Safari, you can generally get by without worrying about Chrome. Any differences you find are probably just bugs that you should file on instead of work around.
However, because Chrome uses a different JS engine, there may be a few incompatibilities with Safari. So, if you're doing anything with JS, you might as well fire up Chrome and see if there's anything obviously wrong.
Generally though, you don't target browsers, you target rendering engines (with their associated DOM support and JS engines).
I am using Google Chrome, so far all the web apps I have work fine in it with no modifications.
No.
Why help Google further build an evil empire? In this particular case it is so obvious that they do not care about users but only obsessed with gathering usage info.
It's not any major player yet