Google Git
Sign in
chromium / chromium / src / 30c667b51a896929158c79b5ff0544285d383aa2
commit30c667b51a896929158c79b5ff0544285d383aa2[log] [tgz]
authorNoam Rosenthal <nrosenthal@chromium.org>Tue Nov 12 10:21:20 2024
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Nov 12 10:21:20 2024
tree377879c951ac5f966482251c536c1f6a6ec62566
parent665bc018c3f4e486f67d7ad13eebb801783f9486 [diff]
View transition layered capture: determine geometry based on box model
Relanding with a build fix(spurious -blink include)

Instead of capturing the border offset, we capture the following
layout sizes to determine sizing, in addition to the border box:
- padding box
- content box
- The box-sizing property

- In layered capture mode, we use the content box size as the
  reference box for positioning the snapshot, so that padding take
  effect.
- The ::view-transition-image-pair pseudo-element now has
  position:relative so that it gets affected by padding. It has the
  content box size.
- The width/height of the group is determined by the box-sizing
  property, and it receives the computed padding.

Bug: 375395117
Change-Id: Ide0c001ea17582bb854a2fe678965504e0d4c0d5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6011700
Reviewed-by: Mike West <mkwst@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: Noam Rosenthal <nrosenthal@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1381667}
19 files changed
tree: 377879c951ac5f966482251c536c1f6a6ec62566
  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. crypto/
  16. dbus/
  17. device/
  18. docs/
  19. extensions/
  20. fuchsia_web/
  21. gin/
  22. google_apis/
  23. gpu/
  24. headless/
  25. infra/
  26. ios/
  27. ipc/
  28. media/
  29. mojo/
  30. native_client_sdk/
  31. net/
  32. pdf/
  33. ppapi/
  34. printing/
  35. remoting/
  36. rlz/
  37. sandbox/
  38. services/
  39. skia/
  40. sql/
  41. storage/
  42. styleguide/
  43. testing/
  44. third_party/
  45. tools/
  46. ui/
  47. url/
  48. webkit/
  49. clank
  50. internal
  51. ios_internal
  52. native_client
  53. signing_keys
  54. v8
  55. .clang-format
  56. .clang-tidy
  57. .clangd
  58. .git-blame-ignore-revs
  59. .gitallowed
  60. .gitattributes
  61. .gitignore
  62. .gitmodules
  63. .gn
  64. .mailmap
  65. .rustfmt.toml
  66. .vpython3
  67. .yapfignore
  68. ATL_OWNERS
  69. AUTHORS
  70. BUILD.gn
  71. CODE_OF_CONDUCT.md
  72. codereview.settings
  73. CPPLINT.cfg
  74. CRYPTO_OWNERS
  75. DEPS
  76. DIR_METADATA
  77. LICENSE
  78. LICENSE.chromium_os
  79. OWNERS
  80. PRESUBMIT.py
  81. PRESUBMIT_test.py
  82. PRESUBMIT_test_mocks.py
  83. README.md
  84. 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.