I'm not sure if you understand the problem here. NS4 will NEVER give a mouseup
event for a layer other than the mousedown event. It simply does not happen.
For this reason, I believe that in the cross browser spirit of the API, we
should cripple the other browsers to make them perform the same. This would
create a standard mouse event environment in which to develop our widgets.
If you find a place where you require the non standard actions to be available,
simply add a mousedown listener to the document that null's the DynEvent.focus
value. This will stop the mouseup event from being redirected.
[EMAIL PROTECTED] wrote:
> >From [EMAIL PROTECTED] Fri Mar 16 15:22:08 2001
> >
> >i would prefer the other way, that ns acts as ie does.
> >there are situations where it makes a difference if the user releases the
> >mouse over another layers than it was pressed.
>
> I think I agree. These situations occur when the mousedown does
> not perform an action, other than possibly providing feedback.
>
> In other situations when the mousedown does start performing
> an action, such as dragging, then one does want to know what
> object the initial action was being formed on (or relative to).
> One may be interested in what object the mouseup occurs in, such
> as for a drop action, or sometimes it doesn't matter, such as
> for a scrollbar drag and release.
>
> To allow all these possibilities, it seems that the lowest level
> functionality should support what IE does: identify the object
> where the mouseup occurs. Applications (or widgets) that need
> to know what the mousedown object was should remember that as part of
> a higher level event, or whatever. The 'click' and 'double click'
> events are higher-level events where the mousedown and mouseup occur
> for the same object.
>
> I tried web searching for what other systems (e.g. Java, VB) do,
> but didn't find much. Usually it is just ambiguous what a
> mouseup event means.
>
> >an event should fire on the obj it occurs on, always!
>
> That seems clear enough. But we could define a higher-level
> event, called a drag-release or drop, that fires on the object being
> dragged, not just on the object being dropped on, or perhaps both the
> source and the target should be identified.
>
> >i don't know if it's possible to make ns acting as ie does, but i'd prefer
> >that at least ie acts how it should.
>
> Someone should track down whether mozilla considers its behavior
> a bug or a feature.
>
> It should be possible to map events either way, making either look
> like the other. It might be hard to deal with systems that only
> want to trigger events after specifically
> declaring that events should be captured for each element where they
> might occur. I don't care where a mouseup event occurs for a scrollbar
> drag, for example.
>
> --
> Daniel LaLiberte
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
> http://www.holonexus.org/~liberte/
>
> _______________________________________________
> Dynapi-Dev mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
--
Michael Pemberton
[EMAIL PROTECTED]
ICQ: 12107010
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev
