chrome-devtools-frontend 1.0.1665921 → 1.0.1666631

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

@@ -1 +1 @@
-# The provider's accounts list endpoint cannot be found.
+# The provider’s accounts list endpoint can’t be found

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

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

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

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

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

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

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

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

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

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

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

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

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

@@ -1 +1 @@
-# The provider's id token endpoint cannot be found.
+# The provider’s id token endpoint can’t be found

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

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

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

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

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

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

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

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

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

@@ -1 +1 @@
-# The provider's FedCM manifest configuration cannot be found.
+# The provider’s FedCM manifest configuration can’t be found

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

@@ -1 +1 @@
-# getUserInfo() caller is not an iframe.
+# getUserInfo() caller isn’t an iframe

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

@@ -1 +1 @@
-# getUserInfo() failed because the config URL is not potentially trustworthy.
+# getUserInfo() failed because the config URL isn’t potentially trustworthy

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

@@ -1 +1 @@
-# getUserInfo() caller is not same origin as the config URL.
+# getUserInfo() caller isn’t same origin as the config URL

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

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

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

@@ -1,7 +1,7 @@
-# Fetching Partitioned Blob URL Issue
+# 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.
+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/front_end/models/issues_manager/descriptions/genericFormAriaLabelledByToNonExistingIdError.md

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

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

@@ -1,5 +1,5 @@
 # Incorrect use of autocomplete attribute
 
-A form field's `autocomplete` attribute is empty. This might prevent the browser from correctly autofilling the form.
+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/front_end/models/issues_manager/descriptions/genericFormDuplicateIdForInputError.md

@@ -1,5 +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 prevent the browser from correctly autofilling the 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/front_end/models/issues_manager/descriptions/genericFormEmptyIdAndNameAttributesForInputError.md

@@ -1,5 +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 prevent the browser from correctly autofilling the form.
+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 is not strictly needed, but still recommended even if you have an autocomplete attribute on the same element.
+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/front_end/models/issues_manager/descriptions/genericFormInputAssignedAutocompleteValueToIdOrNameAttributeError.md

@@ -1,5 +1,5 @@
-# An element doesn't have an autocomplete attribute
+# 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.
+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/front_end/models/issues_manager/descriptions/genericFormInputHasWrongButWellIntendedAutocompleteValueError.md

@@ -1,5 +1,5 @@
 # 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.
+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/front_end/models/issues_manager/descriptions/genericFormInputWithNoLabelError.md

@@ -1,5 +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 prevent the browser from correctly autofilling the form and accessibility tools from working correctly.
+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/front_end/models/issues_manager/descriptions/genericFormLabelForMatchesNonExistingIdError.md

@@ -1,5 +1,5 @@
 # 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.
+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.
+To fix this issue, make sure the label’s `for` attribute references the correct `id` of a form field.

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

@@ -1,5 +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 prevent the browser from correctly autofilling the form and accessibility tools from working correctly.
+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/front_end/models/issues_manager/descriptions/genericFormLabelHasNeitherForNorNestedInputError.md

@@ -1,5 +1,5 @@
 # No label associated with a form field
 
-A `<label>` isn't 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/front_end/models/issues_manager/descriptions/genericFormModelContextMissingToolName.md

@@ -1,5 +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 does not specify a name. A tool name is required for an AI model to correctly identify and invoke the tool.
+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/front_end/models/issues_manager/descriptions/genericFormModelContextParameterMissingName.md

@@ -1,5 +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 cannot format the parameter payload correctly when invoking the tool.
+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/front_end/models/issues_manager/descriptions/genericFormModelContextRequiredParameterMissingName.md

@@ -1,5 +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 cannot format the parameter payload correctly when invoking the tool.
+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/front_end/models/issues_manager/descriptions/genericNavigationEntryMarkedSkippable.md

@@ -1,7 +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 prevent pages
+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/front_end/models/issues_manager/descriptions/heavyAd.md

@@ -2,7 +2,7 @@
 
 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:
+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)

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

@@ -4,4 +4,4 @@ An image on this page specifies `loading="lazy"` without explicit width and heig
 
 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 prevent layout shifts, always include explicit `width` and `height` attributes on lazy-loaded images, or define their aspect ratio using CSS.
+To stop layout shifts, always include explicit `width` and `height` attributes on lazy-loaded images, or define their aspect ratio using CSS.

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

@@ -1,5 +1,5 @@
-# Navigating Partitioned Blob URL Issue
+# 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.
+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.
+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/front_end/models/issues_manager/descriptions/permissionElementActivationDisabled.md

@@ -1,6 +1,6 @@
 # Activation disabled
 
-The "{PLACEHOLDER_Type}" element could not be activated for the following reason: {PLACEHOLDER_DisableReason}.
+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.
 

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

