cross-browser

Cons of using Internet Explorer's Compatibility Mode

 ̄綄美尐妖づ 提交于 2019-12-01 14:33:55
问题 What are cons of force a web site viewed in IE to compatible mode? Say we force IE9 to IE8 compatiblity mode? Performance drawbacks Can't use any new IE9 specific features like HTML5/CSS3/SVG Why? We run legacy web app which is developed since 2000 so it's a mess ball fighting to be compatible with Chrome, Opera, Firefox, IE6/7/8 and now we decide to add IE9 to the list. But with IE9 we run in issues with printing, "Permission deniend" JavaScript errors (probably something about cross-frame

Footer not 100% bottom crossbrowser

非 Y 不嫁゛ 提交于 2019-12-01 14:32:06
This is my first question here, so bare in mind that we may have some issues with code. But the thing is that i'm using a template (Cant remember what template atm) that is supposed to work in every browser but i cant get the code to the bottom. URL TO SITE IN 1 Comment. I'm pasting the HTML & CSS with Pastebin for you people that don't wanna see the page. Please bare in mind that the CSS is rough and not clean, same with the HTML as the page is under development. I searched here a couple of times without result, and couldn't get it going without messing up the whole page. I can only test this

Status 500 Internal Server Error in IE-11 with Angular Js Application

混江龙づ霸主 提交于 2019-12-01 14:27:00
I am implementing single page application(SPA) using of Angular Js, MongoDb. And I am using rest call with promises. Rest call working fine in Chrome, Mozila browser which is using for development. But rest call is not working in IE-11. It is giving me 500 Internal Server Error . I am not able to find out line of rest call. Because it is not showing line number. But I can share sample code of rest call. Rh.all('apicall').get('dbname/_aggrs/'+ ar_dep +'?avars=' + query).then(function (d) { console.log("response data"); }); Above call is not printing console. Because It is breaking in IE-11, But

CSS3 arrow hyperlink

淺唱寂寞╮ 提交于 2019-12-01 14:22:38
Trying to make arrow link with CSS. This one works in Firefox, but has a problems in IE and webkit-based browsers with arrowhead's position. Double div used for centering link content. Any suggestions? content <a href="#" class="readmore"> <div> <div> link content </div> </div> </a> content CSS .readmore { text-decoration:none; } .readmore > div { display: table; height: 30px; //width: 100%; background: #008a00; transition: background 0.2s; } .readmore > div:hover { background:orange; } .readmore > div::after { content:""; display:inline; position:absolute; border: 15px solid; margin-top:-15px

Using conditional knockout templates with IE8

时光怂恿深爱的人放手 提交于 2019-12-01 14:06:03
问题 In all 'modern' browsers the following works but not in IE8: <!-- ko template: {if: $root.itemToEdit.SomeObject() === $data, name: 'EditItemTemplate', afterRender: $root.initializeEditPanel } --> <!-- /ko --> I get the following error: SCRIPT5022: Unable to parse bindings. Message: SyntaxError: Expected identifier, string or number; Bindings value: template: {if: $root.itemToEdit.SomeObject() === $data, name: 'EditItemTemplate', afterRender: $root.initializeEditPanel } It seems to be the

Firefox and Chrome seem to render box-shadow quite differently

点点圈 提交于 2019-12-01 14:04:53
问题 I was testing a box-shadow effect in both Chrome and Firefox and I was surprised to see a drastic difference in rendering between the two browsers. Notably, Firefox's rendering was much darker. Here are two reference images: The first image is rendered in Chrome 22, and the latter in Firefox 16, both running under Mac OS 10.8.2. I have no idea why the two images are rendering so differently. Here's the box shadow itself, same for both browsers: box-shadow: 0px 1px 3px rgba(0,0,0,0.3), inset

Footer not 100% bottom crossbrowser

自作多情 提交于 2019-12-01 13:25:57
问题 This is my first question here, so bare in mind that we may have some issues with code. But the thing is that i'm using a template (Cant remember what template atm) that is supposed to work in every browser but i cant get the code to the bottom. URL TO SITE IN 1 Comment. I'm pasting the HTML & CSS with Pastebin for you people that don't wanna see the page. Please bare in mind that the CSS is rough and not clean, same with the HTML as the page is under development. I searched here a couple of

html5 for IE8 or less

☆樱花仙子☆ 提交于 2019-12-01 13:21:52
I re-build my website with HTML5 tags Its working fine with FF,Chorme, and IE9 Its not working with IE8 or less. Do you know if there are any accentuation for IE8 (or less)? this is the website (Hebrew lang): http://www.switchbook.co.il Thank you al in advanced, Roi Use HTML5 Shiv to add compatibility back to older browsers. http://code.google.com/p/html5shiv/ Add this javascript to your site and it should work fine in IE 6, 7 and 8 https://github.com/aFarkas/html5shiv IE8 and before don't recognize all HTML5 elements. You can trick the browsers into recornising them using Javascript. You can

Firefox : There is no such field called inputType in keydown event object

可紊 提交于 2019-12-01 12:26:51
问题 I have an input event and a keydown event bound to a textbox in angular. In keydown event function I'm recieving an input object as the object representing the event in firefox. At the same time, I'm receiving an InputEvent object for the same event in chrome. I'm using the inputType field in the InputEvent object in chrome to identify if it is insertText , deleteContentBackward or deleteContentForward event as given below. switch(event.inputType) { case 'insertText': //do something break;

How can I check if cross-browser compatible? [closed]

混江龙づ霸主 提交于 2019-12-01 11:35:09
My humble question is if there is an online tool to check if your html/css & jQuery page is cross-browser compatible. I have a simple fade-hover effecr with jquery and it works perfect in Chrome, but what about the other browsers? Firstly, let me stress the point made in one of the comments, that it is really important that you actually test your site for yourself in all browsers that you wish to support. A third party tool simply cannot give you the kind of assurance you need that your site will work flawlessly in any given browser. Now to answer the question... You haven't stated whether