simdeck 0.1.3 → 0.1.5

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/federatedAuthRequestIdTokenNoResponse.md

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

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/federatedAuthRequestInvalidSigninResponse.md

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

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/federatedAuthRequestManifestHttpNotFound.md

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

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/federatedAuthRequestManifestInvalidResponse.md

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

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/federatedAuthRequestManifestNoResponse.md

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

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/federatedAuthRequestTooManyRequests.md

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

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/federatedAuthUserInfoRequestInvalidAccountsResponse.md

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

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/federatedAuthUserInfoRequestInvalidConfigOrWellKnown.md

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

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/federatedAuthUserInfoRequestNoAccountSharingPermission.md

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

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/federatedAuthUserInfoRequestNoApiPermission.md

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

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/federatedAuthUserInfoRequestNoReturningUserFromFetchedAccounts.md

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

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/federatedAuthUserInfoRequestNotIframe.md

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

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/federatedAuthUserInfoRequestNotPotentiallyTrustworthy.md

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

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/federatedAuthUserInfoRequestNotSameOrigin.md

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

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/federatedAuthUserInfoRequestNotSignedInWithIdp.md

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

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/fetchingPartitionedBlobURL.md

@@ -0,0 +1,7 @@
+# Fetching Partitioned Blob URL Issue
+
+This issue occurs when a Blob URL access attempt was blocked because it was made from a cross-partition, same-origin context.
+
+Make sure the Blob URL was created in the same [storage partition](storagePartitioningExplainer) as the context it is being fetched from.
+
+If access to unpartitioned Blob URLs is needed, the Storage Access API [can be used](storageAccessAPI).

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/genericFormAriaLabelledByToNonExistingId.md

@@ -0,0 +1,8 @@
+# An aria-labelledby attribute doesn't match any element id
+
+An `aria-labelledby` attribute doesn't match any element `id`. This might prevent
+the browser from correctly autofilling the form and accessibility tools from
+working correctly.
+
+To fix this issue, make sure that `aria-labelledby` is a space-separated list of
+element `id`s.

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/genericFormAutocompleteAttributeEmptyError.md

@@ -0,0 +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.
+
+To fix this issue, provide a valid `autocomplete` value.

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/genericFormDuplicateIdForInputError.md

@@ -0,0 +1,5 @@
+# Duplicate form field id in the same form
+
+Multiple form field elements in the same form have the same `id` attribute value. This might prevent the browser from correctly autofilling the form.
+
+To fix this issue, use unique `id` attribute values for each form field.

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/genericFormEmptyIdAndNameAttributesForInputError.md

@@ -0,0 +1,5 @@
+# A form field element should have an id or name attribute
+
+A form field element has neither an `id` nor a `name` attribute. This might prevent the browser from correctly autofilling the form.
+
+To fix this issue, add a unique `id` or `name` attribute to a form field. This is not strictly needed, but still recommended even if you have an autocomplete attribute on the same element.

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/genericFormInputAssignedAutocompleteValueToIdOrNameAttributeError.md

@@ -0,0 +1,5 @@
+# An element doesn't have an autocomplete attribute
+
+A form field has an `id` or `name` attribute that the browser's autofill recognizes. However, it doesn't have an `autocomplete` attribute assigned. This might prevent the browser from correctly autofilling the form.
+
+To fix this issue, provide an `autocomplete` attribute.

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/genericFormInputHasWrongButWellIntendedAutocompleteValueError.md

@@ -0,0 +1,5 @@
+# Non-standard `autocomplete` attribute value
+
+An `autocomplete` attribute of a form field uses a non-standard HTML value. This might prevent the browser from correctly autofilling the form.
+
+To fix this issue, use a valid `autocomplete` value.

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/genericFormInputWithNoLabelError.md

@@ -0,0 +1,5 @@
+# Form field without valid aria-labelledby attribute or associated label
+
+A form field has neither a valid `aria-labelledby` attribute nor an associated `<label>`. This might prevent the browser from correctly autofilling the form and accessibility tools from working correctly.
+
+To fix this issue, provide a `<label>` describing the purpose of the form field.

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/genericFormLabelForMatchesNonExistingIdError.md

@@ -0,0 +1,5 @@
+# Incorrect use of <label for=FORM_ELEMENT>
+
+The label's `for` attribute doesn't match any element `id`. This might prevent the browser from correctly autofilling the form and accessibility tools from working correctly.
+
+To fix this issue, make sure the label's `for` attribute references the correct `id` of a form field.

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/genericFormLabelForNameError.md

