Are there any bugzilla issues open with Mozilla for support?

Question

Are there any bugzilla issues open with Mozilla for support?

Opened this issue 7 years ago · 15 comments

At the very least someone there will get back to you on why or not what you're requesting is feasible / already being worked on or not.

Answer 1 · 2017-06-29T09:24:42.000Z

There are not actually :) Do you know what the best place to put this would be? thanks!

Answer 2 · 2017-06-30T20:03:16.000Z

Here's the main page. You'll have to make an account, and it's recommended to search for your bug/feature request before writing one, but it should do the trick

and if you decide to make one (or several) can you link them back here so I can follow them as well? I was thinking about giving developing the extension a try as I haven't before.

Answer 3 · 2017-07-04T11:15:19.000Z

Thank you! :)

Added the bug here: https://bugzilla.mozilla.org/show_bug.cgi?id=1378096

Hopefully they'll take a look!

Answer 4 · 2017-11-14T15:42:15.000Z

You're aware that this WILL break once 57 hits the floor running?

They dropped all support for XUL and XPCOM "addons" now.

Answer 5 · 2017-11-14T15:43:32.000Z

What will break exactly? Can you clarify?

Answer 6 · 2017-11-14T15:45:01.000Z

They've dropped the whole XUL/XPCOM infrastructure from what I can gather, so unless you rework the addon to use the new (I think it's called WebExtensions) Addon API, the addon will not work anymore.

I just took a first look at 57 (as it just hit my distributions' package repos), and a lot of addons just gave me the finger. (Basically I'm fine with just uBlock, but NoScript is a decent addition to it=

Answer 7 · 2017-11-14T15:46:28.000Z

But this add-on is already using the WebExtensions format :)

Answer 8 · 2017-11-14T15:47:33.000Z

Eh, okay, I'll shut up and sit back down :F

I couldn't get it to work for some reason or other, but that may be related to my (rather peculiar) setup here.

Answer 9 · 2017-11-14T15:48:47.000Z

You couldn't get it to work probably because this is a very early version... Unless Firefox adds support for push messaging in add-ons there's no point in continuing development on this unfortunately.

Answer 10 · 2017-11-14T15:50:57.000Z

Ah, too bad then, cause I really want to get rid of chrome atm...

Answer 11 · 2017-11-14T16:59:37.000Z

To be fair, they have support, just not the way you want to do it. The main reason I switched back to Pushbullet is that the Firefox addon has notifications.

Answer 12 · 2017-11-14T17:34:37.000Z

Well, they support websockets, yes, but unfortunately I can't afford those. :( They should really add support for Web Push, since Firefox can already receive those natively.

Answer 13 · 2019-06-14T12:05:55.000Z

With how stale the FF issue is, any possibilities of getting custom, self hosted push notification support?
I understand not wanting to shoulder the costs for a free extension but having the option to configure a self- or cloud-hosted solution could go a long way to making this viable on FF again.

I'd vote for AWS personally as I already maintain stuff over there but any of the 3 big cloud providers and/or 3rd party FOSS solutions would be great to have an option to integrate manually.
That is, unless there is a real possibility of FF actually adding the missing features to the WebExtensions API any time soon, then obv not worth the time/effort.

Answer 14 · 2019-06-14T14:16:40.000Z

I'm actually in the process of implementing something that might give partial support for firefox :) Stay tuned...

Answer 15 · 2019-06-24T09:20:29.000Z

🍿 Looking forward to it, I've been making a concerted effort to move away from Chrome lately, and I'd hate to have to resort to PushBullet :)