Closed
Bug 1974355
Opened 11 months ago
Closed 10 months ago
Allow insecure features in nimbus-secure-experiments, provided there is a secure feature in the recipe
Categories
(Firefox :: Nimbus Desktop Client, enhancement, P1)
Firefox
Nimbus Desktop Client
Tracking
()
RESOLVED
FIXED
142 Branch
| Tracking | Status | |
|---|---|---|
| firefox142 | --- | fixed |
People
(Reporter: beth, Assigned: beth)
References
Details
Attachments
(1 file)
We're going to be adding new secure features in bug 1973228 which will eventually want to use ride-along messaging or, e.g., traditional newtab configuration. To enable this, we need to lift the restriction that the secure collection only contains entirely features marked as secure.
| Assignee | ||
Comment 1•10 months ago
|
||
Pushed by brennie@mozilla.com:
https://github.com/mozilla-firefox/firefox/commit/7ff65053bc05
https://hg.mozilla.org/integration/autoland/rev/b98d7956caa6
Allow recipes from the secure collection to contain insecure features as long as one secure feature is present r=nimbus-reviewers,relud
Comment 3•10 months ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 10 months ago
status-firefox142:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 142 Branch
Updated•10 months ago
|
QA Whiteboard: [qa-triage-done-c143/b142]
You need to log in
before you can comment on or make changes to this bug.
Description
•