Closed Bug 1122142 Opened 10 years ago Closed 10 years ago

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

Categories

(DevTools :: Debugger, defect)

x86
macOS
defect
Not set
normal

Tracking

(firefox39 fixed)

RESOLVED FIXED
Firefox 39
Tracking Status
firefox39 --- fixed

People

(Reporter: fitzgen, Assigned: fitzgen)

Details

Attachments

(1 file)

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
Attachment #8568692 - Flags: review?(past)
Attachment #8568692 - Flags: review?(past) → review+
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 39
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: