×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
From: Pete Helgren
I guess someone who had an axe to grind with Microsoft and
didn't mind losing business could implement logic that would
only run on non-MS browsers.
I could admit to something here, but I don't want folks to think of me as devilish ...
More seriously, IE used to be my "preferred" browser, then I switched to FF, and I can see how developers can get zealous about one or the other.
Regarding the behavior of the Table component that I referred to in other threads, I needed to attach a "click" event-listener to "row" objects and refer back to the row object that was the target of the event. Firefox provides a reference to the row in the event currentTarget property. Easy!
IE events don't have a currentTarget property. They have a srcElement property, but if the row contains other elements, say another table for example, the reference in the srcElement property, may be referring to an element way down in the bowels of the DOM hierarchy.
You think, Blast! I just attached the event listener to a "row", but something I many not even be aware of in the bowels of the DOM hierarchy is triggering the event, and the event srcElement is pointing to it! So you write another layer of code to work your way up the DOM hierarchy. At each step, you ask "are you my mother", "are you my mother", "are you my mother", until you find her. And you have to come up with a kludge for identifying the right mother.
I suppose someone could come up with an example of how Firefox makes something harder, but the point is that you kind-of get a feel for your preferred environment and things are easier for you there.
Nathan.
midrange.com
