- Renames "Toggle Tools" to "Web Developer Tools"
- Renames "Get More Tools" to "Extensions for Developers"
Details
- Reviewers
jdescottes mconley - Commits
- rMOZILLACENTRALc86dc4f007dc: Bug 1690340 - Part 2: Use the new naming for the developer tools menu items.
- Bugzilla Bug ID
- 1690340
Diff Detail
- Repository
- rMOZILLACENTRAL mozilla-central
- Lint
Lint Not Applicable - Unit
Tests Not Applicable - Build Status
Buildable 289543 Build 382491: arc lint + arc unit
Event Timeline
Code analysis found 1 defect in the diff 398715:
- 1 defect found by code coverage analysis
In our previous code coverage analysis run, we found some files which had no coverage and are being modified in this patch:
Should they have tests, or are they dead code?
- You can file a bug blocking Bug 1415824 for untested files that should be tested.
- You can file a bug blocking Bug 1415819 for untested files that should be removed.
If you see a problem in this automated review, please report it here.
You can view these defects on the code-review frontend and on Treeherder.
devtools/client/locales/en-US/menus.properties | ||
---|---|---|
31–35 | I can already hear @flod - instead of updating these, we should port them to Fluent first. | |
devtools/client/menus.js | ||
65–66 | Whatever imports this collection is, I think, going to have to know when it's populating the menubar menupopup, or the DevTools button menu / AppMenu DevTools menu (which are effectively the same thing). That way it can choose between the menubar.ftl string variants and the appmenu.ftl variants. The reason for having different variants is that we're going to eventually sentence case the appmenu variants, while leaving the menubar variants in Title Case. |
Code analysis found 1 defect in the diff 398809:
- 1 defect found by code coverage analysis
In our previous code coverage analysis run, we found some files which had no coverage and are being modified in this patch:
Should they have tests, or are they dead code?
- You can file a bug blocking Bug 1415824 for untested files that should be tested.
- You can file a bug blocking Bug 1415819 for untested files that should be removed.
If you see a problem in this automated review, please report it here.
You can view these defects on the code-review frontend and on Treeherder.
Code analysis found 1 defect in the diff 398826:
- 1 defect found by code coverage analysis
The analysis task source-test-node-devtools-tests failed, but we could not detect any issue.
Please check this task manually.
The analysis task source-test-mozlint-file-whitespace failed, but we could not detect any issue.
Please check this task manually.
The analysis task source-test-mozlint-eslint failed, but we could not detect any issue.
Please check this task manually.
In our previous code coverage analysis run, we found some files which had no coverage and are being modified in this patch:
Should they have tests, or are they dead code?
- You can file a bug blocking Bug 1415824 for untested files that should be tested.
- You can file a bug blocking Bug 1415819 for untested files that should be removed.
If you see a problem in this automated review, please report it here.
You can view these defects on the code-review frontend and on Treeherder.
devtools/client/locales/en-US/menus.properties | ||
---|---|---|
31–35 | I think it would be great, but Devtools is also kind a special case at this point :-( (I would still yell if it was DTDs). More important, why "M" when it's not available in the label? This will results in Extensions for Developers (M). |
Code analysis found 1 defect in the diff 398965:
- 1 defect found by code coverage analysis
In our previous code coverage analysis run, we found some files which had no coverage and are being modified in this patch:
Should they have tests, or are they dead code?
- You can file a bug blocking Bug 1415824 for untested files that should be tested.
- You can file a bug blocking Bug 1415819 for untested files that should be removed.
If you see a problem in this automated review, please report it here.
You can view these defects on the code-review frontend and on Treeherder.
devtools/client/locales/en-US/menus.properties | ||
---|---|---|
31–35 | That's the same access key as browserToolboxMenu. Maybe F? |
devtools/client/locales/en-US/menus.properties | ||
---|---|---|
31–35 | F is still not available in the label. We only have one case AFAIK of this (Inspect element with Q), and I don't think we shouldcreate more. |
Code analysis found 1 defect in the diff 400535:
- 1 defect found by code coverage analysis
In our previous code coverage analysis run, we found some files which had no coverage and are being modified in this patch:
Should they have tests, or are they dead code?
- You can file a bug blocking Bug 1415824 for untested files that should be tested.
- You can file a bug blocking Bug 1415819 for untested files that should be removed.
If you see a problem in this automated review, please report it here.
You can view these defects on the code-review frontend and on Treeherder.
devtools/client/locales/en-US/menus.properties | ||
---|---|---|
31–35 | There is the "f" from "for"? Should it be only from the first word? Or is the case important? |
devtools/client/locales/en-US/menus.properties | ||
---|---|---|
31–35 | Sorry, my brain got completely thrown off by F vs f :-( Having said that, please match the case (so, f in this case). F would still work, but no point in relying on fallback. |
Code analysis found 1 defect in the diff 400669:
- 1 defect found by code coverage analysis
In our previous code coverage analysis run, we found some files which had no coverage and are being modified in this patch:
Should they have tests, or are they dead code?
- You can file a bug blocking Bug 1415824 for untested files that should be tested.
- You can file a bug blocking Bug 1415819 for untested files that should be removed.
If you see a problem in this automated review, please report it here.
You can view these defects on the code-review frontend and on Treeherder.