Vidal Guillermo Diazleal Ortega
4786bc4eee
This CL removes localization from the emulated_devices module for the
following reasons:
- The module does not have a UI surface where the strings are shown; it
declares the strings while emulation consumes and show them.
- Most of the strings declared in the module are branded strings which
are out of scope for translation. (e.g Android/IOS phone models)
- The only strings need to be localized here will be added to
emulation:
- "Laptop with HiDPI screen"
- "Laptop with MDPI screen"
- "Laptop with touch"
In a similar way as done in here:
2631106: [Loc] Migrate heap_snapshot_worker to Localization V2 |
https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2631106
Bug: 1136655
Change-Id: I88b12f7adb955b7236f79bb862dba0db7dc5d5cc
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2707864
Commit-Queue: Vidal Diazleal <vidorteg@microsoft.com>
Reviewed-by: Simon Zünd <szuend@chromium.org>
Reviewed-by: Kalon Hinds <kahinds@microsoft.com>
Chrome DevTools frontend
The client-side of the Chrome DevTools, including all JS & CSS to run the DevTools webapp.
Source code
The frontend is available on chromium.googlesource.com.
Design guidelines
Please be aware that DevTools follows additional development guidelines.
Issue triage
The issue triage guidelines can be found in docs/triage_guidelines.md.
Workflows
Instructions to set up, use, and maintain a DevTools frontend checkout can be found in docs/workflows.md.
Additional references
- DevTools documentation: devtools.chrome.com
- Debugging protocol docs and Chrome Debugging Protocol Viewer
- awesome-chrome-devtools: recommended tools and resources
- Contributing to DevTools: bit.ly/devtools-contribution-guide
- Contributing To Chrome DevTools Protocol: docs.google.com
- DevTools Design Review Guidelines: design_guidelines.md
Source mirrors
DevTools frontend repository is mirrored on GitHub.
DevTools frontend is also available on NPM as the chrome-devtools-frontend package. It's not currently available via CJS or ES modules, so consuming this package in other tools may require some effort.
The version number of the npm package (e.g. 1.0.373466) refers to the Chromium commit position of latest frontend git commit. It's incremented with every Chromium commit, however the package is updated roughly daily.
Getting in touch
-
All DevTools commits: View the log or follow @DevToolsCommits on Twitter
-
All open DevTools tickets on crbug.com
-
File a new DevTools ticket: new.crbug.com
-
Code reviews mailing list: devtools-reviews@chromium.org
-
@ChromeDevTools on Twitter
-
Chrome DevTools mailing list: groups.google.com/forum/google-chrome-developer-tools