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

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

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

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

@@ -0,0 +1,5 @@
+# Request 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 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/build/src/third_party/issue-descriptions/permissionElementSecurityChecksFailed.md

@@ -0,0 +1,5 @@
+# Activation disabled (quota)
+
+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/build/src/third_party/issue-descriptions/permissionElementTypeNotSupported.md

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

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

@@ -0,0 +1,7 @@
+# Untrusted event
+
+The "{PLACEHOLDER_Type}" element can only be activated by actual user clicks, not simulated ones.
+
+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/build/src/third_party/issue-descriptions/placeholderDescriptionForInvisibleIssues.md

@@ -0,0 +1,3 @@
+# This is a placeholder issue 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/build/src/third_party/issue-descriptions/propertyRuleInvalidNameIssue.md

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

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

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

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

@@ -0,0 +1,7 @@
+# Invalid element or text node within <optgroup>
+
+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.
+
+Any text existing within the `<optgroup>` element should either be removed or relocated to a valid element that allows text descendants, e.g., the `<legend>` or `<option>` elements.

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

@@ -0,0 +1,7 @@
+# Invalid element or text node within <select>
+
+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.
+
+Any text existing within the `<select>` element should either be removed or relocated to a valid element that allows text descendants, e.g., an `<optgroup>` with a `<legend>` element or `<option>` elements.

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

@@ -0,0 +1,3 @@
+# Element with invalid attributes within a <select> element
+
+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/build/src/third_party/issue-descriptions/selectElementAccessibilityInteractiveContentLegendChild.md

@@ -0,0 +1,3 @@
+# Interactive element inside of a <legend> element
+
+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/build/src/third_party/issue-descriptions/selectElementAccessibilityInteractiveContentOptionChild.md

@@ -0,0 +1,3 @@
+# Interactive element inside of an <option> element
+
+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/build/src/third_party/issue-descriptions/selectElementAccessibilityNonPhrasingContentOptionChild.md

@@ -0,0 +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 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/build/src/third_party/issue-descriptions/selectivePermissionsIntervention.md

@@ -0,0 +1,7 @@
+# Selective permissions intervention
+
+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 [file a bug](SelectivePermissionsInterventionIssue).

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

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

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

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

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

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

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

@@ -0,0 +1,3 @@
+# 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/build/src/third_party/issue-descriptions/sharedDictionaryUseErrorUnexpectedContentDictionaryHeader.md

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

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

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

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

@@ -0,0 +1 @@
+# compression dictionary is disabled by settings

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

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

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

@@ -0,0 +1,3 @@
+# compression dictionary transport feature is disabled
+
+enable chrome://flags/#enable-compression-dictionary-transport

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

@@ -0,0 +1 @@
+# Failed to write the dictionary due to insufficient resources

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

@@ -0,0 +1 @@
+# Unable to parse the `match` field of the `Use-As-Dictionary` HTTP response header

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

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

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

@@ -0,0 +1 @@
+# The `ttl` field of the `Use-As-Dictionary` HTTP response header must be a positive integer

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

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

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

@@ -0,0 +1 @@
+# There is no `match` field in the `Use-As-Dictionary` HTTP response header

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

@@ -0,0 +1 @@
+# The `ttl` field of the `Use-As-Dictionary` HTTP response header must be an integer

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

@@ -0,0 +1 @@
+# The `match-dest` field of the `Use-As-Dictionary` HTTP response header must be a list

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

@@ -0,0 +1,3 @@
+# Unable to register a dictionary in a non-Secure Context
+
+Compression dictionaries are only available over HTTPS.

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

@@ -0,0 +1 @@
+# The `id` field of the `Use-As-Dictionary` HTTP response header must be a string

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

@@ -0,0 +1 @@
+# Items in the `match-dest` field of the `Use-As-Dictionary` HTTP response header must be strings

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

@@ -0,0 +1 @@
+# The `match` field of the `Use-As-Dictionary` HTTP response header must be a string

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

@@ -0,0 +1 @@
+# The `type` field of the `Use-As-Dictionary` HTTP response header must be a token

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

@@ -0,0 +1 @@
+# An error occurred while writing the dictionary

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

@@ -0,0 +1 @@
+# Failed to write the dictionary due to shutdown

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

@@ -0,0 +1,3 @@
+# The `id` field of the `Use-As-Dictionary` HTTP response header is too long
+
+The `id` field must not be longer than 1024 characters.

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

