Google Git
Sign in
chromium / chromium / src / 851c8446991a8891af7d6c4b7e5a69b939fcb074
commit851c8446991a8891af7d6c4b7e5a69b939fcb074[log] [tgz]
authorAkihiro Ota <akihiroota@chromium.org>Tue Jul 02 15:57:01 2024
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Jul 02 15:57:01 2024
tree5d28d91e9158060fff99cda892751eb4509f7781
parent5ced97a196f670b36183186b55a1b303aab160bc [diff]
FaceGaze: Use ImageCapture instead of video

This change begins the work to implement the camera integration that
will be used for the MVP. The plan is to do everything from Typescript.
FYI, we explored a camera integration via the browser [1], but a
reviewer recommended that we stay in TS and use the existing WebRTC
APIs to connect to the camera.

In this change, we remove the HTML video element and instead use the
ImageCapture API to feed camera frames into the FaceLandmarker API. In
addition, we reduce the size of the frames we receive from the camera,
which results in a minor performance improvement. Note that we keep
the drawing utils logic for now to keep this change scoped, so the
user is still able to see visual results of the FaceLandmarker.

In a follow-up change, we will move the FaceLandmarker to the
background context and remove the new tab that is opened when
FaceGaze is enabled.

[1] https://chromium-review.googlesource.com/c/chromium/src/+/5652849

Bug: b/309121742
Change-Id: I52d77fca76a15425e09f9f3ee022d782d4ce8add
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5663781
Reviewed-by: Amanda Lin Dietz <aldietz@google.com>
Commit-Queue: Akihiro Ota <akihiroota@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1322207}
2 files changed
tree: 5d28d91e9158060fff99cda892751eb4509f7781
  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. CPPLINT.cfg
  77. DEPS
  78. DIR_METADATA
  79. LICENSE
  80. LICENSE.chromium_os
  81. OWNERS
  82. PRESUBMIT.py
  83. PRESUBMIT_test.py
  84. PRESUBMIT_test_mocks.py
  85. README.md
  86. 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.