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

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

@@ -1,11 +0,0 @@
-# Ensure that attribution responses contain either web or OS headers, not both
-
-This page included web and OS Attribution Reporting API headers in the same
-HTTP response, which is prohibited.
-
-The response may set at most one of the following headers:
-
-- `Attribution-Reporting-Register-OS-Source`
-- `Attribution-Reporting-Register-OS-Trigger`
-- `Attribution-Reporting-Register-Source`
-- `Attribution-Reporting-Register-Trigger`

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

@@ -1,3 +0,0 @@
-# Chrome may soon delete state for intermediate websites in a recent navigation chain
-
-In a recent navigation chain, one or more websites without prior user interaction were visited. If these websites don't get such an interaction soon, Chrome will delete their state.

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

@@ -1,4 +0,0 @@
-# Client Hint meta tag contained invalid origin
-
-Items in the delegate-ch meta tag allow list must be valid origins.
-No special values (e.g. self, none, and *) are permitted.

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

@@ -1,4 +0,0 @@
-# Client Hint meta tag modified by javascript
-
-Only delegate-ch meta tags in the original HTML sent from the server
-are respected. Any injected via javascript (or other means) are ignored.

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

@@ -1,12 +0,0 @@
-# Cookie is blocked due to a cross-site redirect chain
-
-The cookie was blocked because the URL redirect chain was not fully same-site,
-meaning the final request was treated as a cross-site request.
-Like other cross-site requests, this blocks cookies with `SameSite=Lax` or
-`SameSite=Strict`.
-
-For example: If site A redirects to site B which then redirects back to site A,
-the final request to site A will be a cross-site request.
-
-If this behavior is causing breakage, please file a bug report with the link
-below.

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

@@ -1,4 +0,0 @@
-# Third-party cookie blocked within the same Related Website Set
-
-A cookie embedded by a site in the top-level page's Related Website Set was blocked
-by third-party cookie blocking.

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

@@ -1,11 +0,0 @@
-# Ensure cookie `Domain` attribute values only contain ASCII characters
-
-`Domain` attributes in cookies are restricted to the ASCII character set. Any
-cookies that contain characters outside of the ASCII range in their `Domain`
-attribute will be ignored.
-
-To resolve this issue, you need to remove all non-ASCII characters from the
-`Domain` attribute of the affected cookies.
-
-If your site has an internationalized domain name (IDN), you should use
-[punycode](punycodeReference) representation for the `Domain` attribute instead.

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

@@ -1,8 +0,0 @@
-# Cookie was not sent due to port mismatch
-
-Cookies can only be accessed by origins that share the same port as the origin
-that initially set the cookie.
-
-If this cookie is required for the request, the cookie will need to be set by an
-origin with the same port as the request. Alternatively, you can utilize the
-Domain attribute, which allows access to a cookie with a mismatched port.

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

@@ -1,7 +0,0 @@
-# Cookie was not sent due to scheme mismatch
-
-The cookie can only be accessed by origins that share the same scheme as
-the origin that initially set it.
-
-If this cookie is required for the request, the cookie will need to be set
-by an origin with the same scheme as the request.

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

@@ -1,6 +0,0 @@
-# Reading third-party cookie is blocked
-
-Cookies with the `SameSite=None; Secure` and not `Partitioned` attributes that operate in cross-site contexts are third-party cookies.
-Third-party cookies are restricted for this browser either because of Chrome flags or browser configuration.
-
-Learn more from the linked article about preparing your site to avoid potential breakage due to this.

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

@@ -1,6 +0,0 @@
-# Setting third-party cookie is blocked
-
-Cookies with the `SameSite=None; Secure` and not `Partitioned` attributes that operate in cross-site contexts are third-party cookies.
-Third-party cookies are restricted for this browser either because of Chrome flags or browser configuration.
-
-Learn more from the linked article about preparing your site to avoid potential breakage due to this.

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

