opera-devtools-mcp 0.2.4 → 0.3.0

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

@@ -1,8 +0,0 @@
-# Migrate entirely to HTTPS to allow cookies to be set by same-site subresources
-
-A cookie was not set by {PLACEHOLDER_origin} origin in {PLACEHOLDER_destination} context.
-Because this cookie would have been set across schemes on the same site, it was blocked.
-This behavior enhances the `SameSite` attribute’s protection of user data from request forgery by network attackers.
-
-Resolve this issue by migrating your site (as defined by the eTLD+1) entirely to HTTPS.
-It is also recommended to mark the cookie with the `Secure` attribute if that is not already the case.

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

@@ -1,8 +0,0 @@
-# Migrate entirely to HTTPS to have cookies sent on same-site requests
-
-A cookie was not sent to {PLACEHOLDER_destination} origin from {PLACEHOLDER_origin} context on a navigation.
-Because this cookie would have been sent across schemes on the same site, it was not sent.
-This behavior enhances the `SameSite` attribute’s protection of user data from request forgery by network attackers.
-
-Resolve this issue by migrating your site (as defined by the eTLD+1) entirely to HTTPS.
-It is also recommended to mark the cookie with the `Secure` attribute if that is not already the case.

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

@@ -1,8 +0,0 @@
-# Migrate entirely to HTTPS to continue having cookies sent to same-site subresources
-
-A cookie is being sent to {PLACEHOLDER_destination} origin from {PLACEHOLDER_origin} context.
-Because this cookie is being sent across schemes on the same site, it will not be sent in a future version of Chrome.
-This behavior enhances the `SameSite` attribute’s protection of user data from request forgery by network attackers.
-
-Resolve this issue by migrating your site (as defined by the eTLD+1) entirely to HTTPS.
-It is also recommended to mark the cookie with the `Secure` attribute if that is not already the case.

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

@@ -1,8 +0,0 @@
-# Migrate entirely to HTTPS to continue allowing cookies to be set by same-site subresources
-
-A cookie is being set by {PLACEHOLDER_origin} origin in {PLACEHOLDER_destination} context.
-Because this cookie is being set across schemes on the same site, it will be blocked in a future version of Chrome.
-This behavior enhances the `SameSite` attribute’s protection of user data from request forgery by network attackers.
-
-Resolve this issue by migrating your site (as defined by the eTLD+1) entirely to HTTPS.
-It is also recommended to mark the cookie with the `Secure` attribute if that is not already the case.

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

@@ -1,8 +0,0 @@
-# Migrate entirely to HTTPS to continue having cookies sent on same-site requests
-
-A cookie is being sent to {PLACEHOLDER_destination} origin from {PLACEHOLDER_origin} context on a navigation.
-Because this cookie is being sent across schemes on the same site, it will not be sent in a future version of Chrome.
-This behavior enhances the `SameSite` attribute’s protection of user data from request forgery by network attackers.
-
-Resolve this issue by migrating your site (as defined by the eTLD+1) entirely to HTTPS.
-It is also recommended to mark the cookie with the `Secure` attribute if that is not already the case.

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

@@ -1,7 +0,0 @@
-# Ensure that the attribution registration context is secure
-
-This page tried to register a source or trigger using the Attribution Reporting
-API but failed because the page that initiated the registration was not secure.
-
-The registration context must use HTTPS unless it is `localhost` or
-`127.0.0.1`.

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

@@ -1,5 +0,0 @@
-# Ensure that the `Attribution-Reporting-Info` header is valid
-
-This page tried to register a source or trigger using the Attribution Reporting
-API but failed because an `Attribution-Reporting-Info` response header was
-invalid.

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

@@ -1,5 +0,0 @@
-# Ensure that the `Attribution-Reporting-Register-OS-Source` header is valid
-
-This page tried to register an OS source using the Attribution Reporting API
-but failed because an `Attribution-Reporting-Register-OS-Source` response
-header was invalid.

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

@@ -1,5 +0,0 @@
-# Ensure that the `Attribution-Reporting-Register-OS-Trigger` header is valid
-
-This page tried to register an OS trigger using the Attribution Reporting API
-but failed because an `Attribution-Reporting-Register-OS-Trigger` response
-header was invalid.

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

@@ -1,5 +0,0 @@
-# Ensure that the `Attribution-Reporting-Register-Source` header is valid
-
-This page tried to register a source using the Attribution Reporting API but
-failed because an `Attribution-Reporting-Register-Source` response header was
-invalid.

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

