Hi Jay, Thanks for doing all that digging around! Yes, we're actively working to improve Parser 2 performance and to explore different approaches to improving the immediate-enter behavior (#838).
mitcho > > Did some additional digging around and it looks like the second issue > was a problem with newtabURL that was corrected today. > > https://addons.mozilla.org/en-US/firefox/addon/2221 > > Also, I realized I could get around that initial bug by going to > ubiquity's settings and disabling Parser 2. So you don't get the new, > experimental parser... but all the functions work as advertised with > no lag. > > Hopefully they'll get that bug fixed in Parser 2 and pushed into a new > release soon! > > > On Jul 28, 1:36 pm, jay <[email protected]> wrote: >> Ahh, looks like the first one is a known bug: >> >> http://ubiquity.mozilla.com/trac/ticket/741 >> >> The second one may have more to do with newtaburl than ubiquity. Or >> maybe they just don't play nicely any more. > > -- mitcho (Michael 芳貴 Erlewine) [email protected] http://mitcho.com/ linguist, coder, teacher --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "ubiquity-firefox" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/ubiquity-firefox?hl=en -~----------~----~----~----~------~----~------~--~---