@@ -1,11 +0,0 @@
-# Ensure cookie `Domain` attribute values only contain ASCII characters
-
-`Domain` attributes in cookies are restricted to the ASCII character set. Any
-cookies that contain characters outside of the ASCII range in their `Domain`
-attribute will be ignored in the future.
-
-To resolve this issue, you need to remove all non-ASCII characters from the
-`Domain` attribute of the affected cookies.
-
-If your site has an internationalized domain name (IDN), you should use
-[punycode](punycodeReference) representation for the `Domain` attribute instead.

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

@@ -1,4 +0,0 @@
-# Third-party websites are allowed to read cookies on this page
-
-One or more websites are allowed to bypass user settings to read third-party cookies on this page. Web developers should take steps to remove these reads without disrupting user experience. To forcefully block these third-party cookies, update [user settings](manageCookiesHelpPage).
-{PLACEHOLDER_topleveloptout}

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

@@ -1,4 +0,0 @@
-# Third-party websites are allowed to set cookies on this page
-
-One or more websites are allowed to bypass user settings to set third-party cookies on this page. Web developers should take steps to remove these sets without disrupting user experience. To forcefully block these third-party cookies, update [user settings](manageCookiesHelpPage).
-{PLACEHOLDER_topleveloptout}

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

@@ -1,6 +0,0 @@
-# Reading cookie in cross-site context may be impacted on Chrome
-
-Cookies with the `SameSite=None; Secure` and not `Partitioned` attributes that operate in cross-site contexts are third-party cookies.
-Chrome is moving towards a new experience that allows users to choose to browse without third-party cookies.
-
-Learn more from the linked article about preparing your site to avoid potential breakage.

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

@@ -1,6 +0,0 @@
-# Setting cookie in cross-site context may be impacted on Chrome
-
-Cookies with the `SameSite=None; Secure` and not `Partitioned` attributes that operate in cross-site contexts are third-party cookies.
-Chrome is moving towards a new experience that allows users to choose to browse without third-party cookies
-
-Learn more from the linked article about preparing your site to avoid potential breakage.

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

@@ -1,6 +0,0 @@
-# Ensure CORS requests include credentials only when allowed
-
-A cross-origin resource sharing (CORS) request was blocked because it was configured to include credentials but the `Access-Control-Allow-Credentials` response header of the request or the associated preflight request was not set to `true`.
-
-To fix this issue, ensure that resources that expect credentialed CORS requests set the `Access-Control-Allow-Credentials` header to `true`.
-Note that this requires the `Access-Control-Allow-Origin` header to not be a wildcard `*`.

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

@@ -1,7 +0,0 @@
-# Ensure CORS requests are made on supported schemes
-
-A cross-origin resource sharing (CORS) request was blocked because the scheme of the request's URL doesn't support CORS.
-
-To fix this issue, ensure all CORS request URLs specify a supported scheme, e.g. most commonly https://.
-
-Note that if an opaque response is sufficient, then for some schemes the request's mode can be set to `no-cors` to fetch the resource with CORS disabled; that way the scheme doesn't need to support CORS, but the response content is inaccessible (opaque).

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

@@ -1,7 +0,0 @@
-# Ensure only same-origin resources are fetched with same-origin request mode
-
-A cross-origin resource sharing (CORS) request to a cross-origin resource was blocked because the request mode was set to `same-origin`.
-
-To fix this issue, ensure that only same-origin resources are fetched with the `same-origin` request mode. If you need to fetch a cross-origin resource, use a request mode such as `cors`.
-
-Note that if an opaque response is sufficient, the request's mode can be set to `no-cors` to fetch the resource with CORS disabled; that way CORS headers are not required but the response content is inaccessible (opaque).

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

@@ -1,5 +0,0 @@
-# Ensure CORS request includes only allowed headers
-
-A cross-origin resource sharing (CORS) request was blocked because it contained request headers that were neither CORS-safelisted (`Accept`, `Accept-Language`, `Content-Language`, `Content-Type`) nor allowed by the `Access-Control-Allow-Headers` response header of the associated preflight request.
-
-To fix this issue, include the additional request headers you want to use in the `Access-Control-Allow-Headers` response header of the associated preflight request.

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

