Google Git
Sign in
chromium / chromium / src / 08b6a8d9f034badfb1853b51e52787f8932fdea0
commit08b6a8d9f034badfb1853b51e52787f8932fdea0[log] [tgz]
authorzhoupeng <zhoupeng.1996@bytedance.com>Sun Mar 03 21:12:24 2024
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Sun Mar 03 21:12:24 2024
treee292301a5192663f064ef97a46fe5d6a6ce5f252
parent161ad888b4e9eefe9e652b4f5db96c8d657dabc6 [diff]
Make sure that the inert element and its subtree cannot be searchable

As per the HTML spec:
Content in an inert element and its subtree will not be perceivable
by all users, or interactive.

Consider this test case:
<body>
  <div inert>Do not find me please</div>
</body>
The return value of `window.find('me')` is true, but `div` is
non-interactive due to the inert attribute being assigned to it.
`ShouldIgnoreContents` should assess the inert attribute of the element.
The reason why some cases in `inert/inert-and-find.html` cannot be
passed is also attributed to this factor.

Bug: 327017912
Change-Id: I5b4b15859c9e9c31f57b1d5cfc44509dc37105aa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5319168
Reviewed-by: Kent Tamura <tkent@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Commit-Queue: Koji Ishii <kojii@chromium.org>
Auto-Submit: Peng Zhou <zhoupeng.1996@bytedance.com>
Cr-Commit-Position: refs/heads/main@{#1267634}
4 files changed
tree: e292301a5192663f064ef97a46fe5d6a6ce5f252
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia_web/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  32. native_client_sdk/
  33. net/
  34. pdf/
  35. ppapi/
  36. printing/
  37. remoting/
  38. rlz/
  39. sandbox/
  40. services/
  41. skia/
  42. sql/
  43. storage/
  44. styleguide/
  45. testing/
  46. third_party/
  47. tools/
  48. ui/
  49. url/
  50. webkit/
  51. clank
  52. internal
  53. ios_internal
  54. native_client
  55. signing_keys
  56. v8
  57. .clang-format
  58. .clang-tidy
  59. .clangd
  60. .eslintrc.js
  61. .git-blame-ignore-revs
  62. .gitallowed
  63. .gitattributes
  64. .gitignore
  65. .gitmodules
  66. .gn
  67. .mailmap
  68. .rustfmt.toml
  69. .vpython3
  70. .yapfignore
  71. ATL_OWNERS
  72. AUTHORS
  73. BUILD.gn
  74. CODE_OF_CONDUCT.md
  75. codereview.settings
  76. DEPS
  77. DIR_METADATA
  78. LICENSE
  79. LICENSE.chromium_os
  80. OWNERS
  81. PRESUBMIT.py
  82. PRESUBMIT_test.py
  83. PRESUBMIT_test_mocks.py
  84. README.md
  85. WATCHLISTS
README.md

Logo Chromium

Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.

The project's web site is https://www.chromium.org.

To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.

Documentation in the source is rooted in docs/README.md.

Learn how to Get Around the Chromium Source Code Directory Structure.

For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.

If you found a bug, please file it at https://crbug.com/new.