shadowkai97 / fauxbar

Automatically exported from code.google.com/p/fauxbar
0 stars 0 forks source link

Focus from Omnibar too slow #122

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
1) Cntrl-T to open a new tab
2.a) Omnibox receives focus
2.b) Start typing my URL (google.com
3.a) Fauxbar takes focus
3.b) Continue typing the URL

Result:
Omnibar has something like: go
Fauxbar has something like : oogle.com

Desired Result: Fauxbar has google.com

When I open a new tab I start typing the url immediately, but fauxbar seems to 
have a small delay of like 100ms between opening the tab, the omnibar receiving 
focus and then fauxbar taking focus. In this amount of time I often start 
typing a URL but then Omnibar get's focus and captures the remainder of the 
input, leaving me with two incorrect searches

Is there any way to avoid this, perhaps by creasing the delay to focus on the 
fauxbar? Or by somehow capturing user input on the omnibox?

Thanks!
Version 20.0.1132.57 on OS 10.7

Original issue reported on code.google.com by nth...@gmail.com on 27 Jul 2012 at 2:30

GoogleCodeExporter commented 8 years ago
This happens to me sometimes. I've tried to make Fauxbar's page load as fast as 
possible (I still think it's faster-loading than Chrome's default new tab 
page!) but it's not always fast enough. Depends on what Chrome and/or the rest 
of your computer is doing, too :(

As far as I'm aware, there's no Chrome API to get the Omnibox's current text, 
so it's best to try and wait until you see that Fauxbar's page has gained focus 
before typing. Annoying, I know.

Marking this as WontFix because really it comes down to processing speed, which 
fluctuates. If an API to grab the Omnibox's text comes along, I'll open this up 
again.

Original comment by fauxbar....@gmail.com on 8 Aug 2012 at 12:49