|
> From: Anton Gombkötö > > That's really annoying. Something works great in one browser and the > other(s) drive you mad... > > It's always irritating to have a 'solution' that doesn't work in every > environment. The big issue here is the support for the Document Object Model (DOM) and event handling. While Netscape claims "full compliance" with the DOM, the truth is that IE is far more friendly for programmers. Most events in IE are modifiable - for example, you can change keystrokes. Many of the common attributes of events in Netscape are read-only. For example, it's quite easy to switch a lower-case keystroke to uppercase in IE, but nowhere near as easy in Netscape. The other issue is event handling. The two browsers work entirely differently. Netscape "bubbles" events, while IE has listeners. Or is it vice versa? I had to step back away from it out of sheer frustration. The only real way to do it is to have separate JavaScript functions for each browser. That's actually doable, though, using JavaServer Pages, because you can change the CSS reference dynamically. But it really is frustrating. Joe
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
