Issues with Ubiquity

3 views
Skip to first unread message

jay

unread,
Jul 28, 2009, 1:34:58 PM7/28/09
to ubiquity-firefox, Gabriel.Irv...@gmail.com
I've been running ubiquity for several months now without any
problems. With the latest release, however, I've seen a few issues.

The first is that typing a command and pressing enter won't bring up
the new tab with the results of the command unless I wait for the
preview to load first. For example, quickly typing 'wiki top gear'
<enter> essentially does nothing. Ubiquity closes and no new tab is
opened. If i type 'wiki top gear' , then pause for a second and wait
for the preview to begin loading, then hit enter... the new tab opens
correctly. This seems to be the case for all commands that open a new
tab, not just wikipedia.

Secondly, I've always used the newTabURL extension, which lets you
choose what happens when a new tab is open. I generally configure mine
so if I open a new tab, it loads to my home page by default. If I have
a link copied in my clipboard, it will load that link instead (but
only once). With the new version of ubiquity, this extension has gone
crazy. Opening a new tab seems to do something random every time.
Sometimes it loads my home page, sometimes it loads a page that I had
opened minutes or even hours ago, sometimes it loads blank, etc. I'm
not sure if this is really a ubiquity problem but things went awry
when ubiquity was updated.

Has anyone else run into problems like this?

jay

unread,
Jul 28, 2009, 1:36:13 PM7/28/09
to ubiquity-firefox
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.

jay

unread,
Jul 28, 2009, 2:19:21 PM7/28/09
to ubiquity-firefox
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!

"mitcho (Michael 芳貴 Erlewine)"

unread,
Jul 28, 2009, 2:23:23 PM7/28/09
to ubiquity...@googlegroups.com
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
--
mitcho (Michael 芳貴 Erlewine)
mit...@mitcho.com
http://mitcho.com/
linguist, coder, teacher

jay

unread,
Jul 28, 2009, 2:26:22 PM7/28/09
to ubiquity-firefox
It actually looks like installing newtaburl breaks ubiquity... so Im
holding off on installing that for now.
Reply all
Reply to author
Forward
0 new messages