Support for Firefox 12.0a2 (Aurora)

[GoogleCodeExporter]

I was using Firefox 11.0a2 (Aurora) and the addon was working fine.
After upgrading to Firefox 12.0a2 (Aurora) it's installed and I can manager 
permissions but it's as if the addon was not installed. I have no notification, 
on the test page of the project it says that my browser doesn't support HTML5 
notifications.

Is this a known issue?

Original issue reported on code.google.com by petersai...@gmail.com on 2 Feb 2012 at 6:05

[GoogleCodeExporter]

Have you tried to restart Firefox ?

I have made the following test :
- start new profile for aurora
- install extension
- click on restart
- go to test page => test failed
- restart firefox
- go to test page => test ok
- restart firefox
- go to test page => test ok
- reinstall extension
- click on restart
- go to test page => test failed
- restart firefox
- go to test page => test ok

So I don't know what to think...
It seems to be a registration problem of Firefox when extension is newly 
installed.
I will look at mozilla bug lists and maybe fill one.

Thank you for reporting bug !

Original comment by pascal.c...@gmail.com on 2 Feb 2012 at 6:17

• Changed state: Accepted

[GoogleCodeExporter]

Yes! On a clean profile I can reproduce the behavior you just described. Now I 
just have to figure out how to fix it on my regular profile.

The problem seems not to be that bad. Probably just a small detail that changed 
between 11 a 12 branches. If you find something on Bugzilla please post here ;)

Original comment by petersai...@gmail.com on 2 Feb 2012 at 6:30

[GoogleCodeExporter]

This seems to be a double issue. On my regular profile, after countless 
experiences (cache cleaning, disabling addons, etc.) I found out that the 
culprit is the Adblock Hiding Element Helper 
(https://addons.mozilla.org/en-US/firefox/addon/elemhidehelper/)

But it's still an issue. I had it installed along side ff-html5notifications on 
Firefox 11 (Aurora) and there was no incompatibility whatsoever.

Original comment by petersai...@gmail.com on 2 Feb 2012 at 7:01

[GoogleCodeExporter]

I thought I had isolated it but it gets stranger. If I disable Scriptish (or 
Greasemonkey) and leave Stylish on it works, if I disable Stylish instead and 
leave Scriptish or Greasemonkey enabled it also works. If enable Stylish AND 
Scriptish or Greasemonkey it doesn't work.

I just can't isolate the problem. Grr...

Original comment by petersai...@gmail.com on 2 Feb 2012 at 7:07

[GoogleCodeExporter]

I seem to have finally detected how to reproduce the problem. It's basically a 
problem, whenever you install/enable/disable an extension when you restart once 
ff-html5notifications stops working. If you restart twice it works again.

Original comment by petersai...@gmail.com on 7 Feb 2012 at 5:46

[GoogleCodeExporter]

That's weird... I do not think this is specific to webkitNotifications, but 
addons that use same technologies are not easy to find. I'll try to figure it 
out, but my last searches on bugs.mozilla.org didn't lead me anywhere...

Original comment by pascal.c...@gmail.com on 7 Feb 2012 at 6:23

[GoogleCodeExporter]

Bug filed at https://bugzilla.mozilla.org/show_bug.cgi?id=725016

Original comment by pascal.c...@gmail.com on 7 Feb 2012 at 7:01

[GoogleCodeExporter]

Nice. I just voted it and will keep an eye on it.

Original comment by petersai...@gmail.com on 7 Feb 2012 at 7:02

[GoogleCodeExporter]

Noted in the BMO bug, please reorder your chrome.manifest so that the category 
is registered *after* the component/contract. We're trying to get the contract 
before it is registered, which is why this fails.

Original comment by bsmedb...@gmail.com on 7 Feb 2012 at 8:56

[GoogleCodeExporter]

Work is in progress : a guy (Nils Maier) gave me a workaround.
Cheers,
Cyril

Original comment by pascal.c...@gmail.com on 8 Feb 2012 at 2:30

[GoogleCodeExporter]

This version should be working :
http://cyril.me/dl/h5n/ff-html5notifications-1.0.6-fx.xpi

Original comment by pascal.c...@gmail.com on 9 Feb 2012 at 7:01

• Changed state: Done