I have a site which should compatible with multiple browsers, like IE7 & IE8 & others.
I choose to use conditional stylesheet to deal with different version of IEs.
Like this, only include ie7.css if current browser is ie7.
<!--[if IE 7]>
<link rel="stylesheet" type="text/css" href="/resources/css/ie7.css" />
<![endif]-->
I use IETester to test the performance of my site and make change for specific version of ie.
Everything look fine and consistent in IETester.
But, when I use the 'F12' tool of IE11 and change the version of IE, the appearance of my site scared me, element's position are disordered and looks ugly.
It seems that my conditional stylesheets(like ie7.css) do not loaded cause I do not see the ie7 styles displayed in the DOM Explorer.
Is this a IE11 bug ? or something else?
anybody knows?
There was a bug in F12 where conditional comments aren't respected when using F12 to set the document mode. This bug was fixed in the April update to IE11. If you run Windows update to get the latest patch you shouldn't see this issue any more.
http://connect.microsoft.com/IE/feedback/details/806767/conditional-comments-do-not-work-when-emulating-document-modes-via-f12-developer-tools
Related
Say I wanted to support IE11 (and sadly, I do), how would I go about making gatsby develop work on that poor old browser?
Right now, I get this message:
webpack-hot-middleware's client requires EventSource to work.
This polyfill looks promising, but that's as far as I've made it.
Any help?
P.S. Probably worth mentioning that I'm using Gatsby v 2.4.7
Looks like Gatsby doesn't support IE in development, only in production, so no polyfills will be added and IE will error when using gatsby develop.
https://www.gatsbyjs.org/packages/babel-preset-gatsby/
Can confirm on my project that running gatsby develop doesn't make it work for IE11, but using gatsby build does. When running gatsby develop, all I could see on IE11 is a blank page.
As per the documentation of Gatsby, You need to use babel 7.
Babel helps ensure the JavaScript you write works across different browsers (including older versions of Internet Explorer).
Reference:
Babel 7 (Gatsby)
Gatsby leverages Babel 7’s ability to automatically add polyfills for your target browsers.
Newer browsers support more JavaScript APIs than older browsers. For older versions, Gatsby (via Babel) automatically adds the minimum “polyfills” necessary for your code to work in those browsers.
If you start using a newer JavaScript API like [].includes that isn’t supported by some of your targeted browsers, you won’t have to worry about it breaking the older browsers as Babel will automatically add the needed polyfill core-js/modules/es7.array.includes.
Reference:
Browser Support
I have a very simple page that includes webcomponents-lite.js polyfill v1.1.1 and polymer.html v2.6.0. I open the page, served through polymer serve, in IE11 or Edge. When I open F12 tools, it takes up to several minutes until the tools are ready and responsive. This makes it extremely frustrating to debug IE compatibility issues. What is the cause? Can it be improved?
The same problem occurs in earlier versions of webcomponentsjs and polymer. Including webcomponentsjs alone does not seem to have the effect.
With Firefox discontinuing the use XUL overlay it raises concerns that Selenium IDE requires this overlay to function. Can anyone confirm one way or the other?
Mozilla Will Deprecate XUL Add-ons Before the End of 2017
Selenium IDE is definitely an overlay/XUL based add-on. It contains an instal.rdf file and chrome.manifest file which uses the overlay directive.
Mozilla has stated that all types of extensions, other than WebExtensions, will be disabled in the near future. They have stated that the target for this is the 2017-11-14 release of Firefox 57. This deprecation may include complete themes, which they have stated "we will provide more details on what’s coming for themes very soon". That XUL based extensions would be deprecated was announced on 2015-08-15. The fact that they would be disabled in Firefox 57 (late 2017) was announced on 2016-11-23.
Mozilla has previously stated that such add-ons will not be explicitly disabled in Firefox Developer Edition and Nightly. However, a primary reason for deprecating such add-ons is that Mozilla wants the freedom to change the underlying Firefox code without worrying about add-on compatibility, other than WebExtensions. Thus, Firefox may change such that the features such add-ons rely upon are no longer available. Another alternative would be to use an Extended Service Release (ESR) version of Firefox. Firefox ESR 52 will be the current ESR at that time. My answer to "How to develop legacy Firefox add-ons in the future?" has more detail about possible options for continuing to use legacy add-ons.
I have not seen anything from Selenium IDE describing their plans for this change.
With jQuery 2.0 Beta 2 being released meaning support for IE > 9 and other browsers how are people handling the bundling and minification for the various jquery versions.
jQuery 1.9 = IE6-8
jQuery 2.0 = IE9 and other browsers
jQuery suggests to use this:
<!--[if lt IE 9]>
<script src="jquery-1.9.1.js"></script>
<![endif]-->
<!--[if gte IE 9]><!-->
<script src="jquery-2.0.0b2.js"></script>
<!--<![endif]-->
But what if you wanted to bundle jQuery, will you have to create 2 bundles one containing one version of jquery say v1.9 and one containing 2.0 and Use Rquest.BRowser?
DotnetShadow
Why do you want to use different jQuery versions for different browsers?
Why not use 1.9 for all browsers?
Unless you have a very string reason to use two different versions, you'd be better off using just 1.9.x which is valid for newer and older browsers.
If you still want to use both versions, yes, you have to use two different bundles, and decide which one to render depending on the requesting browser.
However I still think it's safer to use the version which works for all version of browsers, even if the library is "a little less smart".
The only reason which could be in favor of using 2.x would be that 1.9.x hadn't support in the future, but that's not the case.
I'm trying to install Fireshot addon in opera version 11.62. bt it is not available on opera. Actually fireshot is the extension use for taking screenshot of the current locating site so to make report on the site. so is their any option beside that or can i install Fireshot on it?
Fireshot is a Firefox extension, I don't believe it's available as an Opera extension. You could try installing Lightshot, which sounds like it tries to do something similar (though some of the comments make it sound like it's a bit dodgy), or one of many third-party apps like Screenshot Captor.
Right now it is NOT possible for an Opera extension to do it, though we are working on exposing such functionality in the future through extensions.