@yezack/chrome-devtools-mcp-108 0.0.0-stage → 1.10.2

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

@@ -0,0 +1 @@
+# Email verification request failed because the email verification well-known file returned an invalid response

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

@@ -0,0 +1 @@
+# Email verification request failed because the email verification well-known file did not respond

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

@@ -0,0 +1 @@
+# Email verification request failed because the email address is invalid

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

@@ -0,0 +1 @@
+# Email verification request failed because the JWKS endpoint wasn’t found (HTTP 404)

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

@@ -0,0 +1 @@
+# Email verification request failed because the JWKS endpoint returned an invalid response

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

@@ -0,0 +1 @@
+# Email verification request failed because key binding signing failed

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

@@ -0,0 +1 @@
+# Email verification request failed because the Relying Party origin is opaque

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

@@ -0,0 +1 @@
+# Email verification request failed because the token endpoint wasn’t found (HTTP 404)

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

@@ -0,0 +1 @@
+# Email verification request failed because the token endpoint had an invalid Content-Type

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

@@ -0,0 +1 @@
+# Email verification request failed because the token endpoint response was invalid

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

@@ -0,0 +1 @@
+# Email verification request failed because the token endpoint returned an invalid SD-JWT

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

@@ -0,0 +1 @@
+# Email verification request failed because the token endpoint returned a malformed SD-JWT

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

@@ -0,0 +1 @@
+# Email verification request failed because there was no response from the token endpoint

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

@@ -0,0 +1 @@
+# Email verification request failed because the key binding audience claim is invalid

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

@@ -0,0 +1 @@
+# Email verification request failed because the key binding issued at claim is invalid

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

@@ -0,0 +1 @@
+# Email verification request failed because the key binding nonce claim is invalid

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

@@ -0,0 +1 @@
+# Email verification request failed because the key binding SD hash claim is invalid

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

@@ -0,0 +1 @@
+# Email verification request failed because the key binding type header is invalid

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

@@ -0,0 +1 @@
+# Email verification request failed because the key binding audience claim is missing

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

@@ -0,0 +1 @@
+# Email verification request failed because the key binding confirmation claim is missing

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

@@ -0,0 +1 @@
+# Email verification request failed because the key binding issued at claim is missing

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

@@ -0,0 +1 @@
+# Email verification request failed because the key binding nonce claim is missing

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

@@ -0,0 +1 @@
+# Email verification request failed because the key binding SD hash claim is missing

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

@@ -0,0 +1 @@
+# Email verification request failed because the key binding signature verification failed

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

@@ -0,0 +1 @@
+# Email verification request failed because the SD-JWT email claim is invalid

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

@@ -0,0 +1 @@
+# Email verification request failed because the SD-JWT email verified claim is invalid

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

@@ -0,0 +1 @@
+# Email verification request failed because the SD-JWT holder key is invalid

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

@@ -0,0 +1 @@
+# Email verification request failed because the SD-JWT issued at claim is invalid

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

@@ -0,0 +1 @@
+# Email verification request failed because the SD-JWT issuer claim is invalid

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

@@ -0,0 +1 @@
+# Email verification request failed because the SD-JWT JWKS is missing keys

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

@@ -0,0 +1 @@
+# Email verification request failed because the SD-JWT confirmation claim is missing

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

@@ -0,0 +1 @@
+# Email verification request failed because the SD-JWT email claim is missing

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

@@ -0,0 +1 @@
+# Email verification request failed because the SD-JWT issued at claim is missing

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

@@ -0,0 +1 @@
+# Email verification request failed because the SD-JWT issuer claim is missing

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

@@ -0,0 +1 @@
+# Email verification request failed because the SD-JWT signature verification failed

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

@@ -0,0 +1 @@
+# Email verification request failed because the SD-JWT signature header algorithm is unsupported

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

@@ -0,0 +1 @@
+# Email verification request failed because the user is logged out

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

@@ -0,0 +1 @@
+# Email verification request failed because the accounts endpoint in the well-known file is cross-origin

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

@@ -0,0 +1 @@
+# Email verification request failed because the well-known file wasn’t found (HTTP 404)

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

