From: Joachim L. <lu...@ho...> - 2001-07-15 14:23:02
|
At 2001-07-14 11:05, you wrote: >This doesn't look correct to me, if you test for the value of e.returnValue; >in IE5.5, it will always return "undefined", which will of course seem to >work, but it is actually always returning false. Quite so, my error. I don't know why it worked here in my test-case, I can't make it do it again! >Also, shouldn't the dom test be inside the same "else" clause as the ie >test? > >And using IE5+ wouldn't it first execute the IE clause, and then the dom >one? Blaim that one on cut&paste - don't test for "is.dom" but "e.preventDefault". >I'm surprised the mousemove test affected handleEvent, as it seemed to work >ok here, and seemed to resolve some annoying textselection problems >especially in NS4, I'll give it a try with your sample code. > >If you use this sample code, you'll see the textselection problem in NS4, as >you drag the blue layer: > > >DynAPI.onLoad = function() { > myLayer = new DynLayer('myLayer',0,50,50,50,'blue') > > DragEvent.setDragBoundary(myLayer) > DragEvent.enableDragEvents(myLayer) > DynAPI.document.addChild(myLayer) > > var clk=new EventListener() > clk.onclick=function(e) { > alert('hi') > } > myLayer.addEventListener(clk) >} ></script> ></head> ><body bgcolor="#000000"> ><a href="Message: Click this to test" onclick="status='woot!';return >true;">stuff</a> ></body> ></html> > >Richard. The textselection shouldn't happen since the draglistener does a cancelBrowserEvent() on mousedown and mousemoves (I think the latter is superfluous - it is here at least). I haven't made any changes to dragevent.js, all my checking/testing is done on mouse.js. If I remove the cancelBrowserEvent() in dragevent's onmousedown I too have the textselection bug. I will try to make this work during the next few days (I've given up on a simple solution - or at least an easy-to-find one). I'll let you know what I come up with (in DynAPI-dev instead). /Lunna |