At one point in time, mouseenter was only supported by IE. If we agree it is safe to use on all of our target browsers, we can switch to using it.
I don't think it will solve the flicker problem. I think the tooltips need to be "mouse transparent". My 2 cents, -Alex On 7/11/17, 4:32 AM, "Harbs" <harbs.li...@gmail.com> wrote: >My point with tooltip is that you probably don’t need bubbling for >tooltips and it causes more events than are needed. > >There’s use cases for both mouseover and mouseenter. > >Resolving Justin’s issues using mouseenter would require a couple of >things: >1, We would need mouseeenter (and mouseleave) events and not custom >ROLL_OVER events >2. The tooltip would need to be a descendant of the element which has the >mouseenter event attached to it. Otherwise, you’d get mouseleave events >when the mouse rolls over the tooltip. > >Fixing those two things seems to me like the ideal way to resolve the >performance issues. > >My question here is why are we not using the standard mouseenter and are >using a hacky solution for custom ROLL_OVER events instead. > >I think Alex wrote that code, so I’m going to wait until he can respond. > >Thanks, >Harbs > >> On Jul 11, 2017, at 1:50 PM, piotrz <piotrzarzyck...@gmail.com> wrote: >> >> Ahh..Yes. Maybe let's live it as is. Maybe if you will use in your app >> tooltips more extensively we will see. >> >> Piotr >> >> >> >> ----- >> Apache Flex PMC >> piotrzarzyck...@gmail.com >> -- >> View this message in context: >>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fl >>ex-development.2333347.n4.nabble.com%2FRe-2-5-git-commit-flex-asjs-refs-h >>eads-develop-FLEX-35338-stop-cursor-from-spinning-CPU-from-spiking-tp6306 >>1p63087.html&data=02%7C01%7C%7Cbed16583edd74d4d2a0708d4c860cd33%7Cfa7b1b5 >>a7b34438794aed2c178decee1%7C0%7C0%7C636353765461900518&sdata=Ia2G2yNdIScR >>cThmf9qfrnp%2Bue%2BkEvCmFDEooPHgnwo%3D&reserved=0 >> Sent from the Apache Flex Development mailing list archive at >>Nabble.com. >
