chrome-devtools-frontend 1.0.1668390 → 1.0.1672388

package/.agents/skills/devtools-ci/SKILL.md

@@ -0,0 +1,65 @@
+---
+name: devtools-ci
+description: >-
+  Triage and analyze Chromium/DevTools LUCI build results and trybot failures,
+  including high-level builder status, compile errors, and detailed test
+  failures. Use this to inspect trybot buildbucket (bb) results for a patchset
+  overview or to query ResultDB directly for comprehensive, actionable information
+  about specific test regressions and infrastructure issues.
+---
+
+# LUCI Build Triage & Analysis
+
+This skill provides access to specialized triage tools maintained within the
+`depot_tools` repository. These tools are used to inspect Buildbucket results
+and ResultDB test failures.
+
+## Environment & Auth Discovery
+
+- **Environment**: Always execute these scripts using **`vpython3`** instead
+  of `python3` to ensure all hermetic dependencies (like `httplib2`) are
+  satisfied.
+- **Authentication**: Use `bb auth-info` to proactively check if you are
+  logged into Buildbucket. If not, inform the user they must run `bb auth-login`.
+
+## Locating the Tools
+
+The triage scripts and their detailed documentation are located relative to
+the `depot_tools` installation:
+
+1.  **Locate Depot Tools**: Run `which gerrit_client.py` to find your local
+    `depot_tools` root.
+2.  **Navigation**:
+    - **Buildbucket (`bb_wrapper.py`)**: Found in `<DEPOT_TOOLS_ROOT>/agents/skills/buildbucket/`
+      - *Strengths*: High-level Build info (is it failing? what steps failed?),
+        compile errors, and infra issues.
+    - **Test Results (`luci_triage.py`)**: Found in `<DEPOT_TOOLS_ROOT>/agents/skills/luci-test-results/`
+      - *Strengths*: Detailed Test info (specific test case failures in
+        ResultDB).
+
+## Troubleshooting
+
+- **"No Artifacts Found"**: This usually occurs if:
+  1. The build failed so early (e.g., bot setup) that no artifacts were produced.
+  2. The build is too old and logs have been purged.
+  3. There is an authentication issue.
+  - **Fallback**: Try `bb log <build_id> <step_name>` to see the raw output
+    for the failed step.
+
+## Available Skills in Depot Tools
+
+Once you have located the `depot_tools` directory, read the following files
+to understand how to use each tool:
+
+- **`buildbucket`**: Used for high-level builder status and compile failures.
+  - Read: `<DEPOT_TOOLS_ROOT>/agents/skills/buildbucket/SKILL.md`
+- **`luci-test-results`**: Used for detailed ResultDB test failure analysis.
+  - Read: `<DEPOT_TOOLS_ROOT>/agents/skills/luci-test-results/SKILL.md`
+
+## Usage at Runtime
+
+When you need to triage a build:
+1.  Locate `depot_tools` as described above.
+2.  Read the relevant `SKILL.md` file from `depot_tools`.
+3.  Follow the instructions in that file to execute the Python scripts (e.g.,
+    `bb_wrapper.py` or `luci_triage.py`) using their absolute paths.

package/.agents/skills/fixing-skipped-tests/SKILL.md

@@ -16,17 +16,17 @@ This skill outlines the workflow for fixing skipped tests in the DevTools codeba
    - Ensure you use the instructions from the `devtools-version-control` skill to create and switch branches appropriately.
 
 3. **Search for the Skipped Tests**
-   - Search the codebase for the `<bugid>` to find skipped tests.
-   - You should look for occurrences like `it.skip('[crbug.com/<bugid>] ...', ...)` or skipped describes that mention the bug ID.
+   - Search the `test/TestExpectations` file for the `<bugid>` to find skipped tests.
+   - Tests are no longer skipped using `.skip` in the code, but rather by having a `[ Skip ]` expectation in `test/TestExpectations`.
 
 4. **Iterative Fix Process**
-   - **Step 1:** Remove `it.skip` or `describe.skip` for *one* of the tests associated with the bug.
+   - **Step 1:** Remove the `[ Skip ]` expectation for *one* of the tests associated with the bug in `test/TestExpectations` (or change it to `[ Pass Failure ]` if you are investigating flakiness).
    - **Step 2:** Re-run the specific test using its exact test ID (e.g., `npm run test path/to/foo.test.ts:test_name`) using the guidelines from the `devtools-verification` skill. If you are dealing with flaky tests, you can use the `--repeat=x` flag (e.g. `npm run test -- --repeat=20 path/to/foo.test.ts:test_name`) to run the test multiple times to reproduce the flakiness. This flag works for both E2E and unit tests.
    - **Step 3:** Analyze the test failure and make the necessary fixes to the code or the test itself.
    - **Step 4:** Re-run the test to ensure the fix is correct.
-   - **Step 5:** Remove the `[crbug.com/<bugid>]` prefix from the test name string if it is present.
-   - **Step 6:** Remove any comments directly above the test that explain the reason why the test was skipped (e.g., `// TODO(crbug...): Flaky`).
-   - **Step 7:** Apply the fix to the remaining tests, un-skipping them one by one or in batches, and verifying until all are passing.
+   - **Step 5:** Remove the `[crbug.com/<bugid>]` prefix from the test name string in the code if it is present.
+   - **Step 6:** Remove any comments directly above the test in the code that explain the reason why the test was skipped (e.g., `// TODO(crbug...): Flaky`).
+   - **Step 7:** Apply the fix to the remaining tests, un-skipping them one by one or in batches by modifying `test/TestExpectations`, and verifying until all are passing.
 
 5. **Verify Full Build**
    - Before finishing, run the full verification process (TypeScript checks, linters, full test run) as required by the repository best practices.

package/.agents/skills/gerrit-cli/SKILL.md

@@ -0,0 +1,53 @@
+---
+name: gerrit-cli
+description: >-
+  Interacts with the public Gerrit Code Review platform using depot_tools'
+  gerrit_client.py. Use this skill when asked to query public CLs, retrieve
+  file revisions, add patchset comments, vote on review labels, submit changes,
+  or abandon/restore public CLs. Do not use this skill for Google-internal
+  attention set updates or internal AI-assisted code reviews (CRUAS) which are
+  unsupported by the public API.
+---
+
+# Gerrit CLI Skill
+
+Execute public Gerrit Code Review commands using `gerrit_client.py` from
+depot_tools.
+
+## Prerequisites
+
+- Ensure `gerrit_client.py` is available in the system `PATH` (typically part of
+  `depot_tools`). If `gerrit_client.py` is not available in your environment,
+  stop execution immediately.
+- Use the wrapper script directly instead of an environment variable.
+  Substitute:
+  `vpython3 .agents/skills/gerrit-cli/scripts/gerrit_client_wrapper.py`
+  as the executable command in all examples and invocations.
+
+## Just-in-Time (JiT) Loading Guidance
+
+- Before running any Gerrit CLI command, read `references/commands.md`
+  to locate the required parameters and specific subcommand syntax.
+- Before querying public CLs, adding comments, voting, or submitting changes,
+  read `references/workflows.md` for step-by-step procedures.
+
+## Gotchas & Environment Constraints
+
+- **Specify Host**: Always supply the `--host` flag explicitly (e.g.
+  `--host https://chromium-review.googlesource.com`).
+- **Use JSON Output**: Always use the `--json_file=<path>` flag when querying
+  changes or fetching metadata to obtain structured, machine-readable output.
+
+> [!CAUTION]
+> **NEVER** use this to add patchset comments to an existing comment thread that
+> contains human reviewers in it. Using an agent to reply to a human is a
+> violation of Chromium's code of conduct.
+>
+> If the user requests this or you encounter this scenario as part of your work,
+> inform the user about which comment threads cannot be updated but otherwise
+> continue work.
+
+
+> [!NOTE]
+> This skill was adapted from the [Chromium Gerrit CLI skill](https://chromium.googlesource.com/chromium/agents/+/main/skills/gerrit-cli/)
+> (automatically rolled in from upstream).

package/.agents/skills/gerrit-cli/references/commands.md

@@ -0,0 +1,136 @@
+# Gerrit CLI Common Commands & Usage (Public)
+
+Run the tool directly using the wrapper script path with the `--help` flag:
+
+- `vpython3 .agents/skills/gerrit-cli/scripts/gerrit_client_wrapper.py --help`
+- `vpython3 .agents/skills/gerrit-cli/scripts/gerrit_client_wrapper.py changes --help`
+
+## Global Flags
+
+Use the following global flags for all commands:
+
+- `--host <url>` (e.g., `--host https://chromium-review.googlesource.com`).
+- `--project <project_name>` (e.g., `--project chromium/src`).
+- `--json_file <path>` (saves the structured response as a JSON file).
+
+______________________________________________________________________
+
+## Common Invocations
+
+### 1. Inspecting and Searching Changes
+
+- **Query active changes:**
+
+  ```bash
+  vpython3 .agents/skills/gerrit-cli/scripts/gerrit_client_wrapper.py \
+    changes \
+    --host https://chromium-review.googlesource.com \
+    --query "owner:self status:open"
+  ```
+
+- **View the content of a specific file in a change:**
+
+  **Note:** This command does not work with the `--json_file` flag, instead use
+  stdout redirection (`>`).
+
+  ```bash
+  vpython3 .agents/skills/gerrit-cli/scripts/gerrit_client_wrapper.py \
+    content \
+    --host https://chromium-review.googlesource.com \
+    --project <project> \
+    --change <change_id> \
+    --revision <revision> \
+    --path <file_path> \
+    > output_file
+  ```
+
+- **Get related changes:**
+
+  ```bash
+  vpython3 .agents/skills/gerrit-cli/scripts/gerrit_client_wrapper.py \
+    relatedchanges \
+    --host https://chromium-review.googlesource.com \
+    --change <change_id> --revision <revision>
+  ```
+
+### 2. Reviewing and Voting
+
+- **Add a patchset-level comment:**
+  ```bash
+  vpython3 .agents/skills/gerrit-cli/scripts/gerrit_client_wrapper.py \
+    addpatchsetcomment \
+    --host https://chromium-review.googlesource.com \
+    --change <change_id> --revision <revision> \
+    --message "Review findings: <message>"
+  ```
+- **Vote on a review label (e.g., Code-Review +1):**
+  ```bash
+  vpython3 .agents/skills/gerrit-cli/scripts/gerrit_client_wrapper.py \
+    setlabel \
+    --host https://chromium-review.googlesource.com \
+    --change <change_id> \
+    --label Code-Review 1
+  ```
+
+### 3. Actions and Shepherding
+
+- **Submit/Merge a change:**
+  ```bash
+  vpython3 .agents/skills/gerrit-cli/scripts/gerrit_client_wrapper.py \
+    submitchange \
+    --host https://chromium-review.googlesource.com \
+    --change <change_id>
+  ```
+- **Abandon a change:**
+  ```bash
+  vpython3 .agents/skills/gerrit-cli/scripts/gerrit_client_wrapper.py \
+    abandon \
+    --host https://chromium-review.googlesource.com \
+    --change <change_id> \
+    --message "<reason>"
+  ```
+- **Restore an abandoned change:**
+  ```bash
+  vpython3 .agents/skills/gerrit-cli/scripts/gerrit_client_wrapper.py \
+    restore \
+    --host https://chromium-review.googlesource.com \
+    --change <change_id> \
+    --message "<reason>"
+  ```
+
+______________________________________________________________________
+
+## Just-in-Time Help
+
+Explore the built-in CLI help for additional subcommands or advanced syntax:
+
+- Display all top-level commands:
+  `vpython3 .agents/skills/gerrit-cli/scripts/gerrit_client_wrapper.py --help`
+- Display help for a specific subcommand:
+  ```bash
+  vpython3 .agents/skills/gerrit-cli/scripts/gerrit_client_wrapper.py \
+    help <command>
+  ```
+
+
+## Advanced / Escape Hatch: Arbitrary REST API Calls (`rawapi`)
+
+If the built-in subcommands do not cover a specific action or metadata query, you can use the `rawapi` subcommand to execute arbitrary HTTP requests against the Gerrit REST API.
+
+- **Endpoint Reference**: [Gerrit REST API - Changes](https://gerrit-review.googlesource.com/Documentation/rest-api-changes.html)
+
+### Usage
+
+```bash
+vpython3 .agents/skills/gerrit-cli/scripts/gerrit_client_wrapper.py \
+  rawapi \
+  --host https://chromium-review.googlesource.com \
+  --path "/changes/<change_id>/detail?o=SUBMITTABLE" \
+  --json_file output.json
+```
+
+- **Options**:
+  - `--path`: HTTP path of the API endpoint (e.g. `/changes/<change_id>/revisions/current/mergeable`).
+  - `--method`: HTTP method (GET, POST, PUT, DELETE). Defaults to GET.
+  - `--body`: JSON string body for write requests (e.g., POST/PUT).
+  - `--accept_status`: Comma-separated list of successful HTTP status codes.

package/.agents/skills/gerrit-cli/references/workflows.md

@@ -0,0 +1,63 @@
+# Gerrit CLI Workflows (Public)
+
+## 1. Change List Review Workflow
+
+Execute these steps in chronological order to review a Change List (CL) when
+provided with a link or ID:
+
+1. **Query CL Metadata**: Retrieve CL details and verify its current status:
+   ```bash
+   vpython3 .agents/skills/gerrit-cli/scripts/gerrit_client_wrapper.py \
+     changes \
+     --host https://chromium-review.googlesource.com \
+     --query "change:<id>"
+   ```
+2. **Fetch File Contents**: Retrieve the content of specific files modified in
+   the CL:
+   ```bash
+   vpython3 .agents/skills/gerrit-cli/scripts/gerrit_client_wrapper.py \
+     content \
+     --host https://chromium-review.googlesource.com \
+     --project <project> \
+     --change <change_id> --revision current --path <file_path>
+   ```
+3. **Analyze Local Modifications**: Inspect the fetched contents and local diffs
+   for any logic or formatting issues.
+4. **Add Review Comment**: Post a patchset-level comment containing the review
+   findings:
+   ```bash
+   vpython3 .agents/skills/gerrit-cli/scripts/gerrit_client_wrapper.py \
+     addpatchsetcomment \
+     --host https://chromium-review.googlesource.com \
+     --change <change_id> --revision current \
+     --message "Review findings: ..."
+   ```
+
+## 2. Shepherding & Submission Workflow
+
+Execute these steps in chronological order to approve and merge a Change List:
+
+1. **Check Related Changes**: Retrieve the status of all related changes to
+   ensure there are no unresolved blockers:
+   ```bash
+   vpython3 .agents/skills/gerrit-cli/scripts/gerrit_client_wrapper.py \
+     relatedchanges \
+     --host https://chromium-review.googlesource.com \
+     --change <change_id> --revision current
+   ```
+2. **Vote on Review Labels**: Apply the required Code-Review approval vote:
+   ```bash
+   vpython3 .agents/skills/gerrit-cli/scripts/gerrit_client_wrapper.py \
+     setlabel \
+     --host https://chromium-review.googlesource.com \
+     --change <change_id> \
+     --label Code-Review 1
+   ```
+3. **Submit Change**: Merge the change once all CQ presubmits pass and all
+   approval requirements are satisfied:
+   ```bash
+   vpython3 .agents/skills/gerrit-cli/scripts/gerrit_client_wrapper.py \
+     submitchange \
+     --host https://chromium-review.googlesource.com \
+     --change <change_id>
+   ```

package/.agents/skills/gerrit-cli/scripts/import_upstream.py

@@ -0,0 +1,112 @@
+#!/usr/bin/env python3
+# Copyright 2026 The Chromium Authors
+# Use of this source code is governed by a BSD-style license that can be
+# found in the LICENSE file.
+"""Imports the Gerrit CLI skill from upstream and applies DevTools revisions.
+
+No external checkouts (like chromium/src) are required. The script downloads
+the skill directly from the public Git repository.
+"""
+
+import io
+import re
+import sys
+import tarfile
+import urllib.request
+from pathlib import Path
+
+UPSTREAM_URL = "https://chromium.googlesource.com/chromium/agents/+archive/refs/heads/main/skills/gerrit-cli.tar.gz"
+
+def fetch_upstream_skill(target_dir: Path):
+    print(f"Downloading upstream skill from {UPSTREAM_URL}...")
+    try:
+        req = urllib.request.Request(UPSTREAM_URL,
+                                     headers={'User-Agent': 'Mozilla/5.0'})
+        with urllib.request.urlopen(req) as response:
+            tar_data = response.read()
+    except Exception as e:
+        print(f"Failed to download upstream skill: {e}")
+        sys.exit(1)
+
+    print(f"Extracting to {target_dir}...")
+    target_dir.mkdir(parents=True, exist_ok=True)
+    with tarfile.open(fileobj=io.BytesIO(tar_data), mode='r:gz') as tar:
+        tar.extractall(path=target_dir)
+
+
+def apply_devtools_revisions(target_dir: Path):
+    print("Applying DevTools-specific adaptations...")
+
+    # 2. Update SKILL.md
+    skill_md_path = target_dir / "SKILL.md"
+    if skill_md_path.exists():
+        content = skill_md_path.read_text()
+
+        # Re-route wrapper script path
+        content = re.sub(
+            r'(?:v)?python3\s+agents/shared/skills/gerrit-cli/scripts/gerrit_client_wrapper.py',
+            'vpython3 .agents/skills/gerrit-cli/scripts/gerrit_client_wrapper.py',
+            content)
+
+        # Add attribution note at the bottom
+        attribution = """
+> [!NOTE]
+> This skill was adapted from the [Chromium Gerrit CLI skill](https://chromium.googlesource.com/chromium/agents/+/main/skills/gerrit-cli/)
+> (automatically rolled in from upstream).
+"""
+        if "> [!NOTE]" not in content:
+            content += "\n" + attribution
+
+        skill_md_path.write_text(content)
+        print("  - Adapted SKILL.md")
+
+    # 3. Update references/commands.md and references/workflows.md
+    for filename in ["commands.md", "workflows.md"]:
+        ref_path = target_dir / "references" / filename
+        if ref_path.exists():
+            c = ref_path.read_text()
+
+            # Path & executable transformations
+            c = re.sub(r'(?:v)?python3\s+agents/shared/skills/gerrit-cli/',
+                       'vpython3 .agents/skills/gerrit-cli/', c)
+
+            ref_path.write_text(c)
+            print(f"  - Adapted references/{filename}")
+
+
+def validate_gerrit_client_wrapper(skill_dir: Path):
+    print("Validating gerrit_client_wrapper.py...")
+    import json, subprocess, tempfile
+    wrapper = skill_dir / "scripts" / "gerrit_client_wrapper.py"
+    with tempfile.TemporaryDirectory() as tmp:
+        json_file = Path(tmp) / "out.json"
+        try:
+            subprocess.run([
+                "vpython3",
+                str(wrapper), "changes", "--query", "change:8147179", "--host",
+                "https://chromium-review.googlesource.com", "--json_file",
+                str(json_file)
+            ],
+                           check=True,
+                           capture_output=True)
+            data = json.loads(json_file.read_text())
+            if not data or data[0].get("_number") != 8147179:
+                raise ValueError(f"Invalid response: {data}")
+            print("  - Validation passed successfully!")
+        except Exception as e:
+            stderr = getattr(e, "stderr", b"").decode(errors="replace")
+            print(f"Validation FAILED: {e}\n{stderr}")
+            sys.exit(1)
+
+
+
+def main():
+    skill_dir = Path(__file__).parent.parent.resolve()
+    fetch_upstream_skill(skill_dir)
+    apply_devtools_revisions(skill_dir)
+    validate_gerrit_client_wrapper(skill_dir)
+    print("Upstream sync completed successfully!")
+
+
+if __name__ == "__main__":
+    main()

package/config/typescript/tsconfig.eslint.json

@@ -13,7 +13,7 @@
       "webworker",
       "webworker.iterable"
     ],
-    "outDir": "ignored-for-vscode"
+    "noEmit": true
   },
   "include": [
     "../../front_end/**/*.ts",

package/docs/contributing/infrastructure.md

@@ -257,7 +257,13 @@ because they picked up the test as it was being touched.
 
 You can skip Flake Detection for your tests by adding the `Skip-Flake-Detection`
 CL footer (see example [CL](https://crrev.com/c/6994031)). Make sure you use the
-full path to your test.
+full path to your test. If you need to skip multiple tests, you can repeat the footer:
+```
+Skip-Flake-Detection: test/e2e/foo.test.ts
+Skip-Flake-Detection: test/e2e/bar.test.ts
+```
+
+You can also skip Flake Detection for multiple tests using a glob pattern by adding the `Skip-Flake-Detection-Pattern` CL footer. For example: `Skip-Flake-Detection-Pattern: test/e2e/performance/*`.
 
 ### Common build failures
 

package/docs/contributing/settings-experiments-features.md

@@ -78,12 +78,12 @@ This step is optional. If you want the `base::Feature` to be controllable via th
 
 Prerequisite: The `base::Feature` needs to be have been added to `chrome://flags`.
 
-#### Step 1: Create a HostExperiment in the DevTools repository
+#### Step 1: Create an Experiment in the DevTools repository
 
 Register the experiment in [`MainImpl.ts`](https://crsrc.org/c/third_party/devtools-frontend/src/front_end/entrypoints/main/MainImpl.ts;l=343)
 
 ```ts
-Root.Runtime.experiments.registerHostExperiment({
+Root.Runtime.experiments.register({
   name: Root.ExperimentNames.ExperimentName.DURABLE_MESSAGES,
   // Short description of the experiment, shown to users
   title: 'Durable Messages',
@@ -147,12 +147,6 @@ in the DevTools repository. The label can be anything you like but make sure it
 
 [Example CL](https://crrev.com/c/4915777)
 
-## Deprecated: DevTools experiments
-
-Previously, DevTools experiments that lacked a Chrome component were managed separately. This
-system is now deprecated. All legacy experiments are being migrated to the `base::Feature`
-framework to streamline development.
-
 ## A/B Testing with Finch and base::Feature
 
 `base::Feature` flags can be used with Finch to conduct A/B testing by toggling feature flags for a defined percentage of users. A/B testing can be a good way of testing the waters. However, since the time to get meaningful metrics may take a long time, it shouldn't be used to get feedback on options quickly.

package/docs/ecosystem/automatic_workspace_folders.md

@@ -66,25 +66,6 @@ An example `com.chrome.devtools.json` would look like this:
 Chromium DevTools will only attempt to load the `com.chrome.devtools.json` when
 the origin of the inspected page is `localhost`.
 
-## Setup
-
-In M-136, which is in Canary channel at the time of this writing, the relevant
-flags have been enabled by default (as of 2025-03-16). In earlier versions of
-M-136 and in M-135, this feature is disabled by default. To use it, you need to
-turn on two feature flags in `about:flags`:
-
--   [chrome://flags#devtools-project-settings](chrome://flags#devtools-project-settings)
--   [chrome://flags#devtools-automatic-workspace-folders](chrome://flags#devtools-automatic-workspace-folders)
-
-![](./images/automatic_workspace_folders_flags.png)
-
-Instead of enabling the feature via `about:flags`, you can instead also enable
-them from the command line:
-
-```bash
-google-chrome-canary --enable-features=DevToolsWellKnown,DevToolsAutomaticFileSystems
-```
-
 ## Usage
 
 To check if your setup is correct, you can try out Benedikt’s

package/eslint.config.mjs

@@ -693,8 +693,8 @@ export default defineConfig([
     },
   },
   {
-    name: 'Front-end core files',
-    files: ['front_end/core/**/*.ts'],
+    name: 'Front-end core and models files',
+    files: ['front_end/core/**/*.ts', 'front_end/models/**/*.ts'],
     rules: {
       '@devtools/no-instance-of-migrated-singletons': 'error',
     },

package/front_end/core/common/Lazy.ts

@@ -8,11 +8,11 @@ const ERROR_STATE = Symbol('error');
 /**
  * Very basic memoizer. Will only invoke its callback the first time, returning the cached value all subsequent calls.
  */
-export function lazy<T>(producer: () => T): () => symbol | T {
+export function lazy<T, A extends unknown[] = []>(producer: (...args: A) => T): (...args: A) => T {
   let value: T|typeof ERROR_STATE|typeof UNINITIALIZED = UNINITIALIZED;
   let error: Error = new Error('Initial');
 
-  return (): symbol|T => {
+  return (...args: A): T => {
     if (value === ERROR_STATE) {
       throw error;
     } else if (value !== UNINITIALIZED) {
@@ -20,7 +20,7 @@ export function lazy<T>(producer: () => T): () => symbol | T {
     }
 
     try {
-      value = producer();
+      value = producer(...args);
       return value;
     } catch (err) {
       error = err instanceof Error ? err : new Error(err);

package/front_end/core/common/SettingRegistration.ts

@@ -282,13 +282,6 @@ export interface SettingRegistration {
    */
   disabledCondition?: (config?: Root.Runtime.HostConfig) => DisabledConditionResult;
 
-  /**
-   * If a setting is deprecated, define this notice to show an appropriate warning according to the `warning` property.
-   * If `disabled` is set, the setting will be disabled in the settings UI. In that case, `experiment` optionally can be
-   * set to link to an experiment (by experiment name). The information icon in the settings UI can then be clicked to
-   * jump to the experiment. If a setting is not disabled, the experiment entry will be ignored.
-   */
-  deprecationNotice?: {disabled: boolean, warning: () => Platform.UIString.LocalizedString, experiment?: string};
   /**
    * See {@link LearnMore} for more info.
    */

package/front_end/core/common/Settings.ts

@@ -494,23 +494,6 @@ export class SettingsStorage {
   }
 }
 
-export class Deprecation {
-  readonly disabled: boolean;
-  readonly warning: Platform.UIString.LocalizedString;
-  readonly experiment?: Root.Runtime.Experiment|Root.Runtime.HostExperiment;
-
-  constructor({deprecationNotice}: SettingRegistration) {
-    if (!deprecationNotice) {
-      throw new Error('Cannot create deprecation info for a non-deprecated setting');
-    }
-    this.disabled = deprecationNotice.disabled;
-    this.warning = deprecationNotice.warning();
-    this.experiment = deprecationNotice.experiment ?
-        Root.Runtime.experiments.allConfigurableExperiments().find(e => e.name === deprecationNotice.experiment) :
-        undefined;
-  }
-}
-
 export class Setting<V> {
   #registration: SettingRegistration|null = null;
   #type: SettingType|null = null;
@@ -520,7 +503,6 @@ export class Setting<V> {
   #serializer: Serializer<unknown, V> = JSON;
   #hadUserAction?: boolean;
   #disabled?: boolean;
-  #deprecation: Deprecation|null = null;
   #loggedInitialAccess = false;
   #logSettingAccess?: (name: string, value: number|string|boolean) => Promise<void>;
   readonly #console: Console;
@@ -691,16 +673,6 @@ export class Setting<V> {
     if (registration.settingType) {
       this.#type = registration.settingType;
     }
-    const {deprecationNotice} = registration;
-    if (deprecationNotice?.disabled) {
-      const experiment = deprecationNotice.experiment ?
-          Root.Runtime.experiments.allConfigurableExperiments().find(e => e.name === deprecationNotice.experiment) :
-          undefined;
-      if ((!experiment || experiment.isEnabled())) {
-        this.set(this.defaultValue);
-        this.setDisabled(true);
-      }
-    }
   }
 
   type(): SettingType|null {
@@ -758,16 +730,6 @@ export class Setting<V> {
     return this.#registration?.learnMore ?? null;
   }
 
-  get deprecation(): Deprecation|null {
-    if (!this.#registration || !this.#registration.deprecationNotice) {
-      return null;
-    }
-    if (!this.#deprecation) {
-      this.#deprecation = new Deprecation(this.#registration);
-    }
-    return this.#deprecation;
-  }
-
   private printSettingsSavingError(message: string, value: string): void {
     const errorMessage =
         'Error saving setting with name: ' + this.name + ', value length: ' + value.length + '. Error: ' + message;