@@ -0,0 +1 @@
+# Email verification request failed because the well-known file had an invalid Content-Type

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

@@ -0,0 +1 @@
+# Email verification request failed because the well-known file response was invalid

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

@@ -0,0 +1 @@
+# Email verification request failed because the issuance endpoint in the well-known file is cross-origin

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

@@ -0,0 +1 @@
+# Email verification request failed because the well-known file list was empty

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

@@ -0,0 +1 @@
+# Email verification request failed because the well-known file is missing the accounts endpoint

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

@@ -0,0 +1 @@
+# Email verification request failed because the well-known file is missing the issuance endpoint

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

@@ -0,0 +1 @@
+# Email verification request failed because there was no response when fetching the well-known file

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

@@ -0,0 +1 @@
+# Email verification request failed because the well-known file specifies an unsupported signing algorithm

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

@@ -0,0 +1 @@
+# Fetching the provider's accounts list was blocked by the request's initiator's connection allowlists.

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

@@ -0,0 +1 @@
+# The provider’s accounts list endpoint can’t be found

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

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

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

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

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

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

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

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

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

@@ -0,0 +1 @@
+# Fetching the provider's FedCM manifest configuration was blocked by the request's initiator's connection allowlists.

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

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

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

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

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

@@ -0,0 +1 @@
+# Fetching the provider's token was blocked by the request's initiator's connection allowlists.

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

@@ -0,0 +1 @@
+# The provider’s id token endpoint can’t be found

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

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

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

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

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

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

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

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

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

@@ -0,0 +1 @@
+# The provider’s FedCM manifest configuration can’t be found

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

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

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

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

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

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

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

@@ -0,0 +1 @@
+# Fetching the provider's well-known file was blocked by the request's initiator's connection allowlists.

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

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

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

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

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

@@ -0,0 +1 @@
+# getUserInfo() failed because the user hasn’t yet used FedCM on this site with the provided IDP

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

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

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

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

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

@@ -0,0 +1 @@
+# getUserInfo() caller isn’t an iframe

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

@@ -0,0 +1 @@
+# getUserInfo() failed because the config URL isn’t potentially trustworthy

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

@@ -0,0 +1 @@
+# getUserInfo() caller isn’t same origin as the config URL

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

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

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

@@ -0,0 +1,7 @@
+# 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’s 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/genericBackUINavigationWouldSkipAd.md

@@ -0,0 +1,4 @@
+# Back UI Navigation Will Skip Ad
+
+An ad-related entry was found in the session history. If the user navigates back
+via the browser UI, this ad entry will be skipped.

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

@@ -0,0 +1,8 @@
+# An aria-labelledby attribute doesn’t match any element id
+
+An `aria-labelledby` attribute doesn’t match any element `id`. This might stop
+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

@@ -0,0 +1,5 @@
+# Incorrect use of autocomplete attribute
+
+A form field’s `autocomplete` attribute is empty. This might stop 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

@@ -0,0 +1,5 @@
+# Duplicate form field id in the same form
+
+Multiple form field elements in the same form have the same `id` attribute value. This might stop 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

@@ -0,0 +1,5 @@
+# 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 stop the browser from correctly autofilling the form.
+
+To fix this issue, add a unique `id` or `name` attribute to a form field. This isn’t 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

@@ -0,0 +1,5 @@
+# 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 stop the browser from correctly autofilling the form.
+
+To fix this issue, provide an `autocomplete` attribute.

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

@@ -0,0 +1,5 @@
+# Non-standard `autocomplete` attribute value
+
+An `autocomplete` attribute of a form field uses a non-standard HTML value. This might stop 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

@@ -0,0 +1,5 @@
+# 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 stop 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

@@ -0,0 +1,5 @@
+# Incorrect use of <label for=FORM_ELEMENT>
+
+The label’s `for` attribute doesn’t match any element `id`. This might stop 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

@@ -0,0 +1,5 @@
+# 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 stop 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

@@ -0,0 +1,5 @@
+# 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/genericFormModelContextMissingToolDescription.md

