"Open Fauxbar in current tab" option not being remembered

[GoogleCodeExporter]

To submit a bug report, please answer the questions below.
Or if this is a feature request, the questions below can be deleted :)

What steps will reproduce the problem?
1. Set the "upon clicking the (@) icon, open Fauxbar 'in the current tab'

What is the expected output? What do you see instead?
Fauxbar should open in the currently opened tab, but instead loads in a new tab 

What version of the product are you using? On what operating system?
Fauxbar 1.2.1 on Windows 7 x64

Please provide any additional information below.

Original issue reported on code.google.com by carafen...@gmail.com on 17 Nov 2011 at 3:06

[GoogleCodeExporter]

Hmm, I am unable to reproduce this. Works as intended for me.

If you open up Fauxbar's developer tools console (open Fauxbar, press F12, then 
click Console), can you type in:

localStorage.option_launchFauxbar

then press Enter. A quoted value will appear. Could you please tell me what 
that value is?
Should be either "currentTab", "newTab" or "newWindow"

Original comment by fauxbar....@gmail.com on 18 Nov 2011 at 12:50

• Added labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

Hi there. I've just opened Chrome and at the moment, Fauxbar is defaulting to 
opening in a new tab. The console reports "newTab".

When I set the option back to "open in the current tab" the console output says 
"currentTab" - so that all seems to be working.

The problem is, is that the option isn't saved and I have to keep setting it 
back to "current tab" every time I reload Chrome.

Thanks

Original comment by carafen...@gmail.com on 19 Nov 2011 at 7:58

[GoogleCodeExporter]

Ahh, I see it now. Will get this fixed up. Thanks!

Original comment by fauxbar....@gmail.com on 20 Nov 2011 at 1:19

• Changed state: Started

[GoogleCodeExporter]

Fixed in v1.2.2.

Original comment by fauxbar....@gmail.com on 20 Nov 2011 at 6:10

• Changed state: Fixed