@mcp-b/chrome-devtools-mcp 1.1.2 → 1.1.3

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/SourceFrameIssuesManager.js

@@ -1,81 +0,0 @@
-// Copyright 2020 The Chromium Authors
-// Use of this source code is governed by a BSD-style license that can be
-// found in the LICENSE file.
-import * as Common from '../../core/common/common.js';
-import * as Bindings from '../../models/bindings/bindings.js';
-import * as Workspace from '../../models/workspace/workspace.js';
-import { ContentSecurityPolicyIssue, trustedTypesPolicyViolationCode, trustedTypesSinkViolationCode, } from './ContentSecurityPolicyIssue.js';
-import { toZeroBasedLocation } from './Issue.js';
-import { getIssueTitleFromMarkdownDescription } from './MarkdownIssueDescription.js';
-import { PropertyRuleIssue } from './PropertyRuleIssue.js';
-import { lateImportStylesheetLoadingCode } from './StylesheetLoadingIssue.js';
-export class SourceFrameIssuesManager {
-    issuesManager;
-    #sourceFrameMessageManager = new Bindings.PresentationConsoleMessageHelper.PresentationSourceFrameMessageManager();
-    constructor(issuesManager) {
-        this.issuesManager = issuesManager;
-        this.issuesManager.addEventListener("IssueAdded" /* Events.ISSUE_ADDED */, this.#onIssueAdded, this);
-        this.issuesManager.addEventListener("FullUpdateRequired" /* Events.FULL_UPDATE_REQUIRED */, this.#onFullUpdateRequired, this);
-    }
-    #onIssueAdded(event) {
-        const { issue } = event.data;
-        void this.#addIssue(issue);
-    }
-    async #addIssue(issue) {
-        if (!this.#isTrustedTypeIssue(issue) && !this.#isLateImportIssue(issue) && !this.#isPropertyRuleIssue(issue)) {
-            return;
-        }
-        const issuesModel = issue.model();
-        if (!issuesModel) {
-            return;
-        }
-        const srcLocation = toZeroBasedLocation(issue.details().sourceCodeLocation);
-        const description = issue.getDescription();
-        if (!description || !srcLocation) {
-            return;
-        }
-        const messageText = await getIssueTitleFromMarkdownDescription(description);
-        if (!messageText) {
-            return;
-        }
-        const clickHandler = () => {
-            void Common.Revealer.reveal(issue);
-        };
-        this.#sourceFrameMessageManager.addMessage(new IssueMessage(messageText, issue.getKind(), clickHandler), {
-            line: srcLocation.lineNumber,
-            column: srcLocation.columnNumber ?? -1,
-            url: srcLocation.url,
-            scriptId: srcLocation.scriptId,
-        }, issuesModel.target());
-    }
-    #onFullUpdateRequired() {
-        this.#resetMessages();
-        const issues = this.issuesManager.issues();
-        for (const issue of issues) {
-            void this.#addIssue(issue);
-        }
-    }
-    #isTrustedTypeIssue(issue) {
-        return issue instanceof ContentSecurityPolicyIssue && issue.code() === trustedTypesSinkViolationCode ||
-            issue.code() === trustedTypesPolicyViolationCode;
-    }
-    #isPropertyRuleIssue(issue) {
-        return issue instanceof PropertyRuleIssue;
-    }
-    #isLateImportIssue(issue) {
-        return issue.code() === lateImportStylesheetLoadingCode;
-    }
-    #resetMessages() {
-        this.#sourceFrameMessageManager.clear();
-    }
-}
-export class IssueMessage extends Workspace.UISourceCode.Message {
-    #kind;
-    constructor(title, kind, clickHandler) {
-        super("Issue" /* Workspace.UISourceCode.Message.Level.ISSUE */, title, clickHandler);
-        this.#kind = kind;
-    }
-    getIssueKind() {
-        return this.#kind;
-    }
-}

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/StylesheetLoadingIssue.js

