On 30-Apr-08, at 3:22 PM, Colin Clark wrote: > Hi Michelle, > > Thanks for sending out this preview. Despite the bugs, I'm impressed > with how quickly you were able to inject the new layout behaviour. > > On 30-Apr-08, at 10:57 AM, Michelle D'Souza wrote: >> One of the problems with the new example is that it also showcases >> one >> of our evil bugs. :) The bug is that the drop target shows up >> somewhere but the portlet drops elsewhere. >> http://issues.fluidproject.org/browse/FLUID-407 It's quite a tricky >> little bug from a technical standpoint because the underlying problem >> is that we are getting browser events in the wrong order. We have a >> strategy for working around this issue but it is quite complex and >> will take a while to implement. > > Can you give us an overview of the fix you're considering? How will > it work?
The idea is to stop watching the browser events for which drop target we are over and instead calculate the mouse position and figure out what is beneath it. This has some extra difficulties when we start looking at nested drop targets since the mouse pointer may be above any number of drop targets and we will need to determine which of the drop targets is on top. I have been looking at the bugs in the example and it's possible that once FLUID-563 (http://issues.fluidproject.org/browse/FLUID-563) is fixed FLUID-407 may go back to being a rare occurring bug. Michelle ------------------------------------------------------ Michelle D'Souza Software Developer, Fluid Project Adaptive Technology Resource Centre University of Toronto _______________________________________________ fluid-work mailing list [email protected] http://fluidproject.org/mailman/listinfo/fluid-work