@@ -1,10 +0,0 @@
-# Ensure private network requests are made from secure contexts
-
-A site requested a resource from a network that it could only access because of its users' privileged network position.
-These requests expose devices and servers to the internet, increasing the risk of a cross-site request forgery (CSRF) attack, and/or information leakage.
-
-To mitigate these risks, Chrome deprecates requests to non-public subresources when initiated from non-secure contexts. See the [feature status](PNASecureContextRestrictionFeatureStatus).
-
-To fix this issue, migrate the website that needs to access local resources to HTTPS. If the target resource is not served on localhost, it must also be served on HTTPS to avoid mixed-content issues.
-
-Administrators can make use of the `InsecurePrivateNetworkRequestsAllowed` and `InsecurePrivateNetworkRequestsAllowedForUrls` enterprise policies to temporarily disable this restriction on all or certain websites.

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

@@ -1,7 +0,0 @@
-# Ensure CORS response header values are valid
-
-A cross-origin resource sharing (CORS) request was blocked because of invalid or missing response headers of the request or the associated [preflight request](issueCorsPreflightRequest).
-
-To fix this issue, ensure the response to the CORS request and/or the associated [preflight request](issueCorsPreflightRequest) are not missing headers and use valid header values.
-
-Note that if an opaque response is sufficient, the request's mode can be set to `no-cors` to fetch the resource with CORS disabled; that way CORS headers are not required but the response content is inaccessible (opaque).

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

@@ -1,19 +0,0 @@
-# Ensure that local network requests are compatible with upcoming restrictions
-
-A site requested a resource from a network that it could only access because of
-its users' privileged network position.
-
-These requests expose devices and servers to the internet, increasing the risk
-of a cross-site request forgery (CSRF) attack and/or information leakage.
-
-To mitigate these risks, Chrome will begin requiring the user grant explicit
-permission before a site can make local network requests. Local network requests
-are those that go to either private IP addresses, .local domains, or loopback
-addresses. Additionally, Chrome will block local network requests (both
-subframes and subresources) when initiated from non-secure contexts.
-
-If the user explicitly grants the permission, the site can make local network
-requests over HTTP for hostnames that are private IP addresses, .local
-hostnames, or to localhost. Sites can also set the `targetAddressSpace` fetch
-option to `private` or `local` to mark requests as being local network requests,
-which will allow them to be made over HTTP.

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

@@ -1,5 +0,0 @@
-# Ensure CORS request uses allowed method
-
-A cross-origin resource sharing (CORS) request was blocked because it neither uses one of the CORS-safelisted methods (`GET`, `HEAD`, `POST`) nor was the request method explicitly allowed by the `Access-Control-Allow-Methods` response header of the associated [preflight request](issueCorsPreflightRequest).
-
-To fix this issue, include the request method in the `Access-Control-Allow-Methods` header of the associated preflight request.

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

@@ -1,5 +0,0 @@
-# Ensure no-cors requests configure redirect mode follow
-
-A cross-origin resource sharing (CORS) request was blocked because it was configured to use request mode `no-cors` but did not use the redirect mode `follow`.
-
-To fix this issue, ensure that whenever the request mode `no-cors` is set then the redirect mode is set to `follow`.

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

@@ -1,6 +0,0 @@
-# Ensure CORS requesting origin matches resource's allowed origin
-
-A cross-origin resource sharing (CORS) request was blocked because the `Access-Control-Allow-Origin` response header of the request or the associated [preflight request](issueCorsPreflightRequest) specified an origin different from the origin of the context that initiated the request.
-
-To fix this issue, ensure that the `Access-Control-Allow-Origin` header for the resource matches the request context's origin.
-If the resource never needs to be accessed with credentials, the `Access-Control-Allow-Origin` header may be set to a wildcard `*` to allow access from everywhere.

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