@@ -0,0 +1,5 @@
+# Incorrect use of <label for=FORM_ELEMENT>
+
+The label's `for` attribute refers to a form field by its `name`, not its `id`. This might prevent the browser from correctly autofilling the form and accessibility tools from working correctly.
+
+To fix this issue, refer to form fields by their `id` attribute.

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/genericFormLabelHasNeitherForNorNestedInput.md

@@ -0,0 +1,5 @@
+# No label associated with a form field
+
+A `<label>` isn't associated with a form field.
+
+To fix this issue, nest the `<input>` in the `<label>` or provide a `for` attribute on the `<label>` that matches a form field `id`.

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/genericResponseWasBlockedByORB.md

@@ -0,0 +1,4 @@
+# Response was blocked by CORB (Cross-Origin Read Blocking)
+
+Cross-Origin Read Blocking (CORB) blocked a cross-origin response.
+

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/heavyAd.md

@@ -0,0 +1,10 @@
+# An ad on your site has exceeded resource limits
+
+Chrome identifies heavy ads on your site that use too many resources without a user gesture. Heavy ads have an impact on performance and harm the user’s browsing experience. They increase battery drain, consume mobile data, and make your site slow. To improve the user experience, Chrome warns about or removes heavy ads.
+
+An ad is considered heavy if the user has not interacted with it (for example, has not tapped or clicked it) and it meets any of the following criteria:
+* Uses the main thread for more than 60 seconds in total (CPU total limit)
+* Uses the main thread for more than 15 seconds in any 30 second window (CPU peak limit)
+* Uses more than 4 megabytes of network bandwidth (Network limit)
+
+Stop this from happening by only showing ads that stay within resource limits.

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/mixedContent.md

@@ -0,0 +1,5 @@
+# Mixed content: load all resources via HTTPS to improve the security of your site
+
+Even though the initial HTML page is loaded over a secure HTTPS connection, some resources like images, stylesheets or scripts are being accessed over an insecure HTTP connection. Usage of insecure resources is restricted to strengthen the security of your entire site.
+
+To resolve this issue, load all resources over a secure HTTPS connection.

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/navigatingPartitionedBlobURL.md

@@ -0,0 +1,5 @@
+# Navigating Partitioned Blob URL Issue
+
+This issue occurs when 'noopener' was enforced during navigation to a cross-partition, same-origin Blob URL. The navigation won't be blocked due to it being cross-partition, but APIs like window.open won't return a WindowProxy for the new window in this case.
+
+If your application requires a WindowProxy object to be returned by navigating to the Blob URL, make sure the Blob URL has the same top-level site as the context it is navigated fetched from.

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/placeholderDescriptionForInvisibleIssues.md

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

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/propertyRuleInvalidNameIssue.md

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

package/client/dist/chrome-devtools-ui/models/issues_manager/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/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/selectElementAccessibilityDisallowedOptGroupChild.md

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

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/selectElementAccessibilityDisallowedSelectChild.md

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

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/selectElementAccessibilityInteractiveContentAttributesSelectDescendant.md

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

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/selectElementAccessibilityInteractiveContentLegendChild.md

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

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/selectElementAccessibilityInteractiveContentOptionChild.md

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

package/client/dist/chrome-devtools-ui/models/issues_manager/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 do not make sense as children of an `<option>`, and such semantics will largely be ignored by assistive technology since they are inappropriate in this context. Consider removing or changing such elements to one of the allowed phrasing content elements.

package/client/dist/chrome-devtools-ui/models/issues_manager/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, please ensure that this page opts-into cross-origin isolation by setting Cross-Origin-Opener-Policy and Cross-Origin-Embedder-Policy appropriately.
+
+Note that for each iframe, only the first issue is reported for performance reasons.

package/client/dist/chrome-devtools-ui/models/issues_manager/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/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/sharedDictionaryUseErrorDictionaryLoadFailure.md

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

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/sharedDictionaryUseErrorMatchingDictionaryNotUsed.md

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

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/sharedDictionaryUseErrorUnexpectedContentDictionaryHeader.md

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

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/sharedDictionaryWriteErrorCossOriginNoCorsRequest.md

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

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/sharedDictionaryWriteErrorDisallowedBySettings.md

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

