@mcp-b/chrome-devtools-mcp 2.2.0 → 2.3.0

package/build/src/third_party/issue-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/src/third_party/issue-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/src/third_party/issue-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/src/third_party/issue-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/src/third_party/issue-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/src/third_party/issue-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/src/third_party/issue-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/src/third_party/issue-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/src/third_party/issue-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/src/third_party/issue-descriptions/deprecation.md

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

package/build/src/third_party/issue-descriptions/federatedAuthRequestAccountsHttpNotFound.md

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

package/build/src/third_party/issue-descriptions/federatedAuthRequestAccountsInvalidResponse.md

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

package/build/src/third_party/issue-descriptions/federatedAuthRequestAccountsNoResponse.md

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

package/build/src/third_party/issue-descriptions/federatedAuthRequestApprovalDeclined.md

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

package/build/src/third_party/issue-descriptions/federatedAuthRequestCanceled.md

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

package/build/src/third_party/issue-descriptions/federatedAuthRequestErrorFetchingSignin.md

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

package/build/src/third_party/issue-descriptions/federatedAuthRequestErrorIdToken.md

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

package/build/src/third_party/issue-descriptions/federatedAuthRequestIdTokenHttpNotFound.md

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

package/build/src/third_party/issue-descriptions/federatedAuthRequestIdTokenInvalidRequest.md

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

package/build/src/third_party/issue-descriptions/federatedAuthRequestIdTokenInvalidResponse.md

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

package/build/src/third_party/issue-descriptions/federatedAuthRequestIdTokenNoResponse.md

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

package/build/src/third_party/issue-descriptions/federatedAuthRequestInvalidSigninResponse.md

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

package/build/src/third_party/issue-descriptions/federatedAuthRequestManifestHttpNotFound.md

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

package/build/src/third_party/issue-descriptions/federatedAuthRequestManifestInvalidResponse.md

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

package/build/src/third_party/issue-descriptions/federatedAuthRequestManifestNoResponse.md

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

package/build/src/third_party/issue-descriptions/federatedAuthRequestTooManyRequests.md

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

package/build/src/third_party/issue-descriptions/federatedAuthUserInfoRequestInvalidAccountsResponse.md

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

package/build/src/third_party/issue-descriptions/federatedAuthUserInfoRequestInvalidConfigOrWellKnown.md

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

package/build/src/third_party/issue-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/src/third_party/issue-descriptions/federatedAuthUserInfoRequestNoApiPermission.md

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

package/build/src/third_party/issue-descriptions/federatedAuthUserInfoRequestNoReturningUserFromFetchedAccounts.md

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

package/build/src/third_party/issue-descriptions/federatedAuthUserInfoRequestNotIframe.md

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

package/build/src/third_party/issue-descriptions/federatedAuthUserInfoRequestNotPotentiallyTrustworthy.md

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

package/build/src/third_party/issue-descriptions/federatedAuthUserInfoRequestNotSameOrigin.md

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

package/build/src/third_party/issue-descriptions/federatedAuthUserInfoRequestNotSignedInWithIdp.md

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

package/build/src/third_party/issue-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/src/third_party/issue-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/src/third_party/issue-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/src/third_party/issue-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/src/third_party/issue-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/src/third_party/issue-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/src/third_party/issue-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/src/third_party/issue-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/src/third_party/issue-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/src/third_party/issue-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/src/third_party/issue-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/src/third_party/issue-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/src/third_party/issue-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/src/third_party/issue-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/src/third_party/issue-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/src/third_party/issue-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/src/third_party/issue-descriptions/permissionElementActivationDisabled.md

@@ -1,7 +0,0 @@
-# Activation disabled
-
-The "{PLACEHOLDER_Type}" element could not be activated for the following reason: {PLACEHOLDER_DisableReason}.
-
-To resolve this issue, ensure that the element follows all styling restrictions and is fully visible to the user.
-
-You can use the command line flag `--runtime-enabled-features=BypassPepcSecurityForTesting` to bypass this behavior for testing purposes.

package/build/src/third_party/issue-descriptions/permissionElementActivationDisabledWithOccluder.md

@@ -1,9 +0,0 @@
-# Activation disabled
-
-The "{PLACEHOLDER_Type}" element could not be activated for the following reason: {PLACEHOLDER_DisableReason}.
-
-The element is occluded by: "{PLACEHOLDER_OccluderInfo}"
-
-To resolve this issue, ensure that the element follows all styling restrictions and is fully visible to the user.
-
-You can use the command line flag `--runtime-enabled-features=BypassPepcSecurityForTesting` to bypass this behavior for testing purposes.

package/build/src/third_party/issue-descriptions/permissionElementActivationDisabledWithOccluderParent.md

