"Hide button" isn't persistent

[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. Right-click fauxbar button next to the address bar, select "Hide button", it 
goes away
2. Wait 60 seconds for memory helper to kick in (I think)
3. The button re-appears!

What is the expected output? What do you see instead?

Expected output: Button is hidden permanently until I want it to come back.

What I see instead: Button comes back!

Which version of Fauxbar and Chrome are you using, and which operating
system?

Fauxbar: 1.2.5
FB Memory Helper: 1.0.1
Chrome: 17.0.963.79

Please provide any additional information below.

The button seems pretty redundant since I get the same thing from the new tab 
button.  I am a little scared of the button because it looks like pedobear.

Original issue reported on code.google.com by owen.zah...@gmail.com on 22 Mar 2012 at 12:32

[GoogleCodeExporter]

This isn't a fauxbar bug. This is a chrome bug.
No extension have access to this setting or can control it.

Report this bug here: http://code.google.com/p/chromium/issues/list

Original comment by laboboL...@gmail.com on 31 Mar 2012 at 3:01

[GoogleCodeExporter]

yes, as explained above, this is beyond control.
One not-so-nice solution could be unpacking the extension, modify manifest.json 
file to remove extension icon browser behavior then pack and sign again.   

I don't like the icon either as I prefer a tiny bar.

Original comment by core...@gmail.com on 3 Apr 2012 at 7:08

[GoogleCodeExporter]

Yes, this is a byproduct of Fauxbar Memory Helper disabling and enabling 
Fauxbar. Chrome doesn't remember that you want the Fauxbar button to stay 
hidden. Might be a Chrome "feature".

The Fauxbar toolbar button was first introduced when I added the Fauxbar Lite 
extension.

Perhaps the Fauxbar button is unnecessary for Fauxbar. Chrome's New Tab button 
does the same thing (assuming you opt to have the button open Fauxbar in a new 
tab - its default behaviour).

But there might be users that like having the button open Fauxbar in the 
current tab, or a new window, I'm not sure. Or even just having it there to 
quickly access Fauxbar's options with a right-click.

coreguy's suggestion would work, but yeah, I don't really feel like maintaining 
a third branch of Fauxbar just for this option :/

I *think* it'd be okay to remove it from Fauxbar as it does seem overkill. But 
maybe I could run a poll on Facebook or something and see what people have set, 
just to see?

Original comment by fauxbar....@gmail.com on 8 Apr 2012 at 3:44

• Added labels: Type-Defect

[GoogleCodeExporter]

online polling is fine.

also I think removing icon first from the lite edition could serve as a testing 
approach. By doing this, fauxbar lite is in a more "lite" sense, meanwhile 
responses regarding the removal can be gathered. 

Original comment by core...@gmail.com on 11 Apr 2012 at 12:46

[GoogleCodeExporter]

Once issue #2 is fixed (involving converting Fauxbar's background page into an 
event page, and using Chrome's new alarms instead of JavaScript's setTimeout 
function), Memory Helper will be no more, and this problem will go away.

Please star issue #2 for future updates on this.

Original comment by fauxbar....@gmail.com on 18 Apr 2013 at 5:11

• Changed state: WontFix