[Chameleon-dev] [Bug 159] [cwc2 1.0.4] query re-submitted unexpectedly

[bugzilla-daemon@www.maptools.org]

http://www.maptools.org/bugzilla/show_bug.cgi?id=159

spencer@dmsolutions.ca changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |chameleon-
                   |                            |dev@lists.maptools.org
         AssignedTo|chameleon-                  |bronsema@dmsolutions.ca
                   |dev@lists.maptools.org      |



------- Additional Comments From spencer@dmsolutions.ca  2003-12-09 20:03 -------
This is an interesting bug.  Basically, it has to do with something called
'event bubbling' in javascript (which is handled differently by all browsers). 
You should get the same effect if you select the zoom in tool, then change the
time (without zooming in), you will zoom in.  The dropdown combo for the time
widget appears over the map, when you click on an entry, a mouse click event is
generated that is handled by various event handlers.  In some browsers, if a
custom onclick event handler is provided, then the default behaviour is to pass
the event to other objects in the page that contain the mouse unless one of the
event handlers explicitly cancels it.  In the case of chameleon, the main mouse
event handlers related to the map are actually registered at the document level,
which means that any event that occurs will eventually bubble to these functions
unless canceled - hence if you click on a select item that overlaps the map, and
the event handler doesn't cancel it, it will appear to chameleon as if the user
clicked on the map.  The same effect happens with the scrollbar in some
browsers.  If a navigation tool (or query) is selected, and either scrollbar is
over the map and the user scrolls the scrollbar, then the mouse click ends up in
the chameleon event handler even though it shouldn't.  There is no known
work-around for this problem.  However, in the case of the time widget, I think
that we can add code to the onclick event handler to prevent the onclick event
from being propogated to other objects in the page.

Reassigning to Bill since he worked on this widget.  Bill, discuss with me when
you get to this one.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are on the CC list for the bug, or are watching someone who is.