@@ -0,0 +1,5 @@
+# Missing tool description for a WebMCP declarative tool definition
+
+This form is intended to be used as a WebMCP declarative tool definition, but it lacks a description explaining what the tool does. Descriptions are critical for AI models to decide when to use a given tool.
+
+To fix this issue, provide a tool description via the `tooldescription` attribute.

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

@@ -0,0 +1,5 @@
+# Missing tool name for a WebMCP declarative tool definition
+
+This form is intended to be used as a WebMCP declarative tool definition, but it doesn’t specify a name. A tool name is required for an AI model to correctly identify and invoke the tool.
+
+To fix this issue, provide a tool name via the `toolname` attribute.

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

@@ -0,0 +1,5 @@
+# Parameter missing name for a WebMCP declarative tool definition
+
+An input element within this form lacks a `name` attribute. Without a name, the AI model can’t format the parameter payload correctly when invoking the tool.
+
+To fix this issue, ensure form parameters have a `name` attribute.

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

@@ -0,0 +1,5 @@
+# Missing parameter title and description for a WebMCP declarative tool definition
+
+A parameter within this form (such as an `<input>` field) is missing both a title and a description. An AI model needs this metadata to understand what information should be passed to this parameter when invoking the tool.
+
+To fix this issue, add a title and description to the form parameter.

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

@@ -0,0 +1,5 @@
+# Required parameter missing name for a WebMCP declarative tool definition
+
+A required input element within this form lacks a `name` attribute. Without a name, the AI model can’t format the parameter payload correctly when invoking the tool.
+
+To fix this issue, ensure all required form parameters have a `name` attribute.

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

@@ -0,0 +1,7 @@
+# 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 stop 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

@@ -0,0 +1,4 @@
+# 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

@@ -0,0 +1,10 @@
+# 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 hasn’t interacted with it (for example, hasn’t 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/lazyLoadImageZeroSize.md

@@ -0,0 +1,7 @@
+# Lazy-loaded images should have explicit dimensions
+
+An image on this page specifies `loading="lazy"` without explicit width and height dimensions or aspect ratio styling.
+
+When lazy-loaded images lack dimensions, the browser allocates an initial 0x0 bounding box before network loading completes. As the user scrolls and the image loads, its sudden expansion triggers unexpected layout shifts (CLS) and can displace or clip surrounding content.
+
+To stop layout shifts, always include explicit `width` and `height` attributes on lazy-loaded images, or define their aspect ratio using CSS.

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

@@ -0,0 +1,5 @@
+# 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

@@ -0,0 +1,5 @@
+# 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’s navigated fetched from.

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

@@ -0,0 +1,7 @@
+# Activation disabled
+
+The "{PLACEHOLDER_Type}" element couldn’t 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

@@ -0,0 +1,9 @@
+# Activation disabled
+
+The "{PLACEHOLDER_Type}" element couldn’t 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

@@ -0,0 +1,9 @@
+# Activation disabled
+
+The "{PLACEHOLDER_Type}" element couldn’t 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

@@ -0,0 +1,5 @@
+# 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

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

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

@@ -0,0 +1,5 @@
+# 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

@@ -0,0 +1,5 @@
+# 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

@@ -0,0 +1,5 @@
+# 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

@@ -0,0 +1,5 @@
+# Unsupported inset box shadow
+
+The "{PLACEHOLDER_Type}" element doesn’t 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

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

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

@@ -0,0 +1,5 @@
+# Invalid size value
+
+Content, intrinsic, or stretch sizes aren’t 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

@@ -0,0 +1,5 @@
+# Invalid type attribute
+
+The "{PLACEHOLDER_Type}" type isn’t 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

@@ -0,0 +1,5 @@
+# Invalid type activation
+
+An element with the "{PLACEHOLDER_Type}" type was attempted to be activated. However this type isn’t 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

@@ -0,0 +1,5 @@
+# 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

@@ -0,0 +1,5 @@
+# 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

@@ -0,0 +1,6 @@
+# Unsupported bottom padding
+
+The "{PLACEHOLDER_Type}" element doesn’t 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

@@ -0,0 +1,6 @@
+# Unsupported right padding
+
+The "{PLACEHOLDER_Type}" element doesn’t 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

@@ -0,0 +1,5 @@
+# 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.