The most NS4 complains lately is about clicks being cancelled when
something is maka dragable. This is because event cancellation: this we
all know. If either mousedown or mouseup was cancelled, netscape does
not generate its click event ( something, that inspite of being
annoying, does make sense, since Netscape didn't know of the mousedown,
and without mousedown there is no click ).
Cancelling mouse events in the drag extension is OK. As well as it
happens with the label widget somewhere ( I think ). The proper way of
fixing this is having our mouse.js keep track of cancelled mousedowns
and mouseups so it generates a click when the browser does not. Please
don't think of modifying widgets or extensions or pieces of your own
code. If an event does not work ok, the place to fix that is in the
API's event code. The API should provide a robust event code, we should
avoid any other checks outside it.
I'll try to do it today.
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev
