Error on first press of Fauxbar button

[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. Click the Fauxbar toolbar button

What is the expected output? What do you see instead?
Should load the Fauxbar main screen, however I get the error:

This web page is not available

The web page at chrome-extension://invalid/ might be temporarily down or it may 
have moved permanently to a new web address.
Error 2 (net::ERR_FAILED): Unknown error.

Which version of Fauxbar and Chrome are you using, and which operating
system?
Fauxbar 1.2.8 / Windows 7 x64

Please provide any additional information below.

I get the above error when clicking the toolbar button, however if i click the 
button once more, Fauxbar works normally.

Original issue reported on code.google.com by carafen...@gmail.com on 8 Apr 2012 at 6:54

[GoogleCodeExporter]

I'm getting the same problem if I click the "home" button after visiting a 
website.  Click the button a second time and the Fauxbar page loads 
successfully.  No errors in Fauxbar's log.  Screenshot attached.

Original comment by bewareof...@gmail.com on 8 Apr 2012 at 10:20

Attachments:

• Chrome_FauxbarError.jpg

[GoogleCodeExporter]

Same problem here. But it seems to be a chrome error since Version 18

Original comment by ksdec...@gmail.com on 11 Apr 2012 at 9:52

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I haven't been able to reproduce this, but it sounds similar to issue #112

Original comment by fauxbar....@gmail.com on 3 Jun 2012 at 11:28

• Added labels: Type-Defect

[GoogleCodeExporter]

I strongly believe this has been fixed now with version 1.2.9.
If not, please say so. Thanks

Original comment by fauxbar....@gmail.com on 4 Jun 2012 at 5:19

• Changed state: Fixed

[GoogleCodeExporter]

Updated to 1.2.9 this morning and haven't had the problem since!

Strange that I had to switch to dev mode to force the update, but either way, 
it appears to be working now, thanks :D

Original comment by carafen...@gmail.com on 4 Jun 2012 at 9:59