@@ -1,59 +0,0 @@
-// Copyright 2023 The Chromium Authors
-// Use of this source code is governed by a BSD-style license that can be
-// found in the LICENSE file.
-import { Issue } from './Issue.js';
-export const lateImportStylesheetLoadingCode = [
-    "StylesheetLoadingIssue" /* Protocol.Audits.InspectorIssueCode.StylesheetLoadingIssue */,
-    "LateImportRule" /* Protocol.Audits.StyleSheetLoadingIssueReason.LateImportRule */,
-].join('::');
-export class StylesheetLoadingIssue extends Issue {
-    constructor(issueDetails, issuesModel) {
-        const code = `${"StylesheetLoadingIssue" /* Protocol.Audits.InspectorIssueCode.StylesheetLoadingIssue */}::${issueDetails.styleSheetLoadingIssueReason}`;
-        super(code, issueDetails, issuesModel);
-    }
-    sources() {
-        return [this.details().sourceCodeLocation];
-    }
-    requests() {
-        const details = this.details();
-        if (!details.failedRequestInfo) {
-            return [];
-        }
-        const { url, requestId } = details.failedRequestInfo;
-        if (!requestId) {
-            return [];
-        }
-        return [{ url, requestId }];
-    }
-    primaryKey() {
-        return JSON.stringify(this.details());
-    }
-    getDescription() {
-        switch (this.details().styleSheetLoadingIssueReason) {
-            case "LateImportRule" /* Protocol.Audits.StyleSheetLoadingIssueReason.LateImportRule */:
-                return {
-                    file: 'stylesheetLateImport.md',
-                    links: [],
-                };
-            case "RequestFailed" /* Protocol.Audits.StyleSheetLoadingIssueReason.RequestFailed */:
-                return {
-                    file: 'stylesheetRequestFailed.md',
-                    links: [],
-                };
-        }
-    }
-    getCategory() {
-        return "Other" /* IssueCategory.OTHER */;
-    }
-    getKind() {
-        return "PageError" /* IssueKind.PAGE_ERROR */;
-    }
-    static fromInspectorIssue(issueModel, inspectorIssue) {
-        const stylesheetLoadingDetails = inspectorIssue.details.stylesheetLoadingIssueDetails;
-        if (!stylesheetLoadingDetails) {
-            console.warn('Stylesheet loading issue without details received');
-            return [];
-        }
-        return [new StylesheetLoadingIssue(stylesheetLoadingDetails, issueModel)];
-    }
-}

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/UnencodedDigestIssue.js

@@ -1,62 +0,0 @@
-// Copyright 2025 The Chromium Authors
-// Use of this source code is governed by a BSD-style license that can be
-// found in the LICENSE file.
-import * as i18n from '../../core/i18n/i18n.js';
-import { Issue } from './Issue.js';
-import { resolveLazyDescription, } from './MarkdownIssueDescription.js';
-const UIStrings = {
-    /**
-     *@description Title for HTTP Unencoded Digest specification url
-     */
-    unencodedDigestHeader: 'HTTP Unencoded Digest specification',
-    /**
-     *@description Title for the URL of the integration of unencoded-digest and SRI.
-     */
-    integrityIntegration: 'Server-Initiated Integrity Checks',
-};
-const str_ = i18n.i18n.registerUIStrings('models/issues_manager/UnencodedDigestIssue.ts', UIStrings);
-const i18nLazyString = i18n.i18n.getLazilyComputedLocalizedString.bind(undefined, str_);
-export class UnencodedDigestIssue extends Issue {
-    constructor(issueDetails, issuesModel) {
-        super({
-            code: `${"UnencodedDigestIssue" /* Protocol.Audits.InspectorIssueCode.UnencodedDigestIssue */}::${issueDetails.error}`,
-            umaCode: `${"UnencodedDigestIssue" /* Protocol.Audits.InspectorIssueCode.UnencodedDigestIssue */}::${issueDetails.error}`,
-        }, issueDetails, issuesModel);
-    }
-    primaryKey() {
-        return JSON.stringify(this.details());
-    }
-    getDescription() {
-        const description = {
-            file: `unencodedDigest${this.details().error}.md`,
-            links: [
-                {
-                    link: 'https://www.ietf.org/archive/id/draft-ietf-httpbis-unencoded-digest-01.html',
-                    linkTitle: i18nLazyString(UIStrings.unencodedDigestHeader),
-                },
-                {
-                    link: 'https://wicg.github.io/signature-based-sri/#unencoded-digest-validation',
-                    linkTitle: i18nLazyString(UIStrings.integrityIntegration),
-                },
-            ],
-        };
-        return resolveLazyDescription(description);
-    }
-    getCategory() {
-        return "Other" /* IssueCategory.OTHER */;
-    }
-    getKind() {
-        return "PageError" /* IssueKind.PAGE_ERROR */;
-    }
-    requests() {
-        return this.details().request ? [this.details().request] : [];
-    }
-    static fromInspectorIssue(issuesModel, inspectorIssue) {
-        const details = inspectorIssue.details.unencodedDigestIssueDetails;
-        if (!details) {
-            console.warn('Unencoded-Digest issue without details received.');
-            return [];
-        }
-        return [new UnencodedDigestIssue(details, issuesModel)];
-    }
-}

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/CoepCoopSandboxedIframeCannotNavigateToCoopPage.md