@@ -1,5 +0,0 @@
-# Ensure that the `Attribution-Reporting-Register-Trigger` header is valid
-
-This page tried to register a trigger using the Attribution Reporting API but
-failed because an `Attribution-Reporting-Register-Trigger` response header was
-invalid.

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

@@ -1,5 +0,0 @@
-# Ensure that multiple sources associated with the same navigation have the same attribution scopes
-
-The page tried to register a source using Attribution Reporting API, but the
-source was rejected because a previous source associated with the same
-navigation and reporting origin used a different set of attribution scopes.

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

@@ -1,6 +0,0 @@
-# Ensure that navigation-source registrations are initiated by a user gesture
-
-This page tried to register a navigation source using the Attribution Reporting
-API but failed because the navigation was not initiated by a user gesture.
-Compared to event sources, navigation sources can release more cross-site
-information, and are therefore subject to this additional privacy control.

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

@@ -1,5 +0,0 @@
-# OS attribution source expected but corresponding header not found
-
-The page indicated, via the `Attribution-Reporting-Info` header, that it
-intended to register an OS source using the Attribution Reporting API, but the
-corresponding `Attribution-Reporting-Register-OS-Source` header was missing.

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

@@ -1,5 +0,0 @@
-# OS attribution trigger expected but corresponding header not found
-
-The page indicated, via the `Attribution-Reporting-Info` header, that it
-intended to register an OS trigger using the Attribution Reporting API, but the
-corresponding `Attribution-Reporting-Register-OS-Trigger` header was missing.

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

@@ -1,5 +0,0 @@
-# Web attribution source expected but corresponding header not found
-
-The page indicated, via the `Attribution-Reporting-Info` header, that it
-intended to register a web source using the Attribution Reporting API, but the
-corresponding `Attribution-Reporting-Register-Source` header was missing.

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

@@ -1,5 +0,0 @@
-# Web attribution trigger expected but corresponding header not found
-
-The page indicated, via the `Attribution-Reporting-Info` header, that it
-intended to register a web trigger using the Attribution Reporting API, but the
-corresponding `Attribution-Reporting-Register-Trigger` header was missing.

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

@@ -1,4 +0,0 @@
-# No web or OS support for Attribution Reporting
-
-The page tried to send an attributionsrc request, but there was neither web nor
-OS support for the Attribution Reporting API, so the request was skipped.

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

@@ -1,18 +0,0 @@
-# An attribution OS source registration was ignored because the request was ineligible
-
-This page tried to register an OS source using the Attribution Reporting API,
-but the request was ineligible to do so, so the OS source registration was
-ignored.
-
-A request is eligible for OS source registration if it has all of the following:
-
-- An `Attribution-Reporting-Eligible` header whose value is a structured
-  dictionary that contains the key `navigation-source` or `event-source`
-- An `Attribution-Reporting-Support` header whose value is a structured
-  dictionary that contains the key `os`
-
-Otherwise, any `Attribution-Reporting-Register-OS-Source` response header will
-be ignored.
-
-Additionally, a single HTTP redirect chain may register only all sources or all
-triggers, not a combination of both.

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

@@ -1,19 +0,0 @@
-# An attribution OS trigger registration was ignored because the request was ineligible
-
-This page tried to register an OS trigger using the Attribution Reporting API,
-but the request was ineligible to do so, so the OS trigger registration was
-ignored.
-
-A request is eligible for OS trigger registration if it has all of the following:
-
-- No `Attribution-Reporting-Eligible` header or an
-  `Attribution-Reporting-Eligible` header whose value is a structured
-  dictionary that contains the key `trigger`
-- An `Attribution-Reporting-Support` header whose value is a structured
-  dictionary that contains the key `os`
-
-Otherwise, any `Attribution-Reporting-Register-OS-Trigger` response header will
-be ignored.
-
-Additionally, a single HTTP redirect chain may register only all sources or all
-triggers, not a combination of both.

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

@@ -1,8 +0,0 @@
-# The Attribution Reporting API can’t be used because Permissions Policy has been disabled
-
-This page tried to use the Attribution Reporting API but failed because the
-`attribution-reporting` Permission Policy was explicitly disabled.
-
-This API is currently enabled by default for top-level and cross-origin frames,
-but it is still possible for frames to have the permission disabled by their
-parent, e.g. with `<iframe src="…" allow="attribution-reporting 'none'">`.

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

@@ -1,9 +0,0 @@
-# Ensure that attribution responses contain either source or trigger, not both
-
-This page tried to register a source and a trigger in the same HTTP response
-using the Attribution Reporting API, which is prohibited.
-
-The corresponding request was eligible to register either a source or a
-trigger, but the response may only set either the
-`Attribution-Reporting-Register-Source` header or the
-`Attribution-Reporting-Register-Trigger` header, not both.

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

