shadowkai97 / fauxbar

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

Cannot open new chrome tab on latest fauxbar upgrade #138

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Try and open a new tab or window (using cmd-t or cmd-n or the file menu)
2. window appears and immediately disappears

Mac OS 10.7.5
fauxbar 1.3.1
Chrome 27.0.1453.116

Original issue reported on code.google.com by Nicholas...@gmail.com on 7 Jul 2013 at 6:36

GoogleCodeExporter commented 8 years ago
Can you open Fauxbar's options?

Under General > Tab Override, can you try using Method 1 instead of Method 2?

Original comment by fauxbar....@gmail.com on 7 Jul 2013 at 7:43

GoogleCodeExporter commented 8 years ago

Original comment by fauxbar....@gmail.com on 7 Jul 2013 at 7:44

GoogleCodeExporter commented 8 years ago

Original comment by fauxbar....@gmail.com on 7 Jul 2013 at 7:46

GoogleCodeExporter commented 8 years ago
Even I'm facing the same problem.. Not only me I've seen many posts similar.
Kindly address this issue..

Original comment by pratik...@gmail.com on 7 Jul 2013 at 6:15

GoogleCodeExporter commented 8 years ago
On my Windows laptop I opened Chrome, saw the Fauxbar update, and tested the 
various ways a new tab could be opened while retaining focus on the Fauxbar 
address bar. All was good. I exited from Chrome. 

When I launch Chrome again the window appears and immediately disappears. I 
believe the mechanism which closes a regularly opened tab and reopens a Fauxbar 
tab in its place is is having the undesirable effect of closing the startup tab 
when it is the only tab, therefore closing the entire application. 

Original comment by jmajo...@booksforbusiness.com on 7 Jul 2013 at 7:54

GoogleCodeExporter commented 8 years ago
Okay, hmm, so a Chrome launch issue then. I don't think I tested that >_<

I'm away from my desktop at the moment, but to launch Chrome and bypass this, 
can you try:

1. Create a blank .txt document on your desktop
2. Rename the file to .html
3. Open the HTML file in Chrome?
Hopefully this will bypass Chrome's New Tab page until I push a fix.

I also wonder if (assuming the above works), if you go to Fauxbar's Options > 
General > Tab Override, select Method 1 -- does this setting let you launch 
Chrome without problem?

Original comment by fauxbar....@gmail.com on 7 Jul 2013 at 10:08

GoogleCodeExporter commented 8 years ago
The exact same thing happened the second time I launched Chrome from OSX. 
However on OSX Chrome remains open even if all the tabs are closed. 
(Screenclip: http://note.io/1bh03go) That allowed me to access extension 
settings where I set Fauxbar to open new tabs with Method 1. Now I can open 
Chrome loading a new Faxbar tab via Method 1. 

Method 1 may work on Windows as well but I can't access the extension settings 
with zero tabs open like I can with OSX. 

Original comment by jmajo...@booksforbusiness.com on 7 Jul 2013 at 10:13

GoogleCodeExporter commented 8 years ago
Thank you for the info.

I can confirm that opening Chrome with an HTML file (rather than launching 
Chrome normally) lets Chrome stay open. You can then access Fauxbar's options 
and select Method 1.

On Windows, Method 1 lets Chrome stay open with normal launching.

I will quickly disable Method 2 for v1.3.2 since this is quite critical, then 
will look at my options for letting Method 2 be usable again for v1.3.3 
hopefully.

Original comment by fauxbar....@gmail.com on 7 Jul 2013 at 11:32

GoogleCodeExporter commented 8 years ago
Also, after switching to Method 1, you will need to disable and re-enable 
Fauxbar for it to work again. Or close and restart Chrome.

Working on a fix now anyhow :x

Original comment by fauxbar....@gmail.com on 7 Jul 2013 at 11:40

GoogleCodeExporter commented 8 years ago
Fixed in v1.3.2.

I have added the instructions discussed above to the Help wiki page, if you're 
having trouble upgrading:
https://code.google.com/p/fauxbar/wiki/Help#Chrome_will_not_stay_open

Original comment by fauxbar....@gmail.com on 8 Jul 2013 at 1:11