@@ -1,10 +0,0 @@
-# Ensure private network requests are only made to resources that allow them
-
-A site requested a resource from a network that it could only access because of its users' privileged network position.
-These requests expose devices and servers to the internet, increasing the risk of a cross-site request forgery (CSRF) attack, and/or information leakage.
-
-To mitigate these risks, Chrome will require non-public subresources to opt-into being accessed with a preflight request and will start blocking them in Chrome 130 (October 2024).
-
-To fix this issue, ensure that response to the [preflight request](issueCorsPreflightRequest) for the private network resource has the `Access-Control-Allow-Private-Network` header set to `true`.
-
-Administrators can make use of the `InsecurePrivateNetworkRequestsAllowed` and `InsecurePrivateNetworkRequestsAllowedForUrls` enterprise policies to temporarily disable this restriction on all or certain websites.

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

@@ -1,5 +0,0 @@
-# Ensure preflight responses are valid
-
-A cross-origin resource sharing (CORS) request was blocked because the response to the associated [preflight request](issueCorsPreflightRequest) failed, had an unsuccessful HTTP status code, and/or was a redirect.
-
-To fix this issue, ensure all CORS preflight `OPTIONS` requests are answered with a successful HTTP status code (2xx) and do not redirect.

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

@@ -1,10 +0,0 @@
-# Ensure that private network requests made from secure context to plaintext resources can gain access based on user permission
-
-A site requested a resource from a network that it could only access because of its users' privileged network position.
-These requests expose devices and servers to the internet, increasing the risk of a cross-site request forgery (CSRF) attack and/or information leakage.
-
-To mitigate these risks, Chrome deprecates requests to non-public subresources when initiated from non-secure contexts. See the [feature status](PNASecureContextRestrictionFeatureStatus).
-
-Setting a `targetAddressSpace` fetch option to `private` or `local` allows secure contexts to fetch private network resources over HTTP, which is normally forbidden by mixed-content checks. The target server must respond affirmatively to a preflight request, and the user must grant explicit permission.
-
-Make sure that the response to the [preflight request](issueCorsPreflightRequest) for the private network resource has the `Private-Network-Access-Id` and `Private-Network-Access-Name` header properly set. `Private-Network-Access-Id` should be the device's MAC address and `Private-Network-Access-Name` should be a human-friendly device name.

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

@@ -1,5 +0,0 @@
-# Ensure CORS requests are not redirected to URLs containing credentials
-
-A cross-origin resource sharing (CORS) request was blocked because the response was a redirect to a URL that includes credentials, i.e. redirected to a URL of the form `https://username:password@example.com`.
-
-To fix this issue, ensure CORS requests are not redirected to URLs that include credentials.

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

@@ -1,8 +0,0 @@
-# Ensure credentialed requests are not sent to CORS resources with origin wildcards
-
-A cross-origin resource sharing (CORS) request was blocked because it was configured to `include` credentials and the `Access-Control-Allow-Origin` response header of the request or the associated [preflight request](issueCorsPreflightRequest) was set to a wildcard `*`. CORS requests may only include credentials for resources where the `Access-Control-Allow-Origin` header is not a wildcard.
-
-To fix this issue, ensure that either the request is configured to not include credentials, or change the `Access-Control-Allow-Origin` header of the resource to not be a wildcard.
-
-Note that if an opaque response is sufficient, the request's mode can be set to `no-cors` to fetch the resource with CORS disabled; that way CORS headers are not required but credentials are not sent and the response content is inaccessible (opaque).
-

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