@@ -1,4 +0,0 @@
-# An iframe navigation to a document with a Cross-Origin Opener Policy was blocked
-
-A document with a Cross-Origin Opener Policy (COOP) was blocked from loading in an iframe, because the iframe specifies a sandbox attribute.
-This protects COOP-enabled documents from inheriting properties from its opener.

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/CoepCorpNotSameOrigin.md

@@ -1,8 +0,0 @@
-# Specify a more permissive Cross-Origin Resource Policy to prevent a resource from being blocked
-
-Your site tries to access an external resource that only allows same-origin usage.
-This behavior prevents a document from loading any non-same-origin resources which don’t explicitly grant permission to be loaded.
-
-To solve this, add the following to the resource’s HTML response header:
-* `Cross-Origin-Resource-Policy: same-site` if the resource and your site are served from the same site.
-* `Cross-Origin-Resource-Policy: cross-origin` if the resource is served from another location than your website. ⚠️If you set this header, any website can embed this resource.

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/CoepCorpNotSameOriginAfterDefaultedToSameOriginByCoep.md

@@ -1,18 +0,0 @@
-# Specify a Cross-Origin Resource Policy to prevent a resource from being blocked
-
-Because your site has the Cross-Origin Embedder Policy (COEP) enabled, each
-resource must specify a suitable Cross-Origin Resource Policy (CORP). This
-behavior prevents a document from loading cross-origin resources which don’t
-explicitly grant permission to be loaded.
-
-To solve this, add the following to the resource’ response header:
-* `Cross-Origin-Resource-Policy: same-site` if the resource and your site are
-  served from the same site.
-* `Cross-Origin-Resource-Policy: cross-origin` if the resource is served from
-  another location than your website. ⚠️If you set this header, any website can
-  embed this resource.
-
-Alternatively, the document can use the variant: `Cross-Origin-Embedder-Policy:
-credentialless` instead of `require-corp`. It allows loading the resource,
-despite the missing CORP header, at the cost of requesting it without
-credentials like Cookies.

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/CoepCorpNotSameSite.md

@@ -1,7 +0,0 @@
-# Specify a more permissive Cross-Origin Resource Policy to prevent a resource from being blocked
-
-Your site tries to access an external resource that only allows same-site usage.
-This behavior prevents a document from loading any non-same-site resources which don’t explicitly grant permission to be loaded.
-
-To solve this, add the following to the resource’s HTML response header: `Cross-Origin-Resource-Policy: cross-origin`
-⚠️If you set this header, any website can embed this resource.

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/CoepFrameResourceNeedsCoepHeader.md

@@ -1,10 +0,0 @@
-# Specify a Cross-Origin Embedder Policy to prevent this frame from being blocked
-
-Because your site has the Cross-Origin Embedder Policy (COEP) enabled, each
-embedded iframe must also specify this policy. This behavior protects private
-data from being exposed to untrusted third party sites.
-
-To solve this, add one of following to the embedded frame’s HTML response
-header:
-* `Cross-Origin-Embedder-Policy: require-corp`
-* `Cross-Origin-Embedder-Policy: credentialless` (Chrome > 96)

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/CompatibilityModeQuirks.md

