Posts about Crossbrowser

This is well-known knowledge, but I since it was not to me, I'll still catalogue it here. When you use a CSS selector with multiple class names on the same element, i.e.:.class1.class2{ ...}IE 6... more

If you try to eval a JSON string that has special characters in it(non-ascii, or chr > 127), it will error out. The other browsers work fine. more

'abc'[0]

more

Man! Have I been at war with IE lately. I have been holding back a lot of blog posts related to debug IE problems, and I going to start spewing them out now one by one. For the first installment I'll... more

IE, are you kidding me?
more

If you register the change event for a radio button, they fire at different times between IE and FF. FF fires the event immediately when you click on the radio button to change its value. IE does... more

If you write an input element like this:<input type="text" id="name" name="name" value="></input>In IE, if you try to traverse the dom, you will get the end-tag as a separate element... more

If you use a button element as a submit button in a form, like:<button id="mybutton">My Button</button>$('mybutton').value in FF will get you an empty string whereas in IE you would get... more

Since Chrome is so great, I wanted to use it for all my browser needs. But the apps I've been working on myself have not been targeted for WebKit - the rendering engine used by chrome, and also used... more

function.toString() has different behavior between IE and FF. FF collapses the parameter list onto one line, while IE leaves it untouched. Ex:function f(  param1,  param2, ... more

If you use the button element, make sure you set the type attribute:
<button type="submit">Submit</button>

Otherwise, it won't submit it's parent form when clicked in IE.
more

I haven't dug down to the bottom of this but basically Element.descendantOf(elm, ans) gives different results from IE vs FF.
more