@@ -1,13 +0,0 @@
-# An attribution source registration was ignored because the request was ineligible
-
-This page tried to register a source using the Attribution Reporting API, but
-the request was ineligible to do so, so the source registration was ignored.
-
-A request is eligible for source registration if it has an
-`Attribution-Reporting-Eligible` header whose value is a structured dictionary
-that contains the key `navigation-source` or `event-source`. If the header is
-absent or does not contain one of those keys, any
-`Attribution-Reporting-Register-Source` response header will be ignored.
-
-Additionally, a single HTTP redirect chain may register only all sources or all
-triggers, not a combination of both.

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

@@ -1,12 +0,0 @@
-# An attribution trigger registration was ignored because the request was ineligible
-
-This page tried to register a trigger using the Attribution Reporting API, but
-the request was ineligible to do so, so the trigger registration was ignored.
-
-A request is eligible for trigger registration if it has an
-`Attribution-Reporting-Eligible` header whose value is a structured dictionary
-that contains the key `trigger`, or if the header is absent. Otherwise, any
-`Attribution-Reporting-Register-Trigger` response header will be ignored.
-
-Additionally, a single HTTP redirect chain may register only all sources or all
-triggers, not a combination of both.

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

@@ -1,10 +0,0 @@
-# Ensure that attribution reporting origins are trustworthy
-
-This page tried to register a source or trigger using the Attribution Reporting
-API but failed because the reporting origin was not potentially trustworthy.
-
-The reporting origin is typically the server that sets the
-`Attribution-Reporting-Register-Source` or
-`Attribution-Reporting-Register-Trigger` header.
-
-The reporting origin must use HTTPS unless it is `localhost` or `127.0.0.1`.

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

@@ -1,11 +0,0 @@
-# Ensure that attribution responses contain either web or OS headers, not both
-
-This page included web and OS Attribution Reporting API headers in the same
-HTTP response, which is prohibited.
-
-The response may set at most one of the following headers:
-
-- `Attribution-Reporting-Register-OS-Source`
-- `Attribution-Reporting-Register-OS-Trigger`
-- `Attribution-Reporting-Register-Source`
-- `Attribution-Reporting-Register-Trigger`

package/build/src/utils/string.js

@@ -1,37 +0,0 @@
-/**
- * @license
- * Copyright 2026 Google LLC
- * SPDX-License-Identifier: Apache-2.0
- */
-/**
- * Converts a given string to snake_case.
- * This function handles camelCase, PascalCase, and acronyms, including transitions between letters and numbers.
- * It uses Unicode-aware regular expressions (`\p{L}`, `\p{N}`, `\p{Lu}`, `\p{Ll}` with the `u` flag)
- * to correctly process letters and numbers from various languages.
- *
- * @param text The input string to convert to snake_case.
- * @returns The snake_case version of the input string.
- */
-export function toSnakeCase(text) {
-    if (!text) {
-        return '';
-    }
-    // First, handle case-based transformations to insert underscores correctly.
-    // 1. Add underscore between a letter and a number.
-    //    e.g., "version2" -> "version_2"
-    // 2. Add underscore between an uppercase letter sequence and a following uppercase+lowercase sequence.
-    //    e.g., "APIFlags" -> "API_Flags"
-    // 3. Add underscore between a lowercase/number and an uppercase letter.
-    //    e.g., "lastName" -> "last_Name", "version_2Update" -> "version_2_Update"
-    // 4. Replace sequences of non-alphanumeric with a single underscore
-    // 5. Remove any leading or trailing underscores.
-    const result = text
-        .replace(/(\p{L})(\p{N})/gu, '$1_$2') // 1
-        .replace(/(\p{Lu}+)(\p{Lu}\p{Ll})/gu, '$1_$2') // 2
-        .replace(/(\p{Ll}|\p{N})(\p{Lu})/gu, '$1_$2') // 3
-        .toLowerCase()
-        .replace(/[^\p{L}\p{N}]+/gu, '_') // 4
-        .replace(/^_|_$/g, ''); // 5
-    return result;
-}
-//# sourceMappingURL=string.js.map

package/build/src/utils/types.js

@@ -1,7 +0,0 @@
-/**
- * @license
- * Copyright 2025 Google LLC
- * SPDX-License-Identifier: Apache-2.0
- */
-export {};
-//# sourceMappingURL=types.js.map