Google Git
Sign in
chromium / chromium / src / d60d6dd1a564116ab6243a299278d12740b3b552
commitd60d6dd1a564116ab6243a299278d12740b3b552[log] [tgz]
authorAndreu Botella <abotella@igalia.com>Thu Oct 31 09:57:32 2024
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Oct 31 09:57:32 2024
tree9cd3540a48480dbfec2f22635d2bb5af9e5a6b58
parentc5259e684e7afd2305878d5acdaf1e532591bf94 [diff]
[line-clamp] Update crbug for new disable-css-line-clamp test failures

WPT PR #48729 (https://github.com/web-platform-tests/wpt/pull/48729)
updated `-webkit-line-clamp` tests to specifically test that lines
after clamp are not painted. This is the behavior in the spec, and the
one Chromium has with the `CSSLineClamp` feature, which is
experimental; but it is different from the legacy behavior.

We have a virtual test suite, `virtual/disable-css-line-clamp`, that
disables this feature, to make sure the legacy behavior does not
regress while it is still enabled by default. Therefore, these test
updates introduced failures in that virtual test suite. This patch
moves them with the rest of `virtual/disable-css-line-clamp` and
changes their crbug to the line-clamp issue.

Bug: 40336192, 374822356
Change-Id: I6679950344b6bc9e07870ca5ec2460ec03f7d5e9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5975670
Reviewed-by: Koji Ishii <kojii@chromium.org>
Commit-Queue: Andreu Botella <abotella@igalia.com>
Cr-Commit-Position: refs/heads/main@{#1376194}
1 file changed
tree: 9cd3540a48480dbfec2f22635d2bb5af9e5a6b58
  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.