If you can come up with a single reason for not including my patch, then show me an example that needs the obscure event structure and write me some code that will allow NS4 to behave like IE and NS6.
As I've stated in another post, NS6 also behaves slightly different to IE when it comes to event hadling also. eg. If the mouse leaves the layer while the mouse is down, a mouseout event is not triggered. When the mouse is released while still outside the layer, a mouseout event is triggered in IE only. This means that any code required on mouseout, will not be triggered by NS6. Call it a bug, call it a feature, this is still something that should be fixed in our code.
[EMAIL PROTECTED] wrote:
Here's one for this argument then.If we are saying that we will DE-EVOLVE all browsers to support a single
browser then why not DE-EVOLVE the whole thing so it supports everything from
NS 2.0 and IE 3.0 and up? This is the logic that we are using right?I know, I know, I can hear the arguments already; "That's not the point",
"Get Real", etc.My point is that if NS 4 doesn't support it then note it. But don't
DE-EVOLVE the features that are supported by all other browsers. I would
think that this would be a simple thing, if the browser doesn't support it
then find a way to work around it.And I realize the arguments have already been made concerning support for
older browsers, but lets face it people. This is not the dark ages of
computing anymore. The newer browsers do support more advanced features and
if we choose not to support those features because an older browser doesn't
support them then we will be condemning the API to a M$ style death; slow and
agonizing.People will not use something that refuses to support newer technology and
implementations of web standards. The DynAPI will not gain the popularity
that everyone wants. I use the DynAPI for some fairly simple stuff. But I
use it because it works and makes my job easier. That is what makes the
DynAPI what it is. And I know that everyone thinks that the people using
this are the average Joe who doesn't have a ton of technical knowledge, but
thats not true. The people who use this have technical knowledge and have
the ability to go off and create a script that will be exactly what they want
and provide the limited amount of use they need. But then they have to do
more work to keep it updated and running. The DynAPI is used by technology
professionals who don't have the time to devote to a project that provides
cross-browser API.Simply put, If you want the DynAPI to succeed and to become something that
will be used by more people, then you cannot DE-EVOLVE features.J
--
Michael Pemberton
[EMAIL PROTECTED]
ICQ: 12107010