@@ -1,9 +0,0 @@
-# Content Security Policy of your site blocks the use of 'eval' in JavaScript`
-
-The Content Security Policy (CSP) prevents the evaluation of arbitrary strings as JavaScript to make it more difficult for an attacker to inject unathorized code on your site.
-
-To solve this issue, avoid using `eval()`, `new Function()`, `setTimeout([string], ...)` and `setInterval([string], ...)` for evaluating strings.
-
-If you absolutely must: you can enable string evaluation by adding `unsafe-eval` as an allowed source in a `script-src` directive.
-
-⚠️ Allowing string evaluation comes at the risk of inline script injection.

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

@@ -1,10 +0,0 @@
-# Content Security Policy blocks inline execution of scripts and stylesheets
-
-The Content Security Policy (CSP) prevents cross-site scripting attacks by blocking inline execution of scripts and style sheets.
-
-To solve this, move all inline scripts (e.g. `onclick=[JS code]`) and styles into external files.
-
-⚠️ Allowing inline execution comes at the risk of script injection via injection of HTML script elements. If you absolutely must, you can allow inline script and styles by:
-
-* adding `unsafe-inline` as a source to the CSP header
-* adding the hash or nonce of the inline script to your CSP header.

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

@@ -1,5 +0,0 @@
-# Trusted Type policy creation blocked by Content Security Policy
-
-Your site tries to create a Trusted Type policy that has not been allowed by the Content Security Policy. The Content Security Policy may restrict the set of valid names for Trusted Type policies, and forbid more than one policy of each name.
-
-To solve this, make sure that the names of the policies listed below are declared in the `trusted-types` CSP directive. To allow redefining policies add the `allow-duplicates` keyword. If you want to remove all restrictions on policy names, remove the `trusted-types` directive entirely (not recommended).

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

@@ -1,8 +0,0 @@
-# Trusted Type expected, but String received
-
-Your site tries to use a plain string in a DOM modification where a Trusted Type is expected. Requiring Trusted Types for DOM modifications helps to prevent cross-site scripting attacks.
-
-To solve this, provide a Trusted Type to all the DOM modifications listed below. You can convert a string into a Trusted Type by:
-
-* defining a policy and using its corresponding `createHTML`, `createScript` or `createScriptURL` function.
-* defining a policy named `default` which will be automatically called.

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

@@ -1,10 +0,0 @@
-# Content Security Policy of your site blocks some resources
-
-Some resources are blocked because their origin is not listed in your site's Content Security Policy (CSP). Your site's CSP is allowlist-based, so resources must be listed in the allowlist in order to be accessed.
-
-A site's Content Security Policy is set either via an HTTP header (recommended), or via a meta HTML tag.
-
-To fix this issue do one of the following:
-
-* (Recommended) If you're using an allowlist for `'script-src'`, consider switching from an allowlist CSP to a strict CSP, because strict CSPs are [more robust against XSS](issuesCSPWhyStrictOverAllowlist). [See how to set a strict CSP](issuesCSPSetStrict).
-* Or carefully check that all of the blocked resources are trustworthy; if they are, include their sources in the CSP of your site. ⚠️Never add a source you don't trust to your site's CSP. If you don't trust the source, consider hosting resources on your own site instead.

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

@@ -1,3 +0,0 @@
-# {PLACEHOLDER_title}
-
-{PLACEHOLDER_message}

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

@@ -1 +0,0 @@
-# The provider's accounts list endpoint cannot be found.

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

@@ -1 +0,0 @@
-# Provider's accounts list is invalid.

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

@@ -1 +0,0 @@
-# The response body is empty when fetching the provider's accounts list.

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

@@ -1 +0,0 @@
-# User declined the sign-in attempt.

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

@@ -1 +0,0 @@
-# The request has been aborted.

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

@@ -1 +0,0 @@
-# The provider's client metadata endpoint cannot be found.

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

@@ -1 +0,0 @@
-# Provider's client metadata is invalid.

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

@@ -1 +0,0 @@
-# The response body is empty when fetching the provider's client metadata.

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

@@ -1 +0,0 @@
-# Error attempting to reach the provider's sign-in endpoint.

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

@@ -1 +0,0 @@
-# Error retrieving a token.

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

