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.
Related
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.
I'm developing a mobile site using AngularJS (v 1.5) and it doesn't load in Opera mini. So I started searching and found one article about how Opera mini is a proxy based server and it stripes maximum JavaScript data.
But except that one article, I haven't seen it stated explicitly that Opera mini isn't supported, so I'm a bit confused.
I know Angular 2 is supposed to be released with the view of mobile-first architecture, but does Angular 1.x support opera mini?
Thanks in advance.
It seems Opera mini no longer supported by AngularJS. Check this:
https://mobiforge.com/news-comment/angularjs-to-opera-mini-youre-just-not-worth-it
Edited:
Quoting from AngularJS FAQ (latest stable v1.5):
What browsers does Angular work with?
We run our extensive test suite against the following browsers: the
latest versions of Chrome, Firefox, Safari, and Safari
for iOs, as well as Internet Explorer versions 9-11. See
Internet Explorer Compatibility for more details on supporting legacy
IE browsers.
If a browser is untested, it doesn't mean it won't work; for example, older Android (2.3.x) is supported in the sense that we avoid
the dot notation for reserved words as property names, but we don't
actively test changes against it. You can also expect browsers to work
that share a large part of their codebase with a browser we test, such
as Opera > version 12 (uses the Blink engine), or the various Firefox
derivatives.
I built a web app using some technologies that do not work well for IE 8/9. The app functions well in Chrome and Firefox and mostly okay in Standard IE 10 but breaks down in IE 8/9 standard. However, if I switch over to quirks mode for IE 8/9 in the developer console, it works perfectly for some reason. Is there a danger to trying to force quirks mode for older IE?
Well I would say that it's definitely not optimal and you should be trying to fix the errors that prevents you to run in standard mode, however if you are unable to do it and it's the only way to go, I do not see how a working application running in quirks mode could be worse than a failing application in standard mode.
I get reports that a button does not work in my webapp on IE8 (and older). Everything works in IE9, FF and Chrome. The error is triggered in this click-bind:
$("#save_refresh").click(function(e) {
alert('hello world!');
});
This is the html:
<input class='button' type='button' value='Save / Refresh' id='save_refresh' />
When clicking the button in IETester running IE8, the "hello world!" is not shown and I get this error:
Line: 17
Character: 28691
Error:
Code: 0
URL: jquery-1.6.1.min.js
So my question is:
is there anything wrong with my above code OR does anyone know how to debug javascript in older version of IE.
I agree with Quentin. You should download one of Microsoft's Internet Explorer Application Compatibility VPC Images to properly test your code. Paul Irish has a good article on the incompatibilities of Internet Explorer compatibility modes.
The IE9 compatibility modes are unreliable in terms of giving you an accurate picture of how the browser will actually render your page and how your page will behave under that browser. It's like putting a Chevrolet Metro engine in your Chevrolet Aveo so you can test drive the Metro.
That said, when using IE8, you can just hit F12 like in IE9, but with IE7, you need to have a copy of Visual Studio and use the debugger keyword.
Microsoft provide virtual machines with older versions of Internet Explorer for testing.
Using IE9, you can switch to the IE7 or IE8 rendering engine. Press F12 and the developer panel should appear. The header bar has options to switch to the IE7 and IE8 Browser Modes (and their respective notorious Quirks Modes).
For IE6, you'll have to rely on Virtual Machines (as mentioned by Quentin above). Microsoft released XP Mode partly for this.
Internet explorer has compatibility mode for IE7 and IE8 (and even for Quirks mode), it which you can debug most of the issues. Rarely you need true installation of older version of IE
The Zepto.js website says:
Zepto.js is a minimalist JavaScript framework for mobile WebKit browsers, with a jQuery-compatible syntax.
Is it only recommended for use with apps that will be used on mobile devices or can it also be used in traditional computer browser web apps as well? What are the downsides of doing so?
I use jQuery a lot in my regular web apps (for computer browsers) and I've realized (after finding Zepto.js) that I don't always use all of jQuery's features, so Zepto.js is perfect for what I do.
Also, why is there focus on the 'WebKit' engine? Does it not work with mobile Internet Explorer on Windows Phone 7, Firefox Mobile on Android or Opera Mobile?
EDIT: The presence of $.os.android in addition to $.os.ios indicates that there is support for non-iOS platforms, so the last question is answered!
EDIT (final): I guess the real question is "Can the Zepto.js library, intended for use on mobile WebKit-based browsers, be used as a lighter-weight alternative to jQuery for the desktop also?" The answer is no.
Note: This answer is old, and not up to date anymore. Yes, Zepto started as a webkit-only, mobile-specific framework, but it has evolved since then as EBarr points out below.
So always check Zepto's website for the most up-to-date information.
Not to sound too harsh, but did you click the big button on the site to see the presentation?
You basically already answered the questions:
Yes, it's for mobile devices. Support for swipe and tap events doesn't exactly make sense on a desktop computer, where you use a mouse.
Yes, it's for WebKit specifically, because that's what's most used for mobile browsing. That means no support for IE/Firefox/Opera - mobile or desktop. As the presentation says, "No one is running IE6 on an iPhone". Most desktop-browser JS libraries exist specifically to eliminate browser differences. Zepto does the opposite.
jQuery is an offroad truck: Enormous but very capable both on- and off-road.
Zepto is a Formula-1 car: Small, fast, and built exclusively to be great on the racetrack, so it won't work right in any other situation.
It seems that Zepto's purpose has evolved. The site now notes :
Note that some optional features of Zepto specifically target mobile
browsers; as the original project goal was to specifically provide a
leaner alternative to jQuery on for the mobile web.
It lists the following as target platforms (note the inclusion of desktop browsers):
Browser support
Primary (100% support)
Safari 6+ (Mac)
Chrome 30+ (Windows, Mac, Android, iOS, Linux, Chrome OS)
Firefox 24+ (Windows, Mac, Android, Linux, Firefox OS)
iOS 5+ Safari
Android 2.3+ Browser
Internet Explorer 10+ (Windows, Windows Phone)
Secondary targets (fully or mostly supported)
iOS 3+ Safari
Chrome <30
Firefox 4+
Safari <6
Android Browser 2.2
Opera 10+
webOS 1.4.5+ Browser
BlackBerry Tablet OS 1.0.7+ Browser
Amazon Silk 1.0+
Other WebKit-based browsers/runtimes
EDIT
List above updated to reflect reality as of January 2013.