On 8/15/2014 3:27 PM, Neil wrote: >> It soon became apparent that most of the autocomplete code was >> designed for synchronous operation >> > Synchronous operation of what? Autocomplete works like this: You ask for > some results; some time later, you get some results. How could that be > less synchronous?
We've found race conditions due to the fact that only one popup is expected to be open at any given time, with its associated search, and everything is handled by a global service. So yes, "synchronous" is not the right word, maybe "non-concurrent" may give a better idea. Anyways, the concept is that reworking and simplifying the interfaces will reduce the chance of having new bugs of this type. > *SeaMonkey's search bar uses toolkit's autocomplete widget but > SeaMonkey's popup. You're saying that it manually binds to Toolkit's autocomplete.xml? The binding in xul.css is between an #ifdef for SeaMonkey, thus I assumed it was unused. Paolo _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