@@ -1,9 +0,0 @@
-# Activation disabled
-
-The "{PLACEHOLDER_Type}" element could not be activated for the following reason: {PLACEHOLDER_DisableReason}.
-
-The element is occluded by: "{PLACEHOLDER_OccluderInfo}" (parent element: "{PLACEHOLDER_OccluderParentInfo}")
-
-To resolve this issue, ensure that the element follows all styling restrictions and is fully visible to the user.
-
-You can use the command line flag `--runtime-enabled-features=BypassPepcSecurityForTesting` to bypass this behavior for testing purposes.

package/build/src/third_party/issue-descriptions/permissionElementCspFrameAncestorsMissing.md

@@ -1,5 +0,0 @@
-# CSP `frame-ancestors` missing
-
-The "{PLACEHOLDER_Type}" element is used in a cross-origin iframe, but the required `frame-ancestors` Content Security Policy directive is missing.
-
-To resolve this issue, add a `frame-ancestors` Content Security Policy directive to the iframe.

package/build/src/third_party/issue-descriptions/permissionElementFencedFrameDisallowed.md

@@ -1,5 +0,0 @@
-# Fenced frame disallowed
-
-The "{PLACEHOLDER_Type}" element is not allowed in a fenced frame.
-
-To resolve this issue, ensure the element is not used in a fenced frame.

package/build/src/third_party/issue-descriptions/permissionElementFontSizeTooLarge.md

@@ -1,5 +0,0 @@
-# Font size too large
-
-The "{PLACEHOLDER_Type}" element's font size is too large.
-
-To resolve this issue, ensure that the element's font is at most 'xx-large'.

package/build/src/third_party/issue-descriptions/permissionElementFontSizeTooSmall.md

@@ -1,5 +0,0 @@
-# Font size too small
-
-The "{PLACEHOLDER_Type}" element's font size is too small.
-
-To resolve this issue, ensure that the element's font is at least 'small'.

package/build/src/third_party/issue-descriptions/permissionElementGeolocationDeprecated.md

@@ -1,5 +0,0 @@
-# Geolocation deprecated
-
-Using `<permission type="geolocation">` is deprecated.
-
-To resolve this issue, use the `<geolocation>` element instead.

package/build/src/third_party/issue-descriptions/permissionElementInsetBoxShadowUnsupported.md

@@ -1,5 +0,0 @@
-# Unsupported inset box shadow
-
-The "{PLACEHOLDER_Type}" element does not support `inset` box shadows.
-
-To resolve this issue, remove the `inset` keyword from the relevant stylesheet.

package/build/src/third_party/issue-descriptions/permissionElementInvalidDisplayStyle.md

@@ -1,5 +0,0 @@
-# Invalid display style
-
-The "{PLACEHOLDER_Type}" element has an invalid display style. Values that result in an unsupported layout are not allowed.
-
-To resolve this issue, consider using 'inline-block', 'block', or 'flex' instead.

package/build/src/third_party/issue-descriptions/permissionElementInvalidSizeValue.md

@@ -1,5 +0,0 @@
-# Invalid size value
-
-Content, intrinsic, or stretch sizes are not supported as values for the min/max width and height of the "{PLACEHOLDER_Type}" element.
-
-To resolve this issue, use absolute or relative lengths for the element's width and height.

package/build/src/third_party/issue-descriptions/permissionElementInvalidType.md

@@ -1,5 +0,0 @@
-# Invalid type attribute
-
-The "{PLACEHOLDER_Type}" type is not supported.
-
-To resolve this issue, ensure the element's type is one of the supported values: "camera", "microphone", "geolocation", "camera microphone".

package/build/src/third_party/issue-descriptions/permissionElementInvalidTypeActivation.md

@@ -1,5 +0,0 @@
-# Invalid type activation
-
-An element with the "{PLACEHOLDER_Type}" type was attempted to be activated. However this type is not supported.
-
-To resolve this issue, ensure the element's type is one of the supported values: "camera", "microphone", "geolocation", "camera microphone".

package/build/src/third_party/issue-descriptions/permissionElementLowContrast.md

@@ -1,5 +0,0 @@
-# Low contrast
-
-The contrast between the text color and background color of the "{PLACEHOLDER_Type}" element is too low.
-
-To resolve this issue, ensure that your text/background colors have more contrast between them.

package/build/src/third_party/issue-descriptions/permissionElementNonOpaqueColor.md

@@ -1,5 +0,0 @@
-# Non-opaque color
-
-The text color or background color of the "{PLACEHOLDER_Type}" element is non-opaque.
-
-To resolve this issue, ensure the element's text and background colors have their alpha channel value at 100%.

package/build/src/third_party/issue-descriptions/permissionElementPaddingBottomUnsupported.md

@@ -1,6 +0,0 @@
-# Unsupported bottom padding
-
-The "{PLACEHOLDER_Type}" element does not support `padding-bottom`.
-`padding-bottom` is always set to be identical to `padding-top`.
-
-To resolve this issue, ensure the element's `padding-bottom` is unset or identical to `padding-top`.

