Fast Dial support question
chiaroscuro —Tue, 10/14/2014 - 02:34
The following has been reported by a Fast Dial User Mysha
I'd like to use Fast Dial as the content of empty tabs. There's one problem with that, though: When I start a new search, I add a new tab, click on the search field, type the terms, and press enter. This works fine with Firefox' dialer. However, when I have Fast Dial on those tabs, I find that during this process my input gets hijacked, and I end up with only half the input ti the search bar, or with part of my input together with one of the dialer's URL-s in the addressbar.
It looks like Fast Dial moves the cursor to the address bar at some point., with that point not being very early. The Firefox dialer does so much earlier, apparently, and will than leave it alone while I move the cursor and enter the query, even though it's often still loading thumbnails by the time I hit enter.
If that's the problem, is there a way to have Fast Dial do this at some earlier point in the process, so it won't interfere with input?
Search logos
Search site
Navigation
User login
Online users
Recent comments
-
by: sijiv317594 hours 34 min ago
-
by: sijiv317595 hours 44 min ago
-
by: wakawaka6 hours 17 min ago
-
by: wakawaka6 hours 47 min ago
-
by: wakawaka6 hours 56 min ago
-
by: peter65410 hours 50 min ago
-
by: sijiv3175910 hours 54 min ago
-
by: wakawaka14 hours 23 min ago
Re: Fast Dial support question
Submitted by chiaroscuro on Tue, 10/14/2014 - 11:07I would like a little help
Everyone uses Firefox/Fast Dial differently
When you open Firefox what to you see
That is what is your home page
Is one to suppose that it is not Fast Dial ?
However, when I have Fast Dial on those tabs, I find that during this process my input gets hijacked, and I end up with only half the input ti the search bar, or with part of my input together with one of the dialer's URL-s in the addressbar.
I do not understand this. Or rather when I try to reproduce I am not sure that what I am doing matches your actions.
Re: Fast Dial support question
Submitted by Deva on Tue, 10/14/2014 - 12:07Yes, homepage is not a fastdial page. Fastdial embeds itself into a blank page, or rather a browsers "Quickdial" page.
I cannot reproduce this on my setup, using Firefox or Pale Moon. Tried writing into address bar, browsers search bar and FastDials search bar, all right after opening a new FastDial tab. In multiple tries never had my typing focus hijacked anywhere else but the place I started to write into.
I'm not understanding if the focus is lost from the browsers search to the address bar or into FastDials search bar, or the other way around.
For me, it looks like the part about thumbnails not being loaded up right away can give us a clue that something is slow at loading an empty tab. Is this happening even if the FastDial is opened for some time or only if typed right after opening FastDial?
Re: Fast Dial support question
Submitted by gumanov on Wed, 10/15/2014 - 03:40I remember this issue.. I had the same exact thing happen to me before - in fact there may be a discussion on the site here somewhere about it.
It was an older version of Fast dial, around when the search box was first introduced. Telega had fixed this though, long ago.
I'll see if I can find out which version this happened in.
Re: Fast Dial support question
Submitted by gumanov on Wed, 10/15/2014 - 05:29Here it is:
http://www.userlogos.org/forums/support/fast-dial/08052008/after-selecti...
Maybe this is unrelated though...
Re: Fast Dial support question
Submitted by telega on Wed, 10/15/2014 - 11:07It looks like Fast Dial moves the cursor to the address bar at some point., with that point not being very early.
You are right, Fast Dial moves cursor to the address bar because some people who have Fast Dial as homepage want address bar focused. When Fast Dial is displayed in a new tab, this isn't needed, because Firefox focuses addressbar. You can fix the problem by editing Fast Dial code:
- Unzip the Fast Dial .xpi file, find fastdial.html file inside and edit it.
- Find the line "if (!params.folder) wnd.gURLBar.select();" and remove it.
- Save your changes, zip the .xpi file again and install. This should fix the problem.