@@ -1,5 +0,0 @@
-# Page layout may be unexpected due to Quirks Mode
-
-One or more documents in this page is in Quirks Mode, which will render the affected document(s) with quirks incompatible with the current HTML and CSS specifications.
-
-Quirks Mode exists mostly due to historical reasons. If this is not intentional, you can [add or modify the DOCTYPE to be `<!DOCTYPE html>`](issueQuirksModeDoctype) to render the page in No Quirks Mode.

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/CookieAttributeValueExceedsMaxSize.md

@@ -1,5 +0,0 @@
-# Ensure cookie attribute values don’t exceed 1024 characters
-
-Cookie attribute values exceeding 1024 characters in size will result in the attribute being ignored. This could lead to unexpected behavior since the cookie will be processed as if the offending attribute / attribute value pair were not present.
-
-Resolve this issue by ensuring that cookie attribute values don’t exceed 1024 characters.

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/LowTextContrast.md

@@ -1,5 +0,0 @@
-# Users may have difficulties reading text content due to insufficient color contrast
-
-Low-contrast text is difficult or impossible for users to read. A [minimum contrast ratio (AA) of 4.5](issuesContrastWCAG21AA) is recommended for all text. Since font size and weight affect color perception, an exception is made for very large or bold text — in this case, a contrast ratio of 3.0 is allowed. The [enhanced conformance level (AAA)](issuesContrastWCAG21AAA) requires the contrast ratio to be above 7.0 for regular text and 4.5 for large text.
-
-Update colors or change the font size or weight to achieve sufficient contrast. You can use the [“Suggest color” feature](issuesContrastSuggestColor) in the DevTools color picker to automatically select a better text color.

package/build/node_modules/chrome-devtools-frontend/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/build/node_modules/chrome-devtools-frontend/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/build/node_modules/chrome-devtools-frontend/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/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/SameSiteInvalidSameParty.md

@@ -1,8 +0,0 @@
-# Mark SameParty cookies as Secure and do not use SameSite=Strict for SameParty cookies
-
-Cookies marked with `SameParty` must also be marked with `Secure`. In addition, cookies marked
-with `SameParty` cannot use `SameSite=Strict`.
-
-Resolve this issue by updating the attributes of the cookie:
-  * Remove `SameParty` if the cookie should only be used by the same site but not the same first-party set
-  * Remove `SameSite=Strict` and specify `Secure` if the cookie should be available to all sites of the same first-party set

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/SameSiteNoneInsecureErrorRead.md

@@ -1,8 +0,0 @@
-# Mark cross-site cookies as Secure to allow them to be sent in cross-site requests
-
-Cookies marked with `SameSite=None` must also be marked with `Secure` to get sent in cross-site requests.
-This behavior protects user data from being sent over an insecure connection.
-
-Resolve this issue by updating the attributes of the cookie:
-* Specify `SameSite=None` and `Secure` if the cookie should be sent in cross-site requests. This enables third-party use.
-* Specify `SameSite=Strict` or `SameSite=Lax` if the cookie should not be sent in cross-site requests.

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/SameSiteNoneInsecureErrorSet.md

@@ -1,8 +0,0 @@
-# Mark cross-site cookies as Secure to allow setting them in cross-site contexts
-
-Cookies marked with `SameSite=None` must also be marked with `Secure` to allow setting them in a cross-site context.
-This behavior protects user data from being sent over an insecure connection.
-
-Resolve this issue by updating the attributes of the cookie:
-* Specify `SameSite=None` and `Secure` if the cookie is intended to be set in cross-site contexts. Note that only cookies sent over HTTPS may use the `Secure` attribute.
-* Specify `SameSite=Strict` or `SameSite=Lax` if the cookie should not be set by cross-site requests.

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/SameSiteNoneInsecureWarnRead.md