package/build/src/third_party/issue-descriptions/permissionElementPaddingRightUnsupported.md

@@ -1,6 +0,0 @@
-# Unsupported right padding
-
-The "{PLACEHOLDER_Type}" element does not support `padding-right`.
-`padding-right` is always set to be identical to `padding-left`.
-
-To resolve this issue, ensure the element's `padding-right` is unset or identical to `padding-left`.

package/build/src/third_party/issue-descriptions/permissionElementPermissionsPolicyBlocked.md

@@ -1,5 +0,0 @@
-# Permissions policy blocked
-
-The "{PLACEHOLDER_Type}" element is blocked by the "{PLACEHOLDER_PermissionName}" permission policy.
-
-To resolve this issue, ensure the frame which contains the element is loaded with the appropriate permission policy by its embedder.

package/build/src/third_party/issue-descriptions/permissionElementRegistrationFailed.md

@@ -1,5 +0,0 @@
-# Quota exceeded
-
-The "{PLACEHOLDER_Type}" element has surpassed the maximum instances quota per page.
-
-To resolve this issue, ensure that you have no more than 3 elements of the same type per page.

package/build/src/third_party/issue-descriptions/permissionElementRequestInProgress.md

@@ -1,5 +0,0 @@
-# Request in progress
-
-A permission request on the "{PLACEHOLDER_Type}" element was prevented because a previous request is still in progress.
-
-To resolve this issue, ensure that the site does not allow users to interact with the element behind the current content scrim (for example by moving the element to a document in a new window, which is not covered by the scrim).

package/build/src/third_party/issue-descriptions/permissionElementSecurityChecksFailed.md

@@ -1,5 +0,0 @@
-# Activation disabled (quota)
-
-The "{PLACEHOLDER_Type}" element could not be activated because the page's quota has been exceeded.
-
-To resolve this issue, ensure that you have no more than 3 elements of the same type per page.

package/build/src/third_party/issue-descriptions/permissionElementTypeNotSupported.md

@@ -1,5 +0,0 @@
-# Permission not supported
-
-The permission type "{PLACEHOLDER_Type}" is not supported by this browser and therefore the element will not be functional.
-
-To resolve this issue, ensure the element's type is one of the supported values: "camera", "microphone", "geolocation", "camera microphone".

package/build/src/third_party/issue-descriptions/permissionElementUntrustedEvent.md

@@ -1,7 +0,0 @@
-# Untrusted event
-
-The "{PLACEHOLDER_Type}" element can only be activated by actual user clicks, not simulated ones.
-
-To resolve this issue, do not use frameworks which simulate click events, (e.g. via `click()`) and do not prevent the `DOMActivate` event.
-
-You can use the command line flag `--runtime-enabled-features=BypassPepcSecurityForTesting` to bypass this behavior for testing purposes.

package/build/src/third_party/issue-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/src/third_party/issue-descriptions/propertyRuleInvalidNameIssue.md

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

package/build/src/third_party/issue-descriptions/propertyRuleIssue.md

@@ -1,7 +0,0 @@
-# Ignored @property rule
-
-An @property rule is ignored because it contains an invalid property or is missing a required one:
-
-```
-{PLACEHOLDER_property}
-```

package/build/src/third_party/issue-descriptions/selectElementAccessibilityDisallowedOptGroupChild.md

@@ -1,7 +0,0 @@
-# Invalid element or text node within <optgroup>
-
-An element which is not allowed in the content model of the `<optgroup>` element was found within an `<optgroup>` element. These elements will not consistently be accessible to people navigating by keyboard or using assistive technology.
-
-If using disallowed elements for layout structure and styling, consider using the allowed `<div>` element instead.
-
-Any text existing within the `<optgroup>` element should either be removed or relocated to a valid element that allows text descendants, e.g., the `<legend>` or `<option>` elements.

package/build/src/third_party/issue-descriptions/selectElementAccessibilityDisallowedSelectChild.md

@@ -1,7 +0,0 @@
-# Invalid element or text node within <select>
-
-An element which is not allowed in the content model of the `<select>` element was found within a `<select>` element. These elements will not consistently be accessible to people navigating by keyboard or using assistive technology.
-
-If using disallowed elements for layout structure and styling, consider using the allowed `<div>` element instead.
-
-Any text existing within the `<select>` element should either be removed or relocated to a valid element that allows text descendants, e.g., an `<optgroup>` with a `<legend>` element or `<option>` elements.

package/build/src/third_party/issue-descriptions/selectElementAccessibilityInteractiveContentAttributesSelectDescendant.md

