OS X firewall does not remember Firefox Developer Edition

RESOLVED WORKSFORME

Status

()

Firefox
Developer Tools
RESOLVED WORKSFORME
4 years ago
4 years ago

People

(Reporter: Sören Hentzschel, Unassigned)

Tracking

35 Branch
All
Mac OS X
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

4 years ago
Created attachment 8515381 [details]
screenshot

STR:

1. install current build of Firefox Developer Edition (http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/gum-macosx64-debug/1414787394/)
2. start Firefox Developer Edition
3. allow the network connection (OS X firewall)
4. quit Firefox
5. start Firefox Developer Edition

Expected:

No OS X firewall dialog.

Actual:

The OS X firewall asks after every start of Firefox Developer Edition.
I think this is because you didn't use a signed build. Can you try again using the latest build from gum?

Actually, make sure you download any existing updates first from the About dialog.
Group: mozilla-employee-confidential
(Reporter)

Comment 2

4 years ago
You're right, there are no problems with the latest build from gum, so resolving as WFM.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WORKSFORME
Blocks: 1054353
Resolution: WORKSFORME → FIXED
Resolution: FIXED → WORKSFORME
(Reporter)

Comment 3

4 years ago
Sorry for "bug spam", but I have a question. Is there a list with open issues? Because there are a few style issues but most of "devbrowser bugs" are confidential, so a) I don't know what issues are known and b) I don't want do file more public bugs about the developer edition.
The main reason I marked this bug as confidential is the attached screenshot. If you can adequately describe the issue without attaching a screenshot and also refer to Aurora instead of Developer Edition, then a public bug is fine.

If however you must post a screenshot, just ping me or jwalker on IRC beforehand so we can quickly mark it as moco-confidential.
Group: mozilla-employee-confidential
You need to log in before you can comment on or make changes to this bug.