"enable chrome and add-on debugging" implies *this* toolbox, when it actually enables browser toolbox

RESOLVED FIXED in Firefox 39

Status

RESOLVED FIXED
4 years ago
4 months ago

People

(Reporter: fitzgen, Assigned: fitzgen)

Tracking

unspecified
Firefox 39
x86
Mac OS X

Firefox Tracking Flags

(firefox39 fixed)

Details

Attachments

(1 attachment)

We should probably reword it to "enable browser toolbox" or something.
The problem with "browser toolbox" is that nobody but us would know what it is. Add-on debugging clearly indicates its purpose, and I think MDN has a lot of references to chrome code that chrome debugging makes sense to at least the people who would want to use it (and putting it next to add-on debugging certainly indicates the target demographic).
Maybe "enable chrome and addon toolbox"? Because "enabling debugging" implies *this* toolbox (people inside mozilla didn't even know there was a separate toolbox).
Yes, I think that does sound better. How about "enable chrome and add-on debugging toolbox" to keep the phrase closer to current docs and what some people have been used to?
(In reply to Panos Astithas [:past] from comment #3)
> Yes, I think that does sound better. How about "enable chrome and add-on
> debugging toolbox" to keep the phrase closer to current docs and what some
> people have been used to?

Sounds good to me.
Assignee: nobody → nfitzgerald
Status: NEW → ASSIGNED
Created attachment 8568692 [details] [diff] [review]
Reword the label for enabling chrome debugging
Attachment #8568692 - Flags: review?(past)
Attachment #8568692 - Flags: review?(past) → review+
Keywords: checkin-needed
https://hg.mozilla.org/mozilla-central/rev/5727de60e0f0
Status: ASSIGNED → RESOLVED
Last Resolved: 4 years ago
status-firefox39: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 39

Updated

4 months ago
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.