@@ -1,8 +0,0 @@
-# Mark cross-site cookies as Secure to allow them to be sent in cross-site requests
-
-In a future version of the browser, cookies marked with `SameSite=None` must also be marked with `Secure` to get sent in cross-site requests.
-This behavior protects user data from being sent over an insecure connection.
-
-Resolve this issue by updating the attributes of the cookie:
-* Specify `SameSite=None` and `Secure` if the cookie should be sent in cross-site requests. This enables third-party use.
-* Specify `SameSite=Strict` or `SameSite=Lax` if the cookie should not be sent in cross-site requests.

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/SameSiteNoneInsecureWarnSet.md

@@ -1,8 +0,0 @@
-# Mark cross-site cookies as Secure to allow setting them in cross-site contexts
-
-In a future version of the browser, cookies marked with `SameSite=None` must also be marked with `Secure` to allow setting them in a cross-site context.
-This behavior protects user data from being sent over an insecure connection.
-
-Resolve this issue by updating the attributes of the cookie:
-* Specify `SameSite=None` and `Secure` if the cookie is intended to be set in cross-site contexts. Note that only cookies sent over HTTPS may use the `Secure` attribute.
-* Specify `SameSite=Strict` or `SameSite=Lax` if the cookie should not be set by cross-site requests.

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/SameSiteSamePartyCrossPartyContextSet.md

@@ -1,10 +0,0 @@
-# Make sure a cookie is using the SameParty attribute correctly
-
-Setting cross-site cookies with the `SameParty` attribute is only possible if
-both domains are a part of the same First-Party Set.
-
-To allow setting cross-site cookies, try one of the following:
-* If the domains satisfy the First-Party Set criteria, add them to the same First-Party Set.
-* If the domains don't satisfy the First-Party Set criteria, remove the `SameParty` attribute and specify `SameSite=None`.
-
-If you don't have the option to do any of the above, cookies are not intended to be set in cross-site contexts.

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/SameSiteUnspecifiedLaxAllowUnsafeRead.md

@@ -1,9 +0,0 @@
-# Indicate whether to send a cookie in a cross-site request by specifying its SameSite attribute
-
-Because a cookie’s `SameSite` attribute was not set or is invalid, it defaults to `SameSite=Lax`,
-which will prevent the cookie from being sent in a cross-site request in a future version of the browser.
-This behavior protects user data from accidentally leaking to third parties and cross-site request forgery.
-
-Resolve this issue by updating the attributes of the cookie:
-* Specify `SameSite=None` and `Secure` if the cookie should be sent in cross-site requests. This enables third-party use.
-* Specify `SameSite=Strict` or `SameSite=Lax` if the cookie should not be sent in cross-site requests.

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/SameSiteUnspecifiedLaxAllowUnsafeSet.md

@@ -1,9 +0,0 @@
-# Indicate whether a cookie is intended to be set in cross-site context by specifying its SameSite attribute
-
-Because a cookie’s `SameSite` attribute was not set or is invalid, it defaults to `SameSite=Lax`,
-which will prevents the cookie from being set in a cross-site context in a future version of the browser.
-This behavior protects user data from accidentally leaking to third parties and cross-site request forgery.
-
-Resolve this issue by updating the attributes of the cookie:
-* Specify `SameSite=None` and `Secure` if the cookie is intended to be set in cross-site contexts. Note that only cookies sent over HTTPS may use the `Secure` attribute.
-* Specify `SameSite=Strict` or `SameSite=Lax` if the cookie should not be set by cross-site requests.

package/build/node_modules/chrome-devtools-frontend/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/build/node_modules/chrome-devtools-frontend/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/build/node_modules/chrome-devtools-frontend/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.

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/arInsecureContext.md

@@ -1,7 +0,0 @@
-# Ensure that the attribution registration context is secure
-
-This page tried to register a source or trigger using the Attribution Reporting
-API but failed because the page that initiated the registration was not secure.
-
-The registration context must use HTTPS unless it is `localhost` or
-`127.0.0.1`.

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/arInvalidInfoHeader.md

@@ -1,5 +0,0 @@
-# Ensure that the `Attribution-Reporting-Info` header is valid
-
-This page tried to register a source or trigger using the Attribution Reporting
-API but failed because an `Attribution-Reporting-Info` response header was
-invalid.

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/arInvalidRegisterOsSourceHeader.md

