The default bug view has changed. See this FAQ.

Add social.enabled and social.active to the Important Modified Preferences in about:support

RESOLVED FIXED in Firefox 17

Status

()

Firefox
SocialAPI
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: jaws, Assigned: jaws)

Tracking

Trunk
Firefox 18
Points:
---
Bug Flags:
in-testsuite -

Firefox Tracking Flags

(firefox17 fixed)

Details

(Whiteboard: [Fx17])

Attachments

(1 attachment, 2 obsolete attachments)

Add social.enabled to the Important Modified Preferences in about:support. We need this to help troubleshoot potential issues with the Social API after it has shipped.
Created attachment 660259 [details] [diff] [review]
Patch
Assignee: nobody → jaws
Status: NEW → ASSIGNED
Attachment #660259 - Flags: review?(felipc)
How about also adding social.active and social.sidebar.open?
Created attachment 660373 [details] [diff] [review]
Patch v2

With the other two prefs. social.sidebar.open defaults to true, so this pref will only show up in about:support if the user has disabled the sidebar.
Attachment #660259 - Attachment is obsolete: true
Attachment #660259 - Flags: review?(felipc)
Attachment #660373 - Flags: review?(gavin.sharp)
Attachment #660373 - Flags: review?(gavin.sharp) → review+
Created attachment 660375 [details] [diff] [review]
Patch for checkin
Attachment #660373 - Attachment is obsolete: true
Attachment #660375 - Flags: review+
Keywords: checkin-needed
https://hg.mozilla.org/integration/mozilla-inbound/rev/e265b3a3e743
Flags: in-testsuite-
Keywords: checkin-needed
https://hg.mozilla.org/mozilla-central/rev/e265b3a3e743
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 18
Attachment #660375 - Flags: approval-mozilla-aurora+
Summary: Add social.enabled to the Important Modified Preferences in about:support → Add social.enabled and social.active to the Important Modified Preferences in about:support
https://hg.mozilla.org/releases/mozilla-aurora/rev/5f05ed6d4b4d
status-firefox17: --- → fixed
You need to log in before you can comment on or make changes to this bug.