Web browsers differences: Difference between revisions
Jump to navigation
Jump to search
(→Opera) |
(→Opera) |
||
| Line 10: | Line 10: | ||
* location.hash is bugged when the hash contains a question mark. '''Update:''' this seems to have been fixed. | * location.hash is bugged when the hash contains a question mark. '''Update:''' this seems to have been fixed. | ||
* myForm.readAttribute("action") behaves differently in Opera, as it adds the hostname before (which is bad!). The bug was apparently fixed in Opera 9.50 ([http://dev.rubyonrails.org/ticket/10345 see this bug reference]). | * myForm.readAttribute("action") behaves differently in Opera, as it adds the hostname before (which is bad!). The bug was apparently fixed in Opera 9.50 ([http://dev.rubyonrails.org/ticket/10345 see this bug reference]). | ||
* Opera automatically adds margins to forms. | * Opera automatically adds margins to forms. | ||
* Opera does not fire the "load" event on an newly created image, which has already been downloaded (eg, whose source corresponds to an already fetched element). This is probably a bug that hopefully will be fixed. | |||
Revision as of 21:16, 17 March 2008
Internet Explorer
- Debugging JavaScript on IE is a lot harder than on FF. The best is to install Firebug Lite. However, you must not use console.log() before the window is loaded (else you'll get a very annoying fatal error saying IE cannot open the page).
- Only use Prototype JS code or you'll run into troubles (mainly because all elements should be extended Prototype elements to ensure cross-browser behavior).
- IE 7 automatically adds margins to forms. You can override that behavior with CSS.
Opera
- location.hash is bugged when the hash contains a question mark. Update: this seems to have been fixed.
- myForm.readAttribute("action") behaves differently in Opera, as it adds the hostname before (which is bad!). The bug was apparently fixed in Opera 9.50 (see this bug reference).
- Opera automatically adds margins to forms.
- Opera does not fire the "load" event on an newly created image, which has already been downloaded (eg, whose source corresponds to an already fetched element). This is probably a bug that hopefully will be fixed.