ideamans-chrome-devtools-mcp 0.11.2 → 0.21.0

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/propertyRuleIssue.md

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

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/selectElementAccessibilityDisallowedOptGroupChild.md

@@ -1,7 +0,0 @@
-# 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/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/selectElementAccessibilityDisallowedSelectChild.md

@@ -1,7 +0,0 @@
-# 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/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/selectElementAccessibilityInteractiveContentAttributesSelectDescendant.md

@@ -1,3 +0,0 @@
-# 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/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/selectElementAccessibilityInteractiveContentLegendChild.md

@@ -1,3 +0,0 @@
-# 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/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/selectElementAccessibilityInteractiveContentOptionChild.md

@@ -1,3 +0,0 @@
-# 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/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/selectElementAccessibilityNonPhrasingContentOptionChild.md

@@ -1,3 +0,0 @@
-# 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/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/sharedArrayBuffer.md

@@ -1,7 +0,0 @@
-# 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/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/sharedDictionaryUseErrorCrossOriginNoCorsRequest.md

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

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/sharedDictionaryUseErrorDictionaryLoadFailure.md

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

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/sharedDictionaryUseErrorMatchingDictionaryNotUsed.md

@@ -1,3 +0,0 @@
-# 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/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/sharedDictionaryUseErrorUnexpectedContentDictionaryHeader.md

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

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/sharedDictionaryWriteErrorCossOriginNoCorsRequest.md

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

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/sharedDictionaryWriteErrorDisallowedBySettings.md

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

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/sharedDictionaryWriteErrorExpiredResponse.md

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

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/sharedDictionaryWriteErrorFeatureDisabled.md

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

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/sharedDictionaryWriteErrorInsufficientResources.md

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

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/sharedDictionaryWriteErrorInvalidMatchField.md

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

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/sharedDictionaryWriteErrorInvalidStructuredHeader.md

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

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/sharedDictionaryWriteErrorInvalidTTLField.md

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

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/sharedDictionaryWriteErrorNavigationRequest.md

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

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/sharedDictionaryWriteErrorNoMatchField.md

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

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/sharedDictionaryWriteErrorNonIntegerTTLField.md

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

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/sharedDictionaryWriteErrorNonListMatchDestField.md

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

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/sharedDictionaryWriteErrorNonSecureContext.md

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

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/sharedDictionaryWriteErrorNonStringIdField.md

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

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/sharedDictionaryWriteErrorNonStringInMatchDestList.md

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

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/sharedDictionaryWriteErrorNonStringMatchField.md

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

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/sharedDictionaryWriteErrorNonTokenTypeField.md

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

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/sharedDictionaryWriteErrorRequestAborted.md

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

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/sharedDictionaryWriteErrorShuttingDown.md

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

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/sharedDictionaryWriteErrorTooLongIdField.md

@@ -1,3 +0,0 @@
-# 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/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/sharedDictionaryWriteErrorUnsupportedType.md

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

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/sriInvalidSignatureHeader.md

@@ -1,14 +0,0 @@
-# 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/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/sriInvalidSignatureInputHeader.md

@@ -1,15 +0,0 @@
-# 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/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/sriMissingSignatureHeader.md

@@ -1,8 +0,0 @@
-# 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/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/sriMissingSignatureInputHeader.md

@@ -1,7 +0,0 @@
-# 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/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/sriSignatureHeaderValueIsIncorrectLength.md

@@ -1,11 +0,0 @@
-# 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/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/sriSignatureHeaderValueIsNotByteSequence.md

@@ -1,14 +0,0 @@
-# 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/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/sriSignatureHeaderValueIsParameterized.md

@@ -1,15 +0,0 @@
-# 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/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/sriSignatureInputHeaderInvalidComponentName.md

@@ -1,8 +0,0 @@
-# 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/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/sriSignatureInputHeaderInvalidComponentType.md

@@ -1,13 +0,0 @@
-# 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/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/sriSignatureInputHeaderInvalidDerivedComponentParameter.md

@@ -1,4 +0,0 @@
-# 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/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/sriSignatureInputHeaderInvalidHeaderComponentParameter.md

@@ -1,5 +0,0 @@
-# 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/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/sriSignatureInputHeaderInvalidParameter.md

