Closed Bug 1519487 Opened 9 months ago Closed 9 months ago

No value for "User Namespaces" in about:support

Categories

(Core :: Internationalization, defect, P2)

defect

Tracking

()

RESOLVED FIXED
mozilla66
Tracking Status
firefox66 --- fixed

People

(Reporter: viktor_jaegerskuepper, Assigned: Gijs)

References

Details

(Whiteboard: [qa-66b-p2])

Attachments

(1 file, 1 obsolete file)

In current Firefox Nightly on Linux (64 bit), when I look at the
"Sandbox" part in about:support, there is no value for "User Namespaces"
(used to be "false" if I remember correctly).

It looks like the behavior of $.new changed slightly with the conversion to Fluent in bug 1507595, and passing false as a boolean for the second argument gives an empty element (but true is still converted to a string).

The fix is simple.

Assignee: nobody → jld
Blocks: 1507595
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Attachment #9036488 - Attachment is obsolete: true

From the comments in https://phabricator.services.mozilla.com/D16519, it sounds like someone who's more familiar with aboutSupport.js should handle this.

Assignee: jld → nobody
Status: ASSIGNED → NEW
Component: Security: Process Sandboxing → Internationalization
OS: Linux → Unspecified
Hardware: x86_64 → Unspecified
Priority: -- → P2

(In reply to Jed Davis [:jld] ⟨⏰|UTC-7⟩ ⟦he/him⟧ from comment #3)

From the comments in https://phabricator.services.mozilla.com/D16519, it sounds like someone who's more familiar with aboutSupport.js should handle this.

Sadly, phab doesn't CC reviewers on bugs so I didn't see this comment... I'll see about fixing this tomorrow or Mon/Tue...

Assignee: nobody → gijskruitbosch+bugs
Pushed by jwein@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/f69488e75f13
fix display of `false` and other falsy values in about:support when passed to $.new, r=jaws
Status: NEW → RESOLVED
Closed: 9 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla66
Whiteboard: [qa-66b-p2]
You need to log in before you can comment on or make changes to this bug.