@@ -1,6 +1,6 @@
 # Activation disabled
 
-The "{PLACEHOLDER_Type}" element could not be activated for the following reason: {PLACEHOLDER_DisableReason}.
+The "{PLACEHOLDER_Type}" element couldn’t be activated for the following reason: {PLACEHOLDER_DisableReason}.
 
 The element is occluded by: "{PLACEHOLDER_OccluderInfo}"
 

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

@@ -1,6 +1,6 @@
 # Activation disabled
 
-The "{PLACEHOLDER_Type}" element could not be activated for the following reason: {PLACEHOLDER_DisableReason}.
+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}")
 

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

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

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

@@ -1,5 +1,5 @@
 # Font size too large
 
-The "{PLACEHOLDER_Type}" element's font size is 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'.
+To resolve this issue, ensure that the element’s font is at most `xx-large`.

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

@@ -1,5 +1,5 @@
 # Font size too small
 
-The "{PLACEHOLDER_Type}" element's font size is 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'.
+To resolve this issue, ensure that the element’s font is at least `small`.

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

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

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

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

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

@@ -1,5 +1,5 @@
 # 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.
+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.
+To resolve this issue, use absolute or relative lengths for the element’s width and height.

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

@@ -1,5 +1,5 @@
 # Invalid type attribute
 
-The "{PLACEHOLDER_Type}" type is not supported.
+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".
+To resolve this issue, ensure the element’s type is one of the supported values: "camera", "microphone", "geolocation", "camera microphone".

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

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

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

@@ -2,4 +2,4 @@
 
 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%.
+To resolve this issue, ensure the element’s text and background colors have their alpha channel value at 100%.

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

@@ -1,6 +1,6 @@
 # Unsupported bottom padding
 
-The "{PLACEHOLDER_Type}" element does not support `padding-bottom`.
+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`.
+To resolve this issue, ensure the element’s `padding-bottom` is unset or identical to `padding-top`.

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

@@ -1,6 +1,6 @@
 # Unsupported right padding
 
-The "{PLACEHOLDER_Type}" element does not support `padding-right`.
+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`.
+To resolve this issue, ensure the element’s `padding-right` is unset or identical to `padding-left`.

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

@@ -1,5 +1,5 @@
 # Request in progress
 
-A permission request on the "{PLACEHOLDER_Type}" element was prevented because a previous request is still in progress.
+A permission request on the "{PLACEHOLDER_Type}" element was stopped 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).
+To resolve this issue, ensure that the site doesn’t 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 isn’t covered by the scrim).

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

@@ -1,5 +1,5 @@
 # Activation disabled (quota)
 
-The "{PLACEHOLDER_Type}" element could not be activated because the page's quota has been exceeded.
+The "{PLACEHOLDER_Type}" element couldn’t 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/front_end/models/issues_manager/descriptions/permissionElementTypeNotSupported.md

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

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

@@ -2,6 +2,6 @@
 
 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.
+To resolve this issue, don’t use frameworks which simulate click events, (e.g. via `click()`) and don’t stop the `DOMActivate` event.
 
 You can use the command line flag `--runtime-enabled-features=BypassPepcSecurityForTesting` to bypass this behavior for testing purposes.

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

@@ -1,3 +1,3 @@
 # 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.
+This description is used for issues that aren’t intended to be shown to the user. This means there is no need for a useful description.

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

@@ -1,6 +1,6 @@
 # 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.
+An element which isn’t allowed in the content model of the `<optgroup>` element was found within an `<optgroup>` element. These elements won’t 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.
 

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

@@ -1,6 +1,6 @@
 # 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.
+An element which isn’t allowed in the content model of the `<select>` element was found within a `<select>` element. These elements won’t 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.
 

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

@@ -1,3 +1,3 @@
 # 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.
+An element with `contenteditable` or `tabindex` attributes isn’t an allowed child of a `<select>` element. It won’t consistently be accessible to people navigating by keyboard or using assistive technology.

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

@@ -1,3 +1,3 @@
 # 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.
+An interactive element which isn’t allowed in the content model of the `<legend>` element was found within a `<legend>` element. Interactive elements aren’t allowed children of a `<legend>` element when used within an `<optgroup>` element. These elements won’t consistently be accessible to people navigating by keyboard or using assistive technology.

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

@@ -1,3 +1,3 @@
 # 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.
+An interactive element which isn’t allowed in the content model of the `<option>` element was found within an `<option>` element. These elements won’t consistently be accessible to people navigating by keyboard or using assistive technology.

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

@@ -1,3 +1,3 @@
 # 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.
+The `<option>` element allows only non-interactive phrasing content, text, and `<div>` elements as its children. The semantics of non-phrasing content elements don’t 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.