@@ -1,11 +0,0 @@
-# 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/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/sriSignatureInputHeaderKeyIdLength.md

@@ -1,12 +0,0 @@
-# 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/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/sriSignatureInputHeaderMissingLabel.md

@@ -1,6 +0,0 @@
-# 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/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/sriSignatureInputHeaderMissingRequiredParameters.md

@@ -1,8 +0,0 @@
-# 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/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/sriSignatureInputHeaderValueMissingComponents.md

@@ -1,11 +0,0 @@
-# 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/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/sriSignatureInputHeaderValueNotInnerList.md

@@ -1,11 +0,0 @@
-# A `signature-input` header has a member whose value is not 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/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/sriValidationFailedIntegrityMismatch.md

@@ -1,10 +0,0 @@
-# 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:
-
-{PLACEHOLDER_integrityAssertions}

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/sriValidationFailedInvalidLength.md

@@ -1,5 +0,0 @@
-# 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/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/sriValidationFailedSignatureExpired.md

@@ -1,6 +0,0 @@
-# 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/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/sriValidationFailedSignatureMismatch.md

@@ -1,11 +0,0 @@
-# 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/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/stylesheetLateImport.md

@@ -1,4 +0,0 @@
-# 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/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/stylesheetRequestFailed.md

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

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/summaryElementAccessibilityInteractiveContentSummaryDescendant.md

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

package/build/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/unencodedDigestIncorrectDigestLength.md

@@ -1,12 +0,0 @@
-# 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 is not 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/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/unencodedDigestIncorrectDigestType.md

@@ -1,17 +0,0 @@
-# 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/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/unencodedDigestMalformedDictionary.md

@@ -1,14 +0,0 @@
-# An `unencoded-digest` header cannot 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/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/descriptions/unencodedDigestUnknownAlgorithm.md

@@ -1,15 +0,0 @@
-# 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/node_modules/chrome-devtools-frontend/front_end/models/issues_manager/issues_manager.js

@@ -1,35 +0,0 @@
-// Copyright 2019 The Chromium Authors
-// Use of this source code is governed by a BSD-style license that can be
-// found in the LICENSE file.
-import * as AttributionReportingIssue from './AttributionReportingIssue.js';
-import * as CheckFormsIssuesTrigger from './CheckFormsIssuesTrigger.js';
-import * as ClientHintIssue from './ClientHintIssue.js';
-import * as ContentSecurityPolicyIssue from './ContentSecurityPolicyIssue.js';
-import * as ContrastCheckTrigger from './ContrastCheckTrigger.js';
-import * as CookieDeprecationMetadataIssue from './CookieDeprecationMetadataIssue.js';
-import * as CookieIssue from './CookieIssue.js';
-import * as CorsIssue from './CorsIssue.js';
-import * as CrossOriginEmbedderPolicyIssue from './CrossOriginEmbedderPolicyIssue.js';
-import * as DeprecationIssue from './DeprecationIssue.js';
-import * as ElementAccessibilityIssue from './ElementAccessibilityIssue.js';
-import * as FederatedAuthUserInfoRequestIssue from './FederatedAuthUserInfoRequestIssue.js';
-import * as GenericIssue from './GenericIssue.js';
-import * as HeavyAdIssue from './HeavyAdIssue.js';
-import * as Issue from './Issue.js';
-import * as IssueAggregator from './IssueAggregator.js';
-import * as IssueResolver from './IssueResolver.js';
-import * as IssuesManager from './IssuesManager.js';
-import * as LowTextContrastIssue from './LowTextContrastIssue.js';
-import * as MarkdownIssueDescription from './MarkdownIssueDescription.js';
-import * as MixedContentIssue from './MixedContentIssue.js';
-import * as PartitioningBlobURLIssue from './PartitioningBlobURLIssue.js';
-import * as PropertyRuleIssue from './PropertyRuleIssue.js';
-import * as QuirksModeIssue from './QuirksModeIssue.js';
-import * as RelatedIssue from './RelatedIssue.js';
-import * as SharedArrayBufferIssue from './SharedArrayBufferIssue.js';
-import * as SharedDictionaryIssue from './SharedDictionaryIssue.js';
-import * as SourceFrameIssuesManager from './SourceFrameIssuesManager.js';
-import * as SRIMessageSignatureIssue from './SRIMessageSignatureIssue.js';
-import * as StylesheetLoadingIssue from './StylesheetLoadingIssue.js';
-import * as UnencodedDigestIssue from './UnencodedDigestIssue.js';
-export { AttributionReportingIssue, CheckFormsIssuesTrigger, ClientHintIssue, ContentSecurityPolicyIssue, ContrastCheckTrigger, CookieDeprecationMetadataIssue, CookieIssue, CorsIssue, CrossOriginEmbedderPolicyIssue, DeprecationIssue, ElementAccessibilityIssue, FederatedAuthUserInfoRequestIssue, GenericIssue, HeavyAdIssue, Issue, IssueAggregator, IssueResolver, IssuesManager, LowTextContrastIssue, MarkdownIssueDescription, MixedContentIssue, PartitioningBlobURLIssue, PropertyRuleIssue, QuirksModeIssue, RelatedIssue, SharedArrayBufferIssue, SharedDictionaryIssue, SourceFrameIssuesManager, SRIMessageSignatureIssue, StylesheetLoadingIssue, UnencodedDigestIssue, };

