Google Git
Sign in
chromium / chromium / src / f367255728dff945495d001e6457371f5c617a75
commitf367255728dff945495d001e6457371f5c617a75[log] [tgz]
authorAri Chivukula <arichiv@chromium.org>Thu Oct 21 21:34:46 2021
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Oct 21 21:34:46 2021
treec72a8bf0ea6247c220fc91d00dff65b02ad8ba58
parent620a674c8a0cc8f08a63dd874f4d61f5ee6d6c56 [diff]
[Deprecation Console->Issue] (2) Consolidate DeprecationInfo

Right now, the DeprecationInfo struct duplicates info between the
message, id, and anticipated_removal. Let's restructure this to break
out the struct info into components, and auto-detect which message
printer to use based in the info set. This is a noop, and won't modify
any existing messages, but paves the way for sending the detailed info
to a DevTools Issue.

This is a part of a set of CLs:
(1) Remove legacy CSS Deprecation path
(2) Consolidate DeprecationInfo
(3) Streamline redundant Deprecation messages
(4) Add features for console/issue deprecation
(5) Fix feature status detail link
(6) Implement Issue Deprecation
(7) Launch Issue Deprecation
(8) Remove Console Deprecation

Bug: 1248484
Change-Id: Ib6a68858b29bfe3d3bb60f27dc92f9290e1898b8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3234988
Auto-Submit: Ari Chivukula <arichiv@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Ari Chivukula <arichiv@chromium.org>
Cr-Commit-Position: refs/heads/main@{#934044}
1 file changed
tree: c72a8bf0ea6247c220fc91d00dff65b02ad8ba58
  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. .rustfmt.toml
  62. .vpython
  63. .vpython3
  64. .yapfignore
  65. AUTHORS
  66. BUILD.gn
  67. CODE_OF_CONDUCT.md
  68. codereview.settings
  69. DEPS
  70. DIR_METADATA
  71. ENG_REVIEW_OWNERS
  72. LICENSE
  73. LICENSE.chromium_os
  74. OWNERS
  75. PRESUBMIT.py
  76. PRESUBMIT_test.py
  77. PRESUBMIT_test_mocks.py
  78. README.md
  79. 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.