Reland "Use Intl.NumberFormat for time and byte formatting" This reverts commit 55ffe2fb876bae23ee9b83f1b7824b2021834c12. Reason for revert: fixed conflicting internal code (NPP) Original change's description: > Revert "Use Intl.NumberFormat for time and byte formatting" > > This reverts commit 6b3449efbc12670977cc04ecf0f1c66148f2df5d. > > Reason for revert: currently failing the auto roller: https://ci.chromium.org/ui/p/devtools-internal/builders/try/devtools_frontend_linux_rel/b8731890377373202833/overview > > Original change's description: > > Use Intl.NumberFormat for time and byte formatting > > > > TimeUtilities now uses Intl.NumberFormat (instead of UIStrings), > > and bytesToString now uses Intl.NumberFormat (instead of non-locale > > aware strings). Additionally, bytesToString is now under the i18n > > module. > > > > Impacts of this change: > > > > * use Chrome ICU locale data to format, rather than human translators, > > which allows us to be more accurate in regards to unit display style > > (narrow vs short vs long) > > * group separators (ex: thousands decimals in english) are now present > > * slight change to rounding behavior - Intl.NumberFormat defaults to > > "halfExpand", which rounds away from zeroes to break ties. Previously > > we just truncated > > > > See go/cpq:i18n-units-design > > > > Bug: 372723536 > > Change-Id: Iff05ca9ff01213660d64ca88fadb613296153fa9 > > Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/5981156 > > Reviewed-by: Simon Zünd <szuend@chromium.org> > > Commit-Queue: Connor Clark <cjamcl@chromium.org> > > Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> > > Reviewed-by: Paul Irish <paulirish@chromium.org> > > Bug: 372723536 > Change-Id: I82f74ae04729b9f6c514d7e186572a8ffade30cd > Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6003765 > Commit-Queue: Kim-Anh Tran <kimanh@chromium.org> > Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Bug: 372723536 Change-Id: I1d6f3ddc5fb0cc97a88b79e27a74ba29c134c83f Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6005878 Commit-Queue: Connor Clark <cjamcl@chromium.org> Reviewed-by: Paul Irish <paulirish@chromium.org>
The client-side of the Chrome DevTools, including all TypeScript & CSS to run the DevTools webapp.
The frontend is available on chromium.googlesource.com. Check out the Chromium DevTools documentation for instructions to set up, use, and maintain a DevTools front-end checkout, as well as design guidelines, and architectural documentation.
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.
There are a few options to keep an eye on the latest and greatest of DevTools development:
Follow What's new in DevTools.
Follow Umar's Dev Tips.
Follow these individual Twitter accounts: @umaar, @malyw, @kdzwinel, @addyosmani, @paul_irish, @samccone, @mathias, @mattzeunert, @PrashantPalikhe, @ziyunfei, and @bmeurer.
Follow to g/devtools-reviews@chromium.org mailing list for all reviews of pending code, and view the log, or follow @DevToolsCommits on Twitter.
Checkout all open DevTools tickets on crbug.com
Use Chrome Canary and poke around the experiments.
