Revert "Store base ComputedStyle on main ComputedStyle"

This reverts commit 4b03422f438df0087ae88aca943b1f55d133bbfa.

Reason for revert: Performance regressions, crbug.com/1227488

Original change's description:
> Store base ComputedStyle on main ComputedStyle
>
> Instead of storing the base ComputedStyle on ElementAnimations, this
> CL suggesting storing it on the (animated) ComputedStyle itself.
> Any animated ComputedStyle produced by StyleResolver gets an associated
> "StyleBaseData" object, which contains the base ComputedStyle and
> the base "important set".
>
> Even without other considerations, this appears to be far simpler to
> deal with than storing it "on the side", however, the true motivation
> for this change is related to container queries:
>
> Since container queries can run style recalc multiple times for the
> same element, we essentially pass through multiple style resolves where
> the "old style" (i.e. current style on the Element) changes each time.
> In other words, there can be multiple apparent "old styles" (some older
> than others). In order to deal with transitions correctly, it's
> necessary to get the *base style* of the *oldest* of the old styles
> (so to speak). Having to keep track of the "true old style" and
> "true old *base* style" separately exceeds my pain threshold. It seems
> far more sensible to simply make the base style of any ComputedStyle
> reachable from *that* ComputedStyle. That way we only need to keep
> track of *one* ComputedStyle to access either the animated style,
> or the associated base style.
>
> Bug: 1180159
>
> Change-Id: Ia43755438c0e2ba7bf8281826c5621c7f3dbf55d
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3010116
> Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
> Reviewed-by: Rune Lillesveen <futhark@chromium.org>
> Reviewed-by: Kevin Ellis <kevers@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#899510}

Bug: 1180159
Change-Id: I90a269f6139d998375ebc87782bc3f519ae4c875
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3017983
Auto-Submit: Anders Hartvoll Ruud <andruud@chromium.org>
Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#899976}
16 files changed
tree: 6b67219ddea546991e156cc8287f34836185dba4
  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. cloud_print/
  13. codelabs/
  14. components/
  15. content/
  16. courgette/
  17. crypto/
  18. dbus/
  19. device/
  20. docs/
  21. extensions/
  22. fuchsia/
  23. gin/
  24. google_apis/
  25. google_update/
  26. gpu/
  27. headless/
  28. infra/
  29. ios/
  30. ipc/
  31. jingle/
  32. media/
  33. mojo/
  34. native_client_sdk/
  35. net/
  36. pdf/
  37. ppapi/
  38. printing/
  39. remoting/
  40. rlz/
  41. sandbox/
  42. services/
  43. skia/
  44. sql/
  45. storage/
  46. styleguide/
  47. testing/
  48. third_party/
  49. tools/
  50. ui/
  51. url/
  52. weblayer/
  53. .clang-format
  54. .clang-tidy
  55. .eslintrc.js
  56. .git-blame-ignore-revs
  57. .gitattributes
  58. .gitignore
  59. .gn
  60. .mailmap
  61. .vpython
  62. .vpython3
  63. .yapfignore
  64. AUTHORS
  65. BUILD.gn
  66. CODE_OF_CONDUCT.md
  67. codereview.settings
  68. DEPS
  69. DIR_METADATA
  70. ENG_REVIEW_OWNERS
  71. LICENSE
  72. LICENSE.chromium_os
  73. OWNERS
  74. PRESUBMIT.py
  75. PRESUBMIT_test.py
  76. PRESUBMIT_test_mocks.py
  77. README.md
  78. 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.