package/client/dist/chrome-devtools-ui/models/issues_manager/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/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/sharedDictionaryWriteErrorFeatureDisabled.md

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

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/sharedDictionaryWriteErrorInsufficientResources.md

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

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/sharedDictionaryWriteErrorInvalidMatchField.md

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

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/sharedDictionaryWriteErrorInvalidStructuredHeader.md

@@ -0,0 +1 @@
+# `Use-As-Dictionary` HTTP response header is not a valid Structured Field value

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/sharedDictionaryWriteErrorNavigationRequest.md

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

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/sharedDictionaryWriteErrorNoMatchField.md

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

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/sharedDictionaryWriteErrorNonListMatchDestField.md

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

package/client/dist/chrome-devtools-ui/models/issues_manager/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/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/sharedDictionaryWriteErrorNonStringIdField.md

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

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/sharedDictionaryWriteErrorNonStringInMatchDestList.md

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

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/sharedDictionaryWriteErrorNonStringMatchField.md

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

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/sharedDictionaryWriteErrorNonTokenTypeField.md

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

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/sharedDictionaryWriteErrorRequestAborted.md

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

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/sharedDictionaryWriteErrorShuttingDown.md

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

package/client/dist/chrome-devtools-ui/models/issues_manager/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/client/dist/chrome-devtools-ui/models/issues_manager/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/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/sriInvalidSignatureHeader.md

@@ -0,0 +1,14 @@
+# A `signature` header is not 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/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/sriInvalidSignatureInputHeader.md

@@ -0,0 +1,15 @@
+# A `signature-input` header is not 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/client/dist/chrome-devtools-ui/models/issues_manager/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/client/dist/chrome-devtools-ui/models/issues_manager/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 cannot 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/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/sriSignatureHeaderValueIsIncorrectLength.md

@@ -0,0 +1,11 @@
+# A `signature` header contains a signature which cannot 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.
+
+For example, the following header contains a valid Ed25519 signature labeled
+"label":
+
+```
+Signature: label=:gHim9e5Pk2H7c9BStOmxSmkyc8+ioZgoxynu3d4INAT4dwfj5LhvaV9DFnEQ9p7C0hzW4o4Qpkm5aApd6WLLCw==:
+```

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/sriSignatureHeaderValueIsNotByteSequence.md

@@ -0,0 +1,14 @@
+# A `signature` header member's value is not 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/client/dist/chrome-devtools-ui/models/issues_manager/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/client/dist/chrome-devtools-ui/models/issues_manager/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/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/sriSignatureInputHeaderInvalidComponentType.md

@@ -0,0 +1,13 @@
+# A `signature-input` header's component is not 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/client/dist/chrome-devtools-ui/models/issues_manager/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/client/dist/chrome-devtools-ui/models/issues_manager/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/client/dist/chrome-devtools-ui/models/issues_manager/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/client/dist/chrome-devtools-ui/models/issues_manager/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) is not a base64-encoded
+256 bit sequence, and therefore cannot 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/client/dist/chrome-devtools-ui/models/issues_manager/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 cannot be verified.

package/client/dist/chrome-devtools-ui/models/issues_manager/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/client/dist/chrome-devtools-ui/models/issues_manager/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/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/sriSignatureInputHeaderValueNotInnerList.md

@@ -0,0 +1,11 @@
+# A `signature-input` header has a member whose value is not an Inner List.
+
+The value of each member of a [`signature-input`](aignatureInputHeader) 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/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/sriValidationFailedIntegrityMismatch.md

@@ -0,0 +1,12 @@
+# 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) do not match the integrity
+assertions made by the request's initiator. Verificiation failed.
+
+The following are the keys specified by the request's initiator:
+
+<ul>
+  {PLACEHOLDER_integrityAssertions}
+</ul>

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/sriValidationFailedInvalidLength.md

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

package/client/dist/chrome-devtools-ui/models/issues_manager/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 is not possible.

package/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/sriValidationFailedSignatureMismatch.md

@@ -0,0 +1,11 @@
+# Signature verification failed.
+
+The public key specified in the [`signature-input`](signatureInputHeader)
+header's [`keyid` parameter](signatureParameters) does not 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/client/dist/chrome-devtools-ui/models/issues_manager/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/client/dist/chrome-devtools-ui/models/issues_manager/descriptions/stylesheetRequestFailed.md

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