[functions] Support @media within @function

This adds support for "functional" media queries, which evaluate
during value computation rather than during RuleSet building.
Although it would probably be possible to also handle @media
within @function on the rule level rather than value level,
the value level approach was chosen since it will be required
anyway for the if() notation in the future [1].

Since the existing invalidation path for @media is RuleSet based,
this CL implements a new invalidation strategy:

 - ComputedStyles affected by functional media are marked as such.
 - Functional MQs are evaluated during StyleCascade, and the results
   are stored on StyleEngine.
 - When media values change, we check the stored results for changes.
   If there was a change in evaluation, we invalidate all elements
   marked as affected by functional media.

It is possible invalidate even more narrowly, e.g. track which
specific elements depend on which specific media queries, but for now
this seems to strike a reasonable balance.

StyleEngine must also keep track of some flags from the functional
MQ evaluation, otherwise ParentLayoutUpgrade will not understand that
there is a parent frame dependency.

[1] https://drafts.csswg.org/css-values-5/#if-notation

Bug: 325504770
Change-Id: I5ac00afc165826e9ce7789fba7fa6e4f0d6c0bf6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6234272
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1417299}
13 files changed
tree: 73a0c4a9faf718ddb0d1ccb570b06c117c4c0cec
  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. .clang-format
  50. .clang-tidy
  51. .clangd
  52. .git-blame-ignore-revs
  53. .gitallowed
  54. .gitattributes
  55. .gitignore
  56. .gitmodules
  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. CPPLINT.cfg
  68. CRYPTO_OWNERS
  69. DEPS
  70. DIR_METADATA
  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.