@@ -1 +0,0 @@
-# The provider's id token endpoint cannot be found.

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

@@ -1 +0,0 @@
-# The token fetching request is invalid.

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

@@ -1 +0,0 @@
-# Provider's token is invalid.

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

@@ -1 +0,0 @@
-# The response body is empty when fetching the provider's token.

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

@@ -1 +0,0 @@
-# Provider's sign-in response is invalid.

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

@@ -1 +0,0 @@
-# The provider's FedCM manifest configuration cannot be found.

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

@@ -1 +0,0 @@
-# Provider's FedCM manifest configuration is invalid.

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

@@ -1 +0,0 @@
-# The response body is empty when fetching the provider's FedCM manifest configuration.

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

@@ -1 +0,0 @@
-# Only one navigator.credentials.get request may be outstanding at one time.

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

@@ -1 +0,0 @@
-# getUserInfo() failed because of an invalid accounts response.

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

@@ -1 +0,0 @@
-# getUserInfo() failed because the config and well-known files were invalid.

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

@@ -1 +0,0 @@
-# getUserInfo() failed because the user has not yet used FedCM on this site with the provided IDP.

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

@@ -1 +0,0 @@
-# getUserInfo() is disabled because FedCM is disabled.

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

@@ -1 +0,0 @@
-# getUserInfo() failed because no account received was a returning account.

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

@@ -1 +0,0 @@
-# getUserInfo() caller is not an iframe.

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

@@ -1 +0,0 @@
-# getUserInfo() failed because the config URL is not potentially trustworthy.

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

@@ -1 +0,0 @@
-# getUserInfo() caller is not same origin as the config URL.

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

@@ -1 +0,0 @@
-# getUserInfo() is disabled because the IDP Sign-In Status is signed-out.

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

@@ -1,7 +0,0 @@
-# Fetching Partitioned Blob URL Issue
-
-This issue occurs when a Blob URL access attempt was blocked because it was made from a cross-partition, same-origin context.
-
-Make sure the Blob URL was created in the same [storage partition](storagePartitioningExplainer) as the context it is being fetched from.
-
-If access to unpartitioned Blob URLs is needed, the Storage Access API [can be used](storageAccessAPI).

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

@@ -1,8 +0,0 @@
-# An aria-labelledby attribute doesn't match any element id
-
-An `aria-labelledby` attribute doesn't match any element `id`. This might prevent
-the browser from correctly autofilling the form and accessibility tools from
-working correctly.
-
-To fix this issue, make sure that `aria-labelledby` is a space-separated list of
-element `id`s.

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

@@ -1,5 +0,0 @@
-# Incorrect use of autocomplete attribute
-
-A form field's `autocomplete` attribute is empty. This might prevent the browser from correctly autofilling the form.
-
-To fix this issue, provide a valid `autocomplete` value.

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

@@ -1,5 +0,0 @@
-# Duplicate form field id in the same form
-
-Multiple form field elements in the same form have the same `id` attribute value. This might prevent the browser from correctly autofilling the form.
-
-To fix this issue, use unique `id` attribute values for each form field.

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

@@ -1,5 +0,0 @@
-# A form field element should have an id or name attribute
-
-A form field element has neither an `id` nor a `name` attribute. This might prevent the browser from correctly autofilling the form.
-
-To fix this issue, add a unique `id` or `name` attribute to a form field. This is not strictly needed, but still recommended even if you have an autocomplete attribute on the same element.

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

@@ -1,5 +0,0 @@
-# An element doesn't have an autocomplete attribute
-
-A form field has an `id` or `name` attribute that the browser's autofill recognizes. However, it doesn't have an `autocomplete` attribute assigned. This might prevent the browser from correctly autofilling the form.
-
-To fix this issue, provide an `autocomplete` attribute.

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

@@ -1,5 +0,0 @@
-# Non-standard `autocomplete` attribute value
-
-An `autocomplete` attribute of a form field uses a non-standard HTML value. This might prevent the browser from correctly autofilling the form.
-
-To fix this issue, use a valid `autocomplete` value.

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