@@ -0,0 +1,3 @@
+# The `type` field of the `Use-As-Dictionary` HTTP response header must be `raw`
+
+Only `raw` dictionaries are currently supported.

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

@@ -0,0 +1,14 @@
+# 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
+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
+[Byte Sequence](sfByteSequence) containing the signature itself.
+
+For example, the following header contains a single Ed25519 signature labeled
+"label":
+
+```
+Signature: label=:gHim9e5Pk2H7c9BStOmxSmkyc8+ioZgoxynu3d4INAT4dwfj5LhvaV9DFnEQ9p7C0hzW4o4Qpkm5aApd6WLLCw==:
+```

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

@@ -0,0 +1,15 @@
+# A `signature-input` header isn’t formatted as a Structured Field Dictionary
+
+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
+relevant signature defined in a [`signature`](signatureHeader) header. Each
+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
+"label":
+
+```
+Signature-Input: signature=("unencoded-digest";sf);keyid="JrQLj5P/89iXES9+vFgrIy29clF9CC/oPPsw3c5D0bs=";tag="sri"
+```

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

@@ -0,0 +1,8 @@
+# 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
+[`signature`](signatureHeader) header is present, the
+[`signature-input`](signatureInputHeader) header can be omitted, as it serves no
+useful purpose in the absence of signatures. Both headers must be present for
+verification to proceed.

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

@@ -0,0 +1,7 @@
+# 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 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/build/src/third_party/issue-descriptions/sriSignatureHeaderValueIsIncorrectLength.md

@@ -0,0 +1,11 @@
+# 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 doesn’t match that length.
+
+For example, the following header contains a valid Ed25519 signature labeled
+"label":
+
+```
+Signature: label=:gHim9e5Pk2H7c9BStOmxSmkyc8+ioZgoxynu3d4INAT4dwfj5LhvaV9DFnEQ9p7C0hzW4o4Qpkm5aApd6WLLCw==:
+```

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

@@ -0,0 +1,14 @@
+# 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
+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
+[Byte Sequence](sfByteSequence) containing the signature itself.
+
+For example, the following header contains a single Ed25519 signature labeled
+"label":
+
+```
+Signature: label=:gHim9e5Pk2H7c9BStOmxSmkyc8+ioZgoxynu3d4INAT4dwfj5LhvaV9DFnEQ9p7C0hzW4o4Qpkm5aApd6WLLCw==:
+```

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

@@ -0,0 +1,15 @@
+# A `signature` header member’s value is parameterized
+
+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
+[Byte Sequence](sfByteSequence) containing the signature itself, with no
+additional parameters specified.
+
+For example, the following header contains a single Ed25519 signature labeled
+"label":
+
+```
+Signature: label=:gHim9e5Pk2H7c9BStOmxSmkyc8+ioZgoxynu3d4INAT4dwfj5LhvaV9DFnEQ9p7C0hzW4o4Qpkm5aApd6WLLCw==:
+```

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

@@ -0,0 +1,8 @@
+# A `signature-input` header member’s value contains an unknown component
+
+The metadata delivered via [`signature-input`](signatureInputHeader) can only
+contain a limited set of components in the list it specifies. The known
+components are:
+
+* "`unencoded-digest`"
+* "`@path`"

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

@@ -0,0 +1,13 @@
+# A `signature-input` header’s component isn’t a string
+
+Responses’ [`signature-input`](signatureInputHeader) header’s members’ values
+are [Inner Lists](sfInnerList) whose contents are each strings. Perhaps you
+forgot double-quotes around a component?
+
+```
+// Correct:
+Signature-Input: signature=("unencoded-digest";sf);keyid="JrQLj5P/89iXES9+vFgrIy29clF9CC/oPPsw3c5D0bs=";tag="sri"
+
+// Incorrect:
+Signature-Input: signature=(unencoded-digest;sf);keyid="JrQLj5P/89iXES9+vFgrIy29clF9CC/oPPsw3c5D0bs=";tag="sri"
+```

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

@@ -0,0 +1,4 @@
+# Invalid parameter on a derived component in a `signature-input` header
+
+Derived components must be specified as deriving from the request, using the
+[`req` parameter](componentParameterReq). No other parameter may be specified.

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

@@ -0,0 +1,5 @@
+# Invalid parameter on a header component in a `signature-input` header
+
+The header [`unencoded-digest`](unencodedDigestHeader) must be specified as
+being strictly serialized in the signature base, using the
+[`sf` parameter](componentParameterSf). No other parameter may be specified.

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

