Robert (and all),
> I believe the right click context menu disabling
> can be removed. I don't see why it is needed.
> Unless it kills the events, it should be
> removed since it doesn't work cross-browser
> anyways.
> --
> //Robert Rainwater
Right-mouse click menu disablement can be cross-browser.
As you might know, I have been working on fixing most of the existing (known) bugs
with the current release, as well as implementing the DynaCore's DynObject,
reorganizing package structure, and adding some extras that I have noticed have been
"lack-of feature" complaints in the past.
One of the things that I have done is to make the right mouse event disablment
cross-browser (I have tested this on IE4+ & NS4+ on the Windows OS), and made it
optional. You can disable-enable the right menu, on the fly.
Anyway,
I have a question about events/our EventMethod...
(some of the below has been a reference from Scott Andrew's web site --
scottandrew.com -- in the Netscape 6 Events article)
In Netscape 4, events will travel inward towards the target of the event.
window --> document --> layer --> childlayer(target)
In Internet Explorer, events travel outward towards the browser window.
childlayer(target) --> layer --> document --> window
In Netscape 6, events start at the window and travel to the target element (event
capture). But upon reaching the target, the event travels backward the way it came,
until it reaches the browser window again (event bubbling).
window --> document -->layer --> childlayer(target) --> layer --> document --> window
So, I beleive (and I could be wrong, so please correct me if I am) the model that we
are wanting to use is the IE's target to document to window. You might think that
events are working in NS6 with the current release, but they are not. Upon closer
examination and testing with very extensive examples, the events to not trigger
correctly. Well, I have fixed the event's in NS6 (the reason everything was happening
more than once is the fact that there is more than one event phase -- 3 actually). But
the problem is NS4's window to document to target. If we want the events to behave in
the same way cross-browser in very complex examples/widgets that uses bubbling, than
we need to reverse the way that NS4 captures events (like IE's), and then use our own
event bubbling method for the bubble (like in IE).
HERE IS THE QUESTION: ** What are thoughts on this? **
I have been working on a method that will do this, but I am still ironing out bugs.
By the way,
Part of my reorganization consisted of breaking away mouse events form the events.js
file, and making it a sperate "mouse.js" file.
This way, you can still have create/delete/resize/etc... events get triggered, but not
have to worry about the weighing down the code/processor with mouse events, if they
are unecessary. (Plus, I saw this as being consistant with some if the file structure
now, ie. keyevets.js).
Also, because it they are required by the DynAPI (dynapi.js), I have made certain
files (document.js, object.js, events.js) be automatically included when you set the
library path.
PLEASE, anybody that has any thoughts on this, reply! :-)
--proteanman
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev
