chrome-devtools-frontend 1.0.1665921 → 1.0.1666631

package/front_end/third_party/chromium/README.chromium

@@ -1,7 +1,7 @@
 Name: Dependencies sourced from the upstream `chromium` repository
 URL: Internal
 Version: N/A
-Revision: 8e5dd02f11d866b080045c734fbb8cbb99e9064c
+Revision: 21a9cb538b3a304c31bcb2fefa6a5f5f16d49ea8
 Update Mechanism: Manual (https://crbug.com/428069060)
 License: BSD-3-Clause
 License File: LICENSE

package/front_end/ui/components/text_editor/AiCodeGenerationProvider.ts

@@ -384,8 +384,7 @@ export class AiCodeGenerationProvider {
       this.#aiCodeGenerationConfig.onResponseReceived();
       return;
     } catch (e) {
-      if (e instanceof Host.DispatchHttpRequestClient.DispatchHttpRequestError &&
-          e.type === Host.DispatchHttpRequestClient.ErrorType.ABORT) {
+      if (e instanceof Host.AidaClient.AidaAbortError) {
         return;
       }
       AiCodeGeneration.debugLog('Error while fetching code generation suggestions from AIDA', e);

package/package.json

@@ -27,7 +27,6 @@
     "lint": "vpython3 third_party/node/node.py --output scripts/test/run_lint_check.mjs",
     "prebuild": "gn gen out/Default",
     "rdb": "rdb stream -new -realm chromium:public --",
-    "rdb-exonerate": "npm run rdb -- vpython3 third_party/node/node.py --output scripts/run_on_target.mjs gen/test/exonerate.js",
     "start": "vpython3 third_party/node/node.py --output scripts/run_start.mjs",
     "webtest": "vpython3 third_party/node/node.py --output scripts/npm_test.js",
     "watch": "npm run build -- --watch",
@@ -92,5 +91,5 @@
     "webidl2": "24.5.0",
     "yargs": "17.7.2"
   },
-  "version": "1.0.1665921"
+  "version": "1.0.1666631"
 }

package/front_end/models/issues_manager/descriptions/SameSiteExcludeContextDowngradeRead.md

@@ -1,8 +0,0 @@
-# Migrate entirely to HTTPS to have cookies sent to same-site subresources
-
-A cookie was not sent to {PLACEHOLDER_destination} origin from {PLACEHOLDER_origin} context.
-Because this cookie would have been sent across schemes on the same site, it was not sent.
-This behavior enhances the `SameSite` attribute’s protection of user data from request forgery by network attackers.
-
-Resolve this issue by migrating your site (as defined by the eTLD+1) entirely to HTTPS.
-It is also recommended to mark the cookie with the `Secure` attribute if that is not already the case.

package/front_end/models/issues_manager/descriptions/SameSiteExcludeContextDowngradeSet.md

@@ -1,8 +0,0 @@
-# Migrate entirely to HTTPS to allow cookies to be set by same-site subresources
-
-A cookie was not set by {PLACEHOLDER_origin} origin in {PLACEHOLDER_destination} context.
-Because this cookie would have been set across schemes on the same site, it was blocked.
-This behavior enhances the `SameSite` attribute’s protection of user data from request forgery by network attackers.
-
-Resolve this issue by migrating your site (as defined by the eTLD+1) entirely to HTTPS.
-It is also recommended to mark the cookie with the `Secure` attribute if that is not already the case.

package/front_end/models/issues_manager/descriptions/SameSiteExcludeNavigationContextDowngrade.md

@@ -1,8 +0,0 @@
-# Migrate entirely to HTTPS to have cookies sent on same-site requests
-
-A cookie was not sent to {PLACEHOLDER_destination} origin from {PLACEHOLDER_origin} context on a navigation.
-Because this cookie would have been sent across schemes on the same site, it was not sent.
-This behavior enhances the `SameSite` attribute’s protection of user data from request forgery by network attackers.
-
-Resolve this issue by migrating your site (as defined by the eTLD+1) entirely to HTTPS.
-It is also recommended to mark the cookie with the `Secure` attribute if that is not already the case.

package/front_end/models/issues_manager/descriptions/SameSiteWarnCrossDowngradeRead.md

@@ -1,8 +0,0 @@
-# Migrate entirely to HTTPS to continue having cookies sent to same-site subresources
-
-A cookie is being sent to {PLACEHOLDER_destination} origin from {PLACEHOLDER_origin} context.
-Because this cookie is being sent across schemes on the same site, it will not be sent in a future version of Chrome.
-This behavior enhances the `SameSite` attribute’s protection of user data from request forgery by network attackers.
-
-Resolve this issue by migrating your site (as defined by the eTLD+1) entirely to HTTPS.
-It is also recommended to mark the cookie with the `Secure` attribute if that is not already the case.

package/front_end/models/issues_manager/descriptions/SameSiteWarnCrossDowngradeSet.md

@@ -1,8 +0,0 @@
-# Migrate entirely to HTTPS to continue allowing cookies to be set by same-site subresources
-
-A cookie is being set by {PLACEHOLDER_origin} origin in {PLACEHOLDER_destination} context.
-Because this cookie is being set across schemes on the same site, it will be blocked in a future version of Chrome.
-This behavior enhances the `SameSite` attribute’s protection of user data from request forgery by network attackers.
-
-Resolve this issue by migrating your site (as defined by the eTLD+1) entirely to HTTPS.
-It is also recommended to mark the cookie with the `Secure` attribute if that is not already the case.

package/front_end/models/issues_manager/descriptions/SameSiteWarnStrictLaxDowngradeStrict.md

@@ -1,8 +0,0 @@
-# Migrate entirely to HTTPS to continue having cookies sent on same-site requests
-
-A cookie is being sent to {PLACEHOLDER_destination} origin from {PLACEHOLDER_origin} context on a navigation.
-Because this cookie is being sent across schemes on the same site, it will not be sent in a future version of Chrome.
-This behavior enhances the `SameSite` attribute’s protection of user data from request forgery by network attackers.
-
-Resolve this issue by migrating your site (as defined by the eTLD+1) entirely to HTTPS.
-It is also recommended to mark the cookie with the `Secure` attribute if that is not already the case.