@@ -1,5 +0,0 @@
-# Ensure that the `Attribution-Reporting-Register-OS-Source` header is valid
-
-This page tried to register an OS source using the Attribution Reporting API
-but failed because an `Attribution-Reporting-Register-OS-Source` response
-header was invalid.

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/arInvalidRegisterOsTriggerHeader.md

@@ -1,5 +0,0 @@
-# Ensure that the `Attribution-Reporting-Register-OS-Trigger` header is valid
-
-This page tried to register an OS trigger using the Attribution Reporting API
-but failed because an `Attribution-Reporting-Register-OS-Trigger` response
-header was invalid.

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/arInvalidRegisterSourceHeader.md

@@ -1,5 +0,0 @@
-# Ensure that the `Attribution-Reporting-Register-Source` header is valid
-
-This page tried to register a source using the Attribution Reporting API but
-failed because an `Attribution-Reporting-Register-Source` response header was
-invalid.

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/arInvalidRegisterTriggerHeader.md

@@ -1,5 +0,0 @@
-# Ensure that the `Attribution-Reporting-Register-Trigger` header is valid
-
-This page tried to register a trigger using the Attribution Reporting API but
-failed because an `Attribution-Reporting-Register-Trigger` response header was
-invalid.

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/arNavigationRegistrationUniqueScopeAlreadySet.md

@@ -1,5 +0,0 @@
-# Ensure that multiple sources associated with the same navigation have the same attribution scopes
-
-The page tried to register a source using Attribution Reporting API, but the
-source was rejected because a previous source associated with the same
-navigation and reporting origin used a different set of attribution scopes.

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/arNavigationRegistrationWithoutTransientUserActivation.md

@@ -1,6 +0,0 @@
-# Ensure that navigation-source registrations are initiated by a user gesture
-
-This page tried to register a navigation source using the Attribution Reporting
-API but failed because the navigation was not initiated by a user gesture.
-Compared to event sources, navigation sources can release more cross-site
-information, and are therefore subject to this additional privacy control.

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/arNoRegisterOsSourceHeader.md

@@ -1,5 +0,0 @@
-# OS attribution source expected but corresponding header not found
-
-The page indicated, via the `Attribution-Reporting-Info` header, that it
-intended to register an OS source using the Attribution Reporting API, but the
-corresponding `Attribution-Reporting-Register-OS-Source` header was missing.

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/arNoRegisterOsTriggerHeader.md

@@ -1,5 +0,0 @@
-# OS attribution trigger expected but corresponding header not found
-
-The page indicated, via the `Attribution-Reporting-Info` header, that it
-intended to register an OS trigger using the Attribution Reporting API, but the
-corresponding `Attribution-Reporting-Register-OS-Trigger` header was missing.

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/arNoRegisterSourceHeader.md

@@ -1,5 +0,0 @@
-# Web attribution source expected but corresponding header not found
-
-The page indicated, via the `Attribution-Reporting-Info` header, that it
-intended to register a web source using the Attribution Reporting API, but the
-corresponding `Attribution-Reporting-Register-Source` header was missing.

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/arNoRegisterTriggerHeader.md

@@ -1,5 +0,0 @@
-# Web attribution trigger expected but corresponding header not found
-
-The page indicated, via the `Attribution-Reporting-Info` header, that it
-intended to register a web trigger using the Attribution Reporting API, but the
-corresponding `Attribution-Reporting-Register-Trigger` header was missing.

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/arNoWebOrOsSupport.md

@@ -1,4 +0,0 @@
-# No web or OS support for Attribution Reporting
-
-The page tried to send an attributionsrc request, but there was neither web nor
-OS support for the Attribution Reporting API, so the request was skipped.

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/arOsSourceIgnored.md

