Google Git
Sign in
chromium / chromium / src / third_party / blink / renderer / devtools / 8d5a4665d34ac0ee5d107d10daf4009c2625047f
commit8d5a4665d34ac0ee5d107d10daf4009c2625047f[log] [tgz]
authorChandani Shrestha <chshrest@microsoft.com>Mon Oct 07 21:20:34 2019
committerCommit Bot <commit-bot@chromium.org>Mon Oct 07 21:20:34 2019
tree590b45510d5d87b88e46c25c37666c4876969cff
parent042827fcdd9a6b8e44d15d6286ae0bdf88ed8b86 [diff]
DevTools: Remove extra tab in Settings Throttling Pane

Without this change when user navigates back by pressing SHIFT TAB from inputs in throttling settings pane.
Tab stops at whole throttling settings pane. Again, pressing SHIFT TAB it takes to 'Throttling' in Settings then, pressing TAB it lands in Throttling Pane content section instead of landing on first control 'Add custom profile button'.
This change removes that extra TAB so that, when user presses TAB it lands only in interactive controls and satisfies below given rule:
- Don't allow users to tab to text elements (such as labels) or other static content.
More info: https://accessibilityinsights.io/docs/en/windows/reference/tabstops

Bug: 963183
Change-Id: I100ccc0b541f2eb8a077a7fdb63c6f594dbc6c4d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1817412
Reviewed-by: Yang Guo <yangguo@chromium.org>
Reviewed-by: John Emau <John.Emau@microsoft.com>
Commit-Queue: Chandani Shrestha <chshrest@microsoft.com>
Cr-Original-Commit-Position: refs/heads/master@{#703472}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 4bf85dbc7308e5769364eaa68924dad764c77843
1 file changed
tree: 590b45510d5d87b88e46c25c37666c4876969cff
  1. docs/
  2. front_end/
  3. scripts/
  4. services/
  5. tests/
  6. .clang-format
  7. .eslintignore
  8. .eslintrc.js
  9. .gitignore
  10. .npmignore
  11. .style.yapf
  12. BUILD.gn
  13. htaccess
  14. karma.conf.js
  15. LICENSE
  16. OWNERS
  17. package.json
  18. PRESUBMIT.py
  19. protocol.json
  20. readme.md
  21. tsconfig.json
readme.md

Chrome DevTools frontend

NPM package

The client-side of the Chrome DevTools, including all JS & CSS to run the DevTools webapp.

It is available on NPM as the chrome-devtools-frontend package. It's not currently available via CJS or ES2015 modules, so consuming this package in other tools may require some effort.

Package versioning

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.

Source code

The frontend is available through a git subtree mirror on chromium.googlesource.com, with a regularly updating GitHub mirror at github.com/ChromeDevTools/devtools-frontend. The codebase's true location is in third_party/blink/renderer/devtools/ in Chromium's git repo.

Getting Started

  1. Clone the repo
  2. Go to repo root and run: npm start
    • This launches Chrome Canary and starts the dev server with 1 command
  3. Go to http://localhost:9222#custom=true&experiments=true

Power user tips:

You can customize the port for the dev server: e.g. PORT=8888 npm start.

You can also launch chrome and start the server separately:

  • npm run chrome
  • npm run server

When you start Chrome separately, you can pass extra args to Chrome:

npm run chrome -- https://news.ycombinator.com

(e.g. this launches Hacker News on startup)

If you want to reset your development profile for Chrome, pass in “--reset-profile”:

npm start -- --reset-profile

OR

npm run chrome -- --reset-profile

Hacking

Useful Commands

Simpler npm commands w/ dtrun

If you want to run these npm commands anywhere in the chromium repo (e.g. in chromium/src), you'll want to setup our dtrun CLI helper.

One-time setup:

npm run setup-dtrun

Now, you can use any of the following commands by simply doing: dtrun test.

In addition, you no longer need to pass double dashes (e.g. --) before you pass in the flags. So you can do: dtrun test -d inspector/test.html.

npm run format

Formats your code using clang-format

npm run format-py

Formats your Python code using yapf

Note: Yapf is a command line tool. You will have to install this manually, either from PyPi through pip install yapf or if you want to enable multiprocessing in Python 2.7, pip install futures

npm test

Builds devtools and runs all inspector/devtools web tests.

Note: If you're using a full chromium checkout and compiled content shell in out/Release, then npm test uses that. Otherwise, with only a front-end checkout (i.e. cloning from GitHub), then npm test will fetch a previously compiled content shell from the cloud (and cache it for future test runs).

npm test basics

# run specific tests
npm test -- inspector/sources inspector/console

# debug a specific test. Any one of:
npm run debug-test inspector/cookie-resource-match.html
npm test -- --debug-devtools inspector/cookie-resource-match.html
npm test -- -d inspector/cookie-resource-match.html

# pass in additional flags to the test harness
npm test -- -f --child-processes=16

# ...for example, use a higher test timeout
npm test -- --time-out-ms=6000000 <test_path>

Tip: Learn about the test harness flags

--fetch-content-shell

# If you're using a full chromium checkout and have a compiled content shell,
# this will fetch a pre-compiled content shell. This is useful if you
# haven't compiled your content shell recently
npm test -- --fetch-content-shell

--target=SUB_DIRECTORY_NAME

# If you're using a build sub-directory that's not out/Release,
# such as out/Default, then use --target=SUB_DIRECTORY_NAME
npm test -- --target=Default

Development

Getting in touch

Tests

The tests are run through Karma.

python scripts/run_tests.py

You can also specify with which Chrome binary to run tests by setting the chrome-binary variable.

python scripts/run_tests.py --chrome-binary=/path/to/chromium/build/chromium