chrome-devtools-frontend 1.0.1665921 → 1.0.1667564

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.

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

@@ -1,7 +1,7 @@
-# Selective Permissions Intervention
+# 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.
+The Selective Permissions Intervention blocks calls to privacy-sensitive APIs when they are called from ad scripts 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).
+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 [file a bug](SelectivePermissionsInterventionIssue).

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

@@ -2,6 +2,6 @@
 
 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.
+To mitigate security risks across browsers, SharedArrayBuffers are gated behind cross-origin isolated contexts starting with Chrome 92 (July 2021). To continue using SharedArrayBuffers, 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/front_end/models/issues_manager/descriptions/sharedDictionaryUseErrorCrossOriginNoCorsRequest.md

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

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

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

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

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

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

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

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

@@ -1 +1 @@
-# Compression Dictionary is disabled by settings
+# compression dictionary is disabled by settings

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

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

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

@@ -1,3 +1,3 @@
-# Compression Dictionary Transport feature is disabled
+# compression dictionary transport feature is disabled
 
-Please enable chrome://flags/#enable-compression-dictionary-transport
+enable chrome://flags/#enable-compression-dictionary-transport

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

@@ -1 +1 @@
-# `Use-As-Dictionary` HTTP response header is not a valid Structured Field value
+# `Use-As-Dictionary` HTTP response header isn’t a valid Structured Field Value

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

@@ -1,3 +1,3 @@
-# Can't register the response of the navigation request as a dictionary
+# Can’t register the response of the navigation request as a dictionary
 
-Navigation responses are not usable as compression dictionaries.
+Navigation responses aren’t usable as compression dictionaries.

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

@@ -1,9 +1,9 @@
-# A `signature` header is not formatted as a Structured Field Dictionary.
+# A `signature` header isn’t formatted as a Structured Field Dictionary
 
-Responses' [`signature`](signatureHeader) header should be formatted as a
-[Dictionary](sfDictionary) containing one or more signatures. Each member's key
+Responses’ [`signature`](signatureHeader) header should be formatted as a
+[Dictionary](sfDictionary) containing one or more signatures. Each member’s key
 is a label for the signature which maps it to the relevant metadata defined in
-a [`signature-input`](signatureInputHeader) header. Each member's value is a
+a [`signature-input`](signatureInputHeader) header. Each member’s value is a
 [Byte Sequence](sfByteSequence) containing the signature itself.
 
 For example, the following header contains a single Ed25519 signature labeled

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

@@ -1,10 +1,10 @@
-# A `signature-input` header is not formatted as a Structured Field Dictionary.
+# A `signature-input` header isn’t formatted as a Structured Field Dictionary
 
-Responses' [`signature-input`](signatureInputHeader) header should be formatted
+Responses’ [`signature-input`](signatureInputHeader) header should be formatted
 as a [Dictionary](sfDictionary) containing metadata regarding one or more
-signatures. Each member's key is a label for the metadata which maps it to the
+signatures. Each member’s key is a label for the metadata which maps it to the
 relevant signature defined in a [`signature`](signatureHeader) header. Each
-member's value is an [Inner List](sfInnerList) containing a set of components
+member’s value is an [Inner List](sfInnerList) containing a set of components
 over which a signature is generated. The list may have one or more parameters.
 
 For example, the following header contains metadata for a signature labeled

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

@@ -1,4 +1,4 @@
-# A `signature-input` header was specified without an accompanying `signature` header.
+# A `signature-input` header was specified without an accompanying `signature` header
 
 [`signature-input`](signatureInputHeader) headers specify metadata that allows
 verification of signatures delivered with a response. If no

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

@@ -1,7 +1,7 @@
-# A `signature` header was specified without an accompanying `signature-input` header.
+# A `signature` header was specified without an accompanying `signature-input` header
 
 [`signature`](signatureHeader) headers specify signatures which can be verified
-against a given response. Verification cannot proceed, however, in the absence of a
+against a given response. Verification can’t proceed, however, in the absence of a
 [`signature-input`](signatureInputHeader) header which defines relevant metadata
 which allows servers and clients to agree on the exact message which is being
 signed. Both headers must be present for verification to proceed.

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

@@ -1,7 +1,7 @@
-# A `signature` header contains a signature which cannot be verified.
+# A `signature` header contains a signature which can’t be verified
 
 This browser can only verify Ed25519 signatures, which are 512 bits long. The
-signature delivered with this response does not match that length.
+signature delivered with this response doesn’t match that length.
 
 For example, the following header contains a valid Ed25519 signature labeled
 "label":

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

@@ -1,9 +1,9 @@
-# A `signature` header member's value is not a Byte Sequence.
+# A `signature` header member’s value isn’t a Byte Sequence
 
-Responses' [`signature`](signatureHeader) header should be formatted as a
-[Dictionary](sfDictionary) containing one or more signatures. Each member's key
+Responses’ [`signature`](signatureHeader) header should be formatted as a
+[Dictionary](sfDictionary) containing one or more signatures. Each member’s key
 is a label for the signature which maps it to the relevant metadata defined in
-a [`signature-input`](signatureInputHeader) header. Each member's value is a
+a [`signature-input`](signatureInputHeader) header. Each member’s value is a
 [Byte Sequence](sfByteSequence) containing the signature itself.
 
 For example, the following header contains a single Ed25519 signature labeled