@@ -1,18 +0,0 @@
-# An attribution OS source registration was ignored because the request was ineligible
-
-This page tried to register an OS source using the Attribution Reporting API,
-but the request was ineligible to do so, so the OS source registration was
-ignored.
-
-A request is eligible for OS source registration if it has all of the following:
-
-- An `Attribution-Reporting-Eligible` header whose value is a structured
-  dictionary that contains the key `navigation-source` or `event-source`
-- An `Attribution-Reporting-Support` header whose value is a structured
-  dictionary that contains the key `os`
-
-Otherwise, any `Attribution-Reporting-Register-OS-Source` response header will
-be ignored.
-
-Additionally, a single HTTP redirect chain may register only all sources or all
-triggers, not a combination of both.

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/arOsTriggerIgnored.md

@@ -1,19 +0,0 @@
-# An attribution OS trigger registration was ignored because the request was ineligible
-
-This page tried to register an OS trigger using the Attribution Reporting API,
-but the request was ineligible to do so, so the OS trigger registration was
-ignored.
-
-A request is eligible for OS trigger registration if it has all of the following:
-
-- No `Attribution-Reporting-Eligible` header or an
-  `Attribution-Reporting-Eligible` header whose value is a structured
-  dictionary that contains the key `trigger`
-- An `Attribution-Reporting-Support` header whose value is a structured
-  dictionary that contains the key `os`
-
-Otherwise, any `Attribution-Reporting-Register-OS-Trigger` response header will
-be ignored.
-
-Additionally, a single HTTP redirect chain may register only all sources or all
-triggers, not a combination of both.

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/arPermissionPolicyDisabled.md

@@ -1,8 +0,0 @@
-# The Attribution Reporting API can’t be used because Permissions Policy has been disabled
-
-This page tried to use the Attribution Reporting API but failed because the
-`attribution-reporting` Permission Policy was explicitly disabled.
-
-This API is currently enabled by default for top-level and cross-origin frames,
-but it is still possible for frames to have the permission disabled by their
-parent, e.g. with `<iframe src="…" allow="attribution-reporting 'none'">`.

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/arSourceAndTriggerHeaders.md

@@ -1,9 +0,0 @@
-# Ensure that attribution responses contain either source or trigger, not both
-
-This page tried to register a source and a trigger in the same HTTP response
-using the Attribution Reporting API, which is prohibited.
-
-The corresponding request was eligible to register either a source or a
-trigger, but the response may only set either the
-`Attribution-Reporting-Register-Source` header or the
-`Attribution-Reporting-Register-Trigger` header, not both.

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/arSourceIgnored.md

@@ -1,13 +0,0 @@
-# An attribution source registration was ignored because the request was ineligible
-
-This page tried to register a source using the Attribution Reporting API, but
-the request was ineligible to do so, so the source registration was ignored.
-
-A request is eligible for source registration if it has an
-`Attribution-Reporting-Eligible` header whose value is a structured dictionary
-that contains the key `navigation-source` or `event-source`. If the header is
-absent or does not contain one of those keys, any
-`Attribution-Reporting-Register-Source` response header will be ignored.
-
-Additionally, a single HTTP redirect chain may register only all sources or all
-triggers, not a combination of both.

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/arTriggerIgnored.md

@@ -1,12 +0,0 @@
-# An attribution trigger registration was ignored because the request was ineligible
-
-This page tried to register a trigger using the Attribution Reporting API, but
-the request was ineligible to do so, so the trigger registration was ignored.
-
-A request is eligible for trigger registration if it has an
-`Attribution-Reporting-Eligible` header whose value is a structured dictionary
-that contains the key `trigger`, or if the header is absent. Otherwise, any
-`Attribution-Reporting-Register-Trigger` response header will be ignored.
-
-Additionally, a single HTTP redirect chain may register only all sources or all
-triggers, not a combination of both.

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/arUntrustworthyReportingOrigin.md

@@ -1,10 +0,0 @@
-# Ensure that attribution reporting origins are trustworthy
-
-This page tried to register a source or trigger using the Attribution Reporting
-API but failed because the reporting origin was not potentially trustworthy.
-
-The reporting origin is typically the server that sets the
-`Attribution-Reporting-Register-Source` or
-`Attribution-Reporting-Register-Trigger` header.
-
-The reporting origin must use HTTPS unless it is `localhost` or `127.0.0.1`.