@@ -0,0 +1,11 @@
+# Invalid parameter on the list of components in a `signature-input` header
+
+The `signature-input` header’s [Inner Lists](sfInnerList) must be specified with the
+[`keyid` and `type` parameters](signatureParameters). The following parameters may
+also be specified:
+
+* `created`
+* `expires`
+* `nonce`
+
+No other parameter may be specified.

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

@@ -0,0 +1,12 @@
+# Invalid `keyid` value in a `signature-input` header
+
+The key specified in a [`signature-input`](signatureInputHeader) header’s
+[`keyid` parameter](signatureParameters) isn’t a base64-encoded
+256 bit sequence, and therefore can’t be decoded as an Ed25519 public key.
+
+Note that the `keyid` parameter’s value is a string, not a
+[Byte Sequence](sfByteSequence). For example:
+
+```
+Signature-Input: signature=("unencoded-digest";sf);keyid="JrQLj5P/89iXES9+vFgrIy29clF9CC/oPPsw3c5D0bs=";tag="sri"
+```

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

@@ -0,0 +1,6 @@
+# Label mismatch between `signature` and `signature-input` headers
+
+A [`signature`](signatureHeader) header specifies a signature whose label does
+not appear in a corresponding [`signature-input`](signatureInputHeader) header.
+Without a `signature-input` header’s definition of the signature’s metadata,
+the signature can’t be verified.

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

@@ -0,0 +1,8 @@
+# Missing a required parameter on the list of components in a `signature-input` header
+
+The [`signature-input`][signatureInputHeader] header’s [Inner Lists](sfInnerList)
+must be specified with both the [`keyid` and `type` parameters](signatureParameters).
+
+```
+Signature-Input: signature=("unencoded-digest";sf);keyid="JrQLj5P/89iXES9+vFgrIy29clF9CC/oPPsw3c5D0bs=";tag="sri"
+```

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

@@ -0,0 +1,11 @@
+# Missing a required component in a `signature-input` header
+
+The [`signature-input`](signatureInputHeader) header’s
+[Inner Lists](sfInnerList) must contain the string "`unencoded-digest`" with an
+`sf` parameter:
+
+For example:
+
+```
+Signature-Input: signature=("unencoded-digest";sf);keyid="JrQLj5P/89iXES9+vFgrIy29clF9CC/oPPsw3c5D0bs=";tag="sri"
+```

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

@@ -0,0 +1,11 @@
+# A `signature-input` header has a member whose value isn’t an Inner List
+
+The value of each member of a [`signature-input`](signatureInputHeader) header’s
+[Dictionary][sfDictionary] must be an [Inner List](sfInnerList) containing the
+set of components over which a signature is generated.
+
+For example:
+
+```
+Signature-Input: signature=("unencoded-digest";sf);keyid="JrQLj5P/89iXES9+vFgrIy29clF9CC/oPPsw3c5D0bs=";tag="sri"
+```

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

@@ -0,0 +1,10 @@
+# Integrity verification failed
+
+The signature associated with a response could be successfully verified, but the
+public keys asserted in the [`signature-input`](signatureInputHeader)
+header’s [`keyid` parameter](signatureParameters) don’t match the integrity
+assertions made by the request’s initiator. Verification failed.
+
+The following are the keys specified by the request’s initiator:
+
+{PLACEHOLDER_integrityAssertions}

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

@@ -0,0 +1,5 @@
+# Signature verification failed: the signature provided isn’t an Ed25519 signature
+
+The signature specified in a [`signature`](signatureHeader) header isn’t a
+base64-encoded 512 bit Byte Sequence, and can therefore not be verified as an
+Ed25519 signature.

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

@@ -0,0 +1,6 @@
+# Signature verification failed: the signature is expired
+
+The [`expires` parameter](signatureParameters) specified in a
+[`signature-input`](signatureInputHeader) header is a UNIX timestamp
+representing a time in the past. The signature has therefore expired, and
+verification isn’t possible.

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

@@ -0,0 +1,11 @@
+# Signature verification failed
+
+The public key specified in the [`signature-input`](signatureInputHeader)
+header’s [`keyid` parameter](signatureParameters) doesn’t match the signature
+specified in the [`signature`](signatureHeader) header. Verification failed.
+
+The following is the signature base over which the verification attempt was made:
+
+```
+{PLACEHOLDER_signatureBase}
+```

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

@@ -0,0 +1,4 @@
+# Define @import rules at the top of the stylesheet
+
+An @import rule was ignored because it wasn’t defined at the top of the stylesheet. Such rules must appear at the top,
+before any style declaration and any other at-rule with the exception of @charset and @layer.

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

