Google Git
Sign in
chromium / chromium / src / 392ef53c5a831b1e177ab589558b8ac99d84230f
commit392ef53c5a831b1e177ab589558b8ac99d84230f[log] [tgz]
authorDevlin Cronin <rdevlin.cronin@chromium.org>Wed Jun 07 18:56:59 2023
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Jun 07 18:56:59 2023
treeb260af7eeb2f7cb0614beeb6bb5770de8a3401eb
parent50d2dd7831922d59c1056c355f375aa6879f8d34 [diff]
Reset service worker idle timer by websocket activities

This is done by two steps. The first step let DOMWebsocket notify
ExecutionContext when selected activity happens. The second step let
ServiceWorkerGlobalScope reset idle timer when received such a notice.

Call it notify instead of on... event has two reasons: 1) To indicate
what does the ExecutionContext do with should not affect WebSocket; 2)
At this point there is no need to distinguish different activity yet.
The purpose is to simply notify something happened in the web socket.
What happened is not a concern, for now.

ChromeContentRendererClient implements the logic that limits this
notification to extension service workers.

Bug: 1382537
Change-Id: I7799c5be6eb981091415576c4b5061336324c58b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4521729
Reviewed-by: Yoshisato Yanagisawa <yyanagisawa@chromium.org>
Reviewed-by: Tim <tjudkins@chromium.org>
Commit-Queue: Devlin Cronin <rdevlin.cronin@chromium.org>
Reviewed-by: David Bertoni <dbertoni@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1154538}
17 files changed
tree: b260af7eeb2f7cb0614beeb6bb5770de8a3401eb
  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. weblayer/
  51. .clang-format
  52. .clang-tidy
  53. .eslintrc.js
  54. .git-blame-ignore-revs
  55. .gitattributes
  56. .gitignore
  57. .gn
  58. .mailmap
  59. .rustfmt.toml
  60. .vpython3
  61. .yapfignore
  62. ATL_OWNERS
  63. AUTHORS
  64. BUILD.gn
  65. CODE_OF_CONDUCT.md
  66. codereview.settings
  67. DEPS
  68. DIR_METADATA
  69. LICENSE
  70. LICENSE.chromium_os
  71. OWNERS
  72. PRESUBMIT.py
  73. PRESUBMIT_test.py
  74. PRESUBMIT_test_mocks.py
  75. README.md
  76. 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.