@@ -1,3 +0,0 @@
-# Element with invalid attributes within a <select> element
-
-An element with `contenteditable` or `tabindex` attributes is not an allowed child of a `<select>` element. It will not consistently be accessible to people navigating by keyboard or using assistive technology.

package/build/src/third_party/issue-descriptions/selectElementAccessibilityInteractiveContentLegendChild.md

@@ -1,3 +0,0 @@
-# Interactive element inside of a <legend> element
-
-An interactive element which is not allowed in the content model of the `<legend>` element was found within a `<legend>` element. Interactive elements are not allowed children of a `<legend>` element when used within an `<optgroup>` element. These elements will not consistently be accessible to people navigating by keyboard or using assistive technology.

package/build/src/third_party/issue-descriptions/selectElementAccessibilityInteractiveContentOptionChild.md

@@ -1,3 +0,0 @@
-# Interactive element inside of an <option> element
-
-An interactive element which is not allowed in the content model of the `<option>` element was found within an `<option>` element. These elements will not consistently be accessible to people navigating by keyboard or using assistive technology.

package/build/src/third_party/issue-descriptions/selectElementAccessibilityNonPhrasingContentOptionChild.md

@@ -1,3 +0,0 @@
-# Non-phrasing content used within an <option> element
-
-The `<option>` element allows only non-interactive phrasing content, text, and `<div>` elements as its children. The semantics of non-phrasing content elements do not make sense as children of an `<option>`, and such semantics will largely be ignored by assistive technology since they are inappropriate in this context. Consider removing or changing such elements to one of the allowed phrasing content elements.

package/build/src/third_party/issue-descriptions/selectivePermissionsIntervention.md

@@ -1,7 +0,0 @@
-# Selective Permissions Intervention
-
-The Selective Permissions Intervention blocks calls to privacy-sensitive APIs when they are called from ad scripts in order to align the permission grant with the user's intent. The particular API that was blocked, the call-stack that triggered the intervention, and why the script that called the API is considered ad-related is shown below.
-
-Note that Chrome considers any script with a URL that matches a rule in the [filterlist](ChromeFilterlistRepository) as ad script, and the matching rule is shown in the Ad Ancestry section. In addition, any script loaded while an ad script is in the JavaScript stack will also be considered an ad script by Chrome and is also shown in Ad Ancestry.
-
-If you believe this intervention  was in error (e.g., this call would occur even when loading the page with an ad blocker enabled), then please [file a bug](SelectivePermissionsInterventionIssue).

package/build/src/third_party/issue-descriptions/sharedArrayBuffer.md

@@ -1,7 +0,0 @@
-# SharedArrayBuffer usage is restricted to cross-origin isolated sites
-
-SharedArrayBuffers (SABs) can be used to construct high-resolution timers. High-resolution timers simplify Spectre attacks on cross-origin resources.
-
-To mitigate security risks across browsers, SharedArrayBuffers are gated behind cross-origin isolated contexts starting with Chrome 92 (July 2021). To continue using SharedArrayBuffers, please ensure that this page opts-into cross-origin isolation by setting Cross-Origin-Opener-Policy and Cross-Origin-Embedder-Policy appropriately.
-
-Note that for each iframe, only the first issue is reported for performance reasons.

package/build/src/third_party/issue-descriptions/sharedDictionaryUseErrorCrossOriginNoCorsRequest.md

@@ -1 +0,0 @@
-# Found a matching dictionary, but the dictionary can't be used for the cross origin no-cors request

package/build/src/third_party/issue-descriptions/sharedDictionaryUseErrorDictionaryLoadFailure.md

@@ -1,3 +0,0 @@
-# Failed to load the matching dictionary
-
-A matching dictionary was found but it failed to load.

package/build/src/third_party/issue-descriptions/sharedDictionaryUseErrorMatchingDictionaryNotUsed.md

@@ -1,3 +0,0 @@
-# Found a matching dictionary, but the dictionary is not used for the response
-
-Consider revisiting the `match` pattern or `match-dest` of the dictionary.

package/build/src/third_party/issue-descriptions/sharedDictionaryUseErrorUnexpectedContentDictionaryHeader.md

@@ -1 +0,0 @@
-# Can't decode the response because the header of dictionary compressed stream was not set correctly

package/build/src/third_party/issue-descriptions/sharedDictionaryWriteErrorCossOriginNoCorsRequest.md

@@ -1 +0,0 @@
-# Can't register the cross origin response fetched by a no-cors request as as a dictionary

package/build/src/third_party/issue-descriptions/sharedDictionaryWriteErrorDisallowedBySettings.md

@@ -1 +0,0 @@
-# Compression Dictionary is disabled by settings

package/build/src/third_party/issue-descriptions/sharedDictionaryWriteErrorExpiredResponse.md

@@ -1,3 +0,0 @@
-# The response can't be used as a dictionary because its freshness is expired
-
-Check `Cache-Control` and `Expires` headers.