@@ -0,0 +1,3 @@
+# Verify stylesheet URLs
+
+This page failed to load a stylesheet from a URL.

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

@@ -0,0 +1,3 @@
+# Interactive element inside of a <summary> element
+
+An interactive element was found within a `<summary>` element. These elements won’t consistently be accessible to people navigating by keyboard or using assistive technology.

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

@@ -0,0 +1,12 @@
+# An `unencoded-digest` header contains a digest with an incorrect length
+
+[`unencoded-digest`](unencodedDigestHeader) headers contain SHA2 digests of a
+response’s body. The digest delivered with this response isn’t the correct
+length for the algorithm specified. SHA-256 digests should be 256 bits long,
+SHA-512 digests 512 bits long. For example, if the body was "Hello, world.", the
+following might be an appropriate header:
+
+```
+Unencoded-Digest: sha-256=:+MO/YqmqPm/BYZwlDkir51GTc9Pt9BvmLrXcRRma8u8=:,
+                  sha-512=:S7LmUoguRQsq3IHIZ0Xhm5jjCDqH6uUQbumuj5CnrIFDk+RyBW/dWuqzEiV4mPaB:
+```

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

@@ -0,0 +1,17 @@
+# An `unencoded-digest` header contains a digest with an invalid type
+
+[`unencoded-digest`](unencodedDigestHeader) headers must be formatted as a
+[Dictionary](sfDictionary), wherein each member’s label specifies the hashing
+algorithm, and the value is a [Byte Sequence](sfByteSequence) containing the
+digest. The digest delivered with this response did not deliver the digest as a
+Byte Sequence.
+
+For example, if the body was "Hello, world.":
+
+```
+// Correctly formatted header:
+Unencoded-Digest: sha-256=:+MO/YqmqPm/BYZwlDkir51GTc9Pt9BvmLrXcRRma8u8=:
+
+// Incorrectly formatted header (quotes rather than colons):
+Unencoded-Digest: sha-256="+MO/YqmqPm/BYZwlDkir51GTc9Pt9BvmLrXcRRma8u8="
+```

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

@@ -0,0 +1,14 @@
+# An `unencoded-digest` header can’t be parsed
+
+[`unencoded-digest`](unencodedDigestHeader) headers must be formatted as a
+[Dictionary](sfDictionary), wherein each member’s label specifies the hashing
+algorithm, and the value is a [Byte Sequence](sfByteSequence) containing the
+digest. The digest delivered with this response did not format the response
+correctly.
+
+For example, if the body was "Hello, world.", the following would be a correctly
+formatted header:
+
+```
+Unencoded-Digest: sha-256=:+MO/YqmqPm/BYZwlDkir51GTc9Pt9BvmLrXcRRma8u8=:
+```

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

@@ -0,0 +1,15 @@
+# An `unencoded-digest` header contains a digest with an invalid algorithm
+
+[`unencoded-digest`](unencodedDigestHeader) headers support only two hashing
+algorithms, SHA-256, and SHA-512. The digests delivered with this response
+specified an unsupported algorithm:
+
+For example, if the body was "Hello, world.", the following would be an
+appropriate header:
+
+```
+Unencoded-Digest: sha-256=:+MO/YqmqPm/BYZwlDkir51GTc9Pt9BvmLrXcRRma8u8=:,
+                  sha-512=:S7LmUoguRQsq3IHIZ0Xhm5jjCDqH6uUQbumuj5CnrIFDk+RyBW/dWuqzEiV4mPaB:
+```
+
+Note also that the labels must be lower-case.

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

@@ -0,0 +1,3 @@
+# Manifest does not contain an `id` field
+
+Add an `id` to the manifest. Alternatively, for installs using an explicit manifest URL, provide the computed manifest ID as `manifestId` alongside the manifest URL.

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

@@ -0,0 +1,3 @@
+# Manifest does not contain a 'name' or 'short_name' field
+
+Add a `name` or `short_name` field to the manifest.

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

@@ -0,0 +1,3 @@
+# Manifest could not be fetched, is empty, or could not be parsed
+
+Check that the web app manifest can be fetched and that it contains valid, non-empty JSON.

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

@@ -0,0 +1,3 @@
+# No manifest detected
+
+Provide a web app manifest for this page.

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

@@ -0,0 +1,3 @@
+# Manifest 'start_url' is not valid
+
+Provide a valid `start_url` in the manifest.