package/build/node_modules/chrome-devtools-frontend/front_end/models/logs/LogManager.js

@@ -1,67 +0,0 @@
-// Copyright 2018 The Chromium Authors
-// Use of this source code is governed by a BSD-style license that can be
-// found in the LICENSE file.
-import * as Common from '../../core/common/common.js';
-import * as SDK from '../../core/sdk/sdk.js';
-import { NetworkLog } from './NetworkLog.js';
-const modelToEventListeners = new WeakMap();
-let instance = null;
-export class LogManager {
-    constructor() {
-        SDK.TargetManager.TargetManager.instance().observeModels(SDK.LogModel.LogModel, this);
-    }
-    static instance({ forceNew } = { forceNew: false }) {
-        if (!instance || forceNew) {
-            instance = new LogManager();
-        }
-        return instance;
-    }
-    modelAdded(logModel) {
-        const eventListeners = [];
-        eventListeners.push(logModel.addEventListener("EntryAdded" /* SDK.LogModel.Events.ENTRY_ADDED */, this.logEntryAdded, this));
-        modelToEventListeners.set(logModel, eventListeners);
-    }
-    modelRemoved(logModel) {
-        const eventListeners = modelToEventListeners.get(logModel);
-        if (eventListeners) {
-            Common.EventTarget.removeEventListeners(eventListeners);
-        }
-    }
-    logEntryAdded(event) {
-        const { logModel, entry } = event.data;
-        const target = logModel.target();
-        const details = {
-            url: entry.url,
-            line: entry.lineNumber,
-            parameters: [entry.text, ...(entry.args ?? [])],
-            stackTrace: entry.stackTrace,
-            timestamp: entry.timestamp,
-            workerId: entry.workerId,
-            category: entry.category,
-            affectedResources: entry.networkRequestId ? { requestId: entry.networkRequestId } : undefined,
-        };
-        const consoleMessage = new SDK.ConsoleModel.ConsoleMessage(target.model(SDK.RuntimeModel.RuntimeModel), entry.source, entry.level, entry.text, details);
-        if (entry.networkRequestId) {
-            NetworkLog.instance().associateConsoleMessageWithRequest(consoleMessage, entry.networkRequestId);
-        }
-        const consoleModel = target.model(SDK.ConsoleModel.ConsoleModel);
-        if (consoleMessage.source === "worker" /* Protocol.Log.LogEntrySource.Worker */) {
-            const workerId = consoleMessage.workerId || '';
-            // We have a copy of worker messages reported through the page, so that
-            // user can see messages from the worker which has been already destroyed.
-            // When opening DevTools, give us some time to connect to the worker and
-            // not report the message twice if the worker is still alive.
-            if (SDK.TargetManager.TargetManager.instance().targetById(workerId)) {
-                return;
-            }
-            window.setTimeout(() => {
-                if (!SDK.TargetManager.TargetManager.instance().targetById(workerId)) {
-                    consoleModel?.addMessage(consoleMessage);
-                }
-            }, 1000);
-        }
-        else {
-            consoleModel?.addMessage(consoleMessage);
-        }
-    }
-}