@@ -1,5 +0,0 @@
-# Form field without valid aria-labelledby attribute or associated label
-
-A form field has neither a valid `aria-labelledby` attribute nor an associated `<label>`. This might prevent the browser from correctly autofilling the form and accessibility tools from working correctly.
-
-To fix this issue, provide a `<label>` describing the purpose of the form field.

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

@@ -1,5 +0,0 @@
-# Incorrect use of <label for=FORM_ELEMENT>
-
-The label's `for` attribute doesn't match any element `id`. This might prevent the browser from correctly autofilling the form and accessibility tools from working correctly.
-
-To fix this issue, make sure the label's `for` attribute references the correct `id` of a form field.

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

@@ -1,5 +0,0 @@
-# Incorrect use of <label for=FORM_ELEMENT>
-
-The label's `for` attribute refers to a form field by its `name`, not its `id`. This might prevent the browser from correctly autofilling the form and accessibility tools from working correctly.
-
-To fix this issue, refer to form fields by their `id` attribute.

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

@@ -1,5 +0,0 @@
-# No label associated with a form field
-
-A `<label>` isn't associated with a form field.
-
-To fix this issue, nest the `<input>` in the `<label>` or provide a `for` attribute on the `<label>` that matches a form field `id`.

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

@@ -1,7 +0,0 @@
-# Session History Item Has Been Marked Skippable
-
-A session history item was added by this document without any interaction from the
-user. As a result, this document's history items will be skipped if the user goes
-back or forward via the browser's UI (e.g., back/forward buttons), to prevent pages
-from trapping a user. If the user interacts with the page, the history items
-will no longer be skipped.

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

@@ -1,4 +0,0 @@
-# Response was blocked by CORB (Cross-Origin Read Blocking)
-
-Cross-Origin Read Blocking (CORB) blocked a cross-origin response.
-

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

@@ -1,10 +0,0 @@
-# An ad on your site has exceeded resource limits
-
-Chrome identifies heavy ads on your site that use too many resources without a user gesture. Heavy ads have an impact on performance and harm the user’s browsing experience. They increase battery drain, consume mobile data, and make your site slow. To improve the user experience, Chrome warns about or removes heavy ads.
-
-An ad is considered heavy if the user has not interacted with it (for example, has not tapped or clicked it) and it meets any of the following criteria:
-* Uses the main thread for more than 60 seconds in total (CPU total limit)
-* Uses the main thread for more than 15 seconds in any 30 second window (CPU peak limit)
-* Uses more than 4 megabytes of network bandwidth (Network limit)
-
-Stop this from happening by only showing ads that stay within resource limits.

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

@@ -1,5 +0,0 @@
-# Mixed content: load all resources via HTTPS to improve the security of your site
-
-Even though the initial HTML page is loaded over a secure HTTPS connection, some resources like images, stylesheets or scripts are being accessed over an insecure HTTP connection. Usage of insecure resources is restricted to strengthen the security of your entire site.
-
-To resolve this issue, load all resources over a secure HTTPS connection.

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

@@ -1,5 +0,0 @@
-# Navigating Partitioned Blob URL Issue
-
-This issue occurs when 'noopener' was enforced during navigation to a cross-partition, same-origin Blob URL. The navigation won't be blocked due to it being cross-partition, but APIs like window.open won't return a WindowProxy for the new window in this case.
-
-If your application requires a WindowProxy object to be returned by navigating to the Blob URL, make sure the Blob URL has the same top-level site as the context it is navigated fetched from.

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

@@ -1,3 +0,0 @@
-# This is a placeholder issue description
-
-This description is used for issues that are not intended to be shown to the user. This means there is no need for a useful description.

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

@@ -1,3 +0,0 @@
-# An @property rule was ignored
-
-An @property rule is ignored because the property name is invalid.