Its a stacking context issue! Even though you are using z-index on the dropdown, it is only relative to elements in the same stacking context. You need to add a z-index and a position to a parent element in order to get this to work. In this case I would recommend the header-top div
If you add this to your meta tags: <meta http-equiv=”X-UA-Compatible” content=”IE=EmulateIE7″ /> IE8 will render the page like IE7.
There is a simple hack to this: Insert a hidden input field in the form with an entity which only occur in the character set the server your posting (or doing a GET) to accepts. Example: If the form is located on a server serving ISO-8859-1 and the form will post to a server expecting … Read more
Internet Explorer does not send form fields if they are posted from an authenticated site (NTLM) to a non-authenticated site (anonymous). This is feature for challange-response situations (NTLM- or Kerberos- secured web sites) where IE can expect that the first POST request immediately leads to an HTTP 401 Authentication Required response (which includes a challenge), … Read more
The User-agent string for IE 11 is currently this one : Mozilla/5.0 (Windows NT 6.3; Trident/7.0; rv 11.0) like Gecko Windows 10 example: Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko Which means your can simply test, for versions 11.xx, var isIE11 = /Trident.*rv[ :]*11\./.test(navigator.userAgent); As IE10 user agent was Mozilla/5.0 (compatible; MSIE 10.0; Windows … Read more
I’d suggest one tweak to crescentfresh’s answer – use document.implementation.hasFeature(“http://www.w3.org/TR/SVG11/feature#BasicStructure”, “1.1”) rather than document.implementation.hasFeature(“http://www.w3.org/TR/SVG11/feature#Shape”, “1.0”) to detect SVG. WebKit is currently very picky about reporting features, and returns false for feature#Shape despite having relatively solid SVG support. The feature#BasicStructure alternative is suggested in the comments to https://bugs.webkit.org/show_bug.cgi?id=17400 and gives me the answers I expected on … Read more
Yes there is a way, the same way you make any css compatible: use a specific css fallback that is supported by the browser. body { –text-color: red; } body { color: red; /* default supported fallback style */ color: var(–text-color); /* will not be used by any browser that doesn’t support it, and will … Read more
As pointed out by Remus Rusanu, PowerShell would be the way to go. Here’s a simple one-liner that you can use to create a scheduled task, without needing to write a separate .ps1 file: powershell -ExecutionPolicy Bypass -Command Invoke-WebRequest ‘http://localhost/cron.aspx’ -UseBasicParsing Note that line breaks are added only for clarity in all of these command … Read more
Does one of the subdomains use an underscore? IE has problems accepting cookies from subdomains that don’t follow the URI RFC.
The page you link to has a compatibility table. Chrome 1.0 (-webkit prefix) Firefox 4.0 (2.0) (-moz prefix) 16.0 (16.0) (no prefix) Internet Explorer 10.0 (no prefix) Opera 10.5 (-o prefix) 12.0 (no prefix) Safari 3.2 (-webkit prefix) There is also an article on MSDN about CSS3 transitions in Internet Explorer.