Parse colors defined in new syntax as `Color` objects Internally, we're still holding `sRGB` values which can be out-of-sRGB-gamut and this is fine as we'll use them as: * Transport mechanism of Colors * Contrast calculations It seems like contrast calculations with out-of-sRGB-gamut colors with sRGB values are fine. So, we probably won't need to do anything specific here. (which I'll confirm next) This is a biiiig CL but I thought it tells a meaningful story, so decided to keep it this way. Let me know if you would prefer seeing changes in smaller CLs. All the things happening in this CL, in order: * We handle parsing new color syntaxes: `lch()`, `oklch()`, `lab()`, `oklab()`, `color()` and create `Color` objects for them too * Since we're able to parse these colors now, we don't need to special case color texts before parsing and render circular color swatch where needed. Instead, we're passing `Color` objects to `ColorSwatch` and it decides what to render: circular color swatch or regular one. * Removal of CircularColorSwatch component. * Since now we're able to understand colors written in the new syntax CSS Overview panel collects color out of the box. After talking to Peter, I've made one adjustment to make sure those colors are represented good (at least without overflowing to other elements or breaking the layout). Fixed: 1385379 Change-Id: Ic9a86addcab08a57bcba6deb5b9e433b146945c6 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4057666 Reviewed-by: Changhao Han <[email protected]> Reviewed-by: Philip Pfaffe <[email protected]> Commit-Queue: Ergün Erdoğmuş <[email protected]>
The client-side of the Chrome DevTools, including all JS & CSS to run the DevTools webapp.
The frontend is available on chromium.googlesource.com.
Check out the project 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.
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: [email protected]
@ChromeDevTools on Twitter
Chrome DevTools mailing list: groups.google.com/forum/google-chrome-developer-tools