[CSSStyleDeclaration] Remove parseUnusedText logic It is introduced in crrev.com/c/1089295 and is served well to us until now, with the nesting introduced. Its custom logic for trying to figure out which properties might the user intended to write is getting more and more complex with the addition of new CSS features (nesting again...). So, this is getting a risky logic that would break Styles pane in some situations. The UX win it provides (crbug.com/813435) does not justify our maintenance costs and the risk it introduces to the reliability. So, it's time we say goodbye to our fellow logic. Fixed: 1473339 Change-Id: Ieaf87f7f9dbcc02d835ec042628a75ec0e13de15 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/5033671 Commit-Queue: Changhao Han <changhaohan@chromium.org> Auto-Submit: Ergün Erdoğmuş <ergunsh@chromium.org> Reviewed-by: Changhao Han <changhaohan@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 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: devtools-reviews@chromium.org
@ChromeDevTools on Twitter
Chrome DevTools mailing list: groups.google.com/forum/google-chrome-developer-tools