| Simon Zünd | 2ce6754 | 2023-02-07 10:15:14 | [diff] [blame] | 1 | // Copyright 2023 The Chromium Authors. All rights reserved. |
| 2 | // Use of this source code is governed by a BSD-style license that can be |
| 3 | // found in the LICENSE file. |
| 4 | |
| 5 | // This file is auto-generated, do not edit manually. |
| 6 | // Re-generate with: npm run generate-protocol-resources |
| 7 | |
| Simon Zünd | 2ce6754 | 2023-02-07 10:15:14 | [diff] [blame] | 8 | export const UIStrings = { |
| 9 | /** |
| 10 | * @description We show this warning when 1) an 'authorization' header is attached to the request by scripts, 2) there is no 'authorization' in the 'access-control-allow-headers' header in the response, and 3) there is a wildcard symbol ('*') in the 'access-control-allow-header' header in the response. This is allowed now, but we're planning to reject such responses and require responses to have an 'access-control-allow-headers' containing 'authorization'. |
| 11 | */ |
| 12 | AuthorizationCoveredByWildcard: 'Authorization will not be covered by the wildcard symbol (*) in CORS `Access-Control-Allow-Headers` handling.', |
| 13 | /** |
| 14 | * @description This warning occurs when a page attempts to request a resource whose URL contained both a newline character (`\n` or `\r`), and a less-than character (`<`). These resources are blocked. |
| 15 | */ |
| Ari Chivukula | 52c774a | 2023-02-10 18:14:09 | [diff] [blame] | 16 | CanRequestURLHTTPContainingNewline: 'Resource requests whose URLs contained both removed whitespace `\\(n|r|t)` characters and less-than characters (`<`) are blocked. Please remove newlines and encode less-than characters from places like element attribute values in order to load these resources.', |
| Simon Zünd | 2ce6754 | 2023-02-07 10:15:14 | [diff] [blame] | 17 | /** |
| 18 | * @description This warning occurs when the website attempts to invoke the deprecated `chrome.loadTimes().connectionInfo` API. |
| 19 | */ |
| 20 | ChromeLoadTimesConnectionInfo: '`chrome.loadTimes()` is deprecated, instead use standardized API: Navigation Timing 2.', |
| 21 | /** |
| 22 | * @description This warning occurs when the website attempts to invoke the deprecated `chrome.loadTimes().firstPaintAfterLoadTime` API. |
| 23 | */ |
| 24 | ChromeLoadTimesFirstPaintAfterLoadTime: '`chrome.loadTimes()` is deprecated, instead use standardized API: Paint Timing.', |
| 25 | /** |
| 26 | * @description This warning occurs when the website attempts to invoke the deprecated `chrome.loadTimes().wasAlternateProtocolAvailable` API. |
| 27 | */ |
| 28 | ChromeLoadTimesWasAlternateProtocolAvailable: '`chrome.loadTimes()` is deprecated, instead use standardized API: `nextHopProtocol` in Navigation Timing 2.', |
| 29 | /** |
| 30 | * @description This warning occurs when the browser attempts to store a cookie containing a banned character. Rather than the cookie string being truncated at the banned character, the entire cookie will be rejected now. |
| 31 | */ |
| Ari Chivukula | 52c774a | 2023-02-10 18:14:09 | [diff] [blame] | 32 | CookieWithTruncatingChar: 'Cookies containing a `\\(0|r|n)` character will be rejected instead of truncated.', |
| Simon Zünd | 2ce6754 | 2023-02-07 10:15:14 | [diff] [blame] | 33 | /** |
| 34 | * @description This warning occurs when a frame accesses another frame's data after having set `document.domain` without having set the `Origin-Agent-Cluster` http header. This is a companion warning to `documentDomainSettingWithoutOriginAgentClusterHeader`, where that warning occurs when `document.domain` is set, and this warning occurs when an access has been made, based on that previous `document.domain` setting. |
| 35 | */ |
| 36 | CrossOriginAccessBasedOnDocumentDomain: 'Relaxing the same-origin policy by setting `document.domain` is deprecated, and will be disabled by default. This deprecation warning is for a cross-origin access that was enabled by setting `document.domain`.', |
| 37 | /** |
| 38 | * @description Issue text shown when the web page uses a deprecated web API. The window.alert is the deprecated web API function. |
| 39 | */ |
| 40 | CrossOriginWindowAlert: 'Triggering window.alert from cross origin iframes has been deprecated and will be removed in the future.', |
| 41 | /** |
| 42 | * @description Issue text shown when the web page uses a deprecated web API. The window.confirm is the deprecated web API function. |
| 43 | */ |
| 44 | CrossOriginWindowConfirm: 'Triggering window.confirm from cross origin iframes has been deprecated and will be removed in the future.', |
| 45 | /** |
| 46 | * @description Warning displayed to developers when they hide the Cast button on a video element using the deprecated CSS selector instead of using the disableRemotePlayback attribute on the element. |
| 47 | */ |
| 48 | CSSSelectorInternalMediaControlsOverlayCastButton: 'The `disableRemotePlayback` attribute should be used in order to disable the default Cast integration instead of using `-internal-media-controls-overlay-cast-button` selector.', |
| 49 | /** |
| 50 | * @description This warning occurs when a script modifies `document.domain` without having set on `Origin-Agent-Cluster` http header. In other words, when a script relies on the default behaviour of `Origin-Agent-Cluster` when setting document.domain. |
| 51 | */ |
| 52 | DocumentDomainSettingWithoutOriginAgentClusterHeader: 'Relaxing the same-origin policy by setting `document.domain` is deprecated, and will be disabled by default. To continue using this feature, please opt-out of origin-keyed agent clusters by sending an `Origin-Agent-Cluster: ?0` header along with the HTTP response for the document and frames. See https://developer.chrome.com/blog/immutable-document-domain/ for more details.', |
| 53 | /** |
| 54 | * @description Warning displayed to developers when the non-standard `Event.path` API is used to notify them that this API is deprecated. |
| 55 | */ |
| 56 | EventPath: '`Event.path` is deprecated and will be removed. Please use `Event.composedPath()` instead.', |
| 57 | /** |
| 58 | * @description This message is shown when the deprecated Expect-CT header is present. |
| 59 | */ |
| 60 | ExpectCTHeader: 'The `Expect-CT` header is deprecated and will be removed. Chrome requires Certificate Transparency for all publicly trusted certificates issued after April 30, 2018.', |
| 61 | /** |
| 62 | * @description Warning displayed to developers when the Geolocation API is used from an insecure origin (one that isn't localhost or doesn't use HTTPS) to notify them that this use is no longer supported. |
| 63 | */ |
| 64 | GeolocationInsecureOrigin: '`getCurrentPosition()` and `watchPosition()` no longer work on insecure origins. To use this feature, you should consider switching your application to a secure origin, such as HTTPS. See https://goo.gle/chrome-insecure-origins for more details.', |
| 65 | /** |
| 66 | * @description Warning displayed to developers when the Geolocation API is used from an insecure origin (one that isn't localhost or doesn't use HTTPS) to notify them that this use is deprecated. |
| 67 | */ |
| 68 | GeolocationInsecureOriginDeprecatedNotRemoved: '`getCurrentPosition()` and `watchPosition()` are deprecated on insecure origins. To use this feature, you should consider switching your application to a secure origin, such as HTTPS. See https://goo.gle/chrome-insecure-origins for more details.', |
| 69 | /** |
| 70 | * @description This warning occurs when the `getUserMedia()` API is invoked on an insecure (e.g., HTTP) site. This is only permitted on secure sites (e.g., HTTPS). |
| 71 | */ |
| 72 | GetUserMediaInsecureOrigin: '`getUserMedia()` no longer works on insecure origins. To use this feature, you should consider switching your application to a secure origin, such as HTTPS. See https://goo.gle/chrome-insecure-origins for more details.', |
| 73 | /** |
| 74 | * @description A deprecation warning shown to developers in the DevTools Issues tab when code tries to use the deprecated hostCandidate field, guiding developers to use the the equivalent information in the .address and .port fields instead. |
| 75 | */ |
| 76 | HostCandidateAttributeGetter: '`RTCPeerConnectionIceErrorEvent.hostCandidate` is deprecated. Please use `RTCPeerConnectionIceErrorEvent.address` or `RTCPeerConnectionIceErrorEvent.port` instead.', |
| 77 | /** |
| 78 | * @description A deprecation warning shown in the DevTools Issues tab, when a service worker reads one of the fields from an event named 'canmakepayment'. |
| 79 | */ |
| 80 | IdentityInCanMakePaymentEvent: 'The merchant origin and arbitrary data from the `canmakepayment` service worker event are deprecated and will be removed: `topOrigin`, `paymentRequestOrigin`, `methodData`, `modifiers`.', |
| 81 | /** |
| 82 | * @description This warning occurs when an insecure context (e.g., HTTP) requests a private resource (not on open internet). This is done to mitigate the potential for CSRF and other attacks. |
| 83 | */ |
| 84 | InsecurePrivateNetworkSubresourceRequest: 'The website requested a subresource from a network that it could only access because of its users\' privileged network position. These requests expose non-public devices and servers to the internet, increasing the risk of a cross-site request forgery (CSRF) attack, and/or information leakage. To mitigate these risks, Chrome deprecates requests to non-public subresources when initiated from non-secure contexts, and will start blocking them.', |
| 85 | /** |
| 86 | * @description This warning occurs when a stylesheet loaded from a local file directive does not end in the file type `.css`. |
| 87 | */ |
| 88 | LocalCSSFileExtensionRejected: 'CSS cannot be loaded from `file:` URLs unless they end in a `.css` file extension.', |
| 89 | /** |
| 90 | * @description This is a deprecation warning to developers that occurs when the script attempts to use the Media Source Extensions API in a way that is no longer supported by the specification for the API. The usage that is problematic is when the script calls the `SourceBuffer.abort()` method at a time when there is still processing happening in response to a previous `SourceBuffer.remove()` call for the same SourceBuffer object. More precisely, we show this warning to developers when script calls the SourceBuffer abort() method while the asynchronous processing of a remove() call on that SourceBuffer is not yet complete. Early versions of the Media Source Extensions specification allowed such aborts, but standardization of the specification resulted in disallowing the aborts. The script should instead wait for the asynchronous remove() operation to complete, which is observable by listening for the associated 'updateend' event from the SourceBuffer. A note is also included in the warning, describing when abort() is meaningful and allowed by the specification for purposes other than interrupting a remove() operation's asynchronous steps. Those supported purposes include using abort() to interrupt processing that may still be happening in response to a previous appendBuffer() call on that SourceBuffer, or using abort() to clear the internal of any unprocessed data remaining from previous appendBuffer() calls. See https://www.w3.org/TR/media-source-2/#dom-sourcebuffer-abort for the currently specified behavior, which would throw an exception once the deprecated removal abort is no longer supported. See https://github.com/w3c/media-source/issues/19 for the discussion that led to the specification change. |
| 91 | */ |
| 92 | MediaSourceAbortRemove: 'Using `SourceBuffer.abort()` to abort `remove()`\'s asynchronous range removal is deprecated due to specification change. Support will be removed in the future. You should listen to the `updateend` event instead. `abort()` is intended to only abort an asynchronous media append or reset parser state.', |
| 93 | /** |
| 94 | * @description This is a deprecation warning to developers that occurs when the script attempts to use the Media Source Extensions API in a way that is no longer supported by the specification for the API. The usage that is problematic is when the script sets the duration attribute of a MediaSource object too low. The duration attribute of a MediaSource must be longer than the actual duration of any media (audio or video) already in the MediaSource. When set too low, the MediaSource must remove audio and video content that is beyond the time indicated by the new duration. Content removal that is caused by setting the duration attribute too low is no longer allowed by the specification. The message describes the minimum allowable duration value as the 'highest presentation timestamp of any buffered coded frames' as a more precise way of describing the duration of content already in the MediaSource: 'coded frames' are the specification's way of describing compressed audio frames or compressed video frames, and they each have a 'presentation timestamp' that describes precisely when that frame's playback occurs in the overall media presentation. Early versions of the Media Source Extensions specification allowed this to happen, but standardization of the specification resulted in disallowing this behavior. The underlying issue leading to this specification change was that setting the duration attribute should be synchronous, but setting it lower than the timestamp of something currently buffered would cause confusing removal of media between that new duration and the previous, larger, duration. The script should instead explicitly remove that range of media first, before lowering the duration. See https://www.w3.org/TR/media-source-2/#dom-mediasource-duration and https://www.w3.org/TR/media-source-2/#dom-mediasource-duration for the currently specified behavior, which would throw an exception once support is removed for deprecated implicit asynchronous range removal when duration is truncated. See both https://github.com/w3c/media-source/issues/20 and https://github.com/w3c/media-source/issues/26 for the discussion that led to the specification change. |
| 95 | */ |
| 96 | MediaSourceDurationTruncatingBuffered: 'Setting `MediaSource.duration` below the highest presentation timestamp of any buffered coded frames is deprecated due to specification change. Support for implicit removal of truncated buffered media will be removed in the future. You should instead perform explicit `remove(newDuration, oldDuration)` on all `sourceBuffers`, where `newDuration < oldDuration`.', |
| 97 | /** |
| Mason Freed | 0cd010d | 2023-02-14 00:17:39 | [diff] [blame] | 98 | * @description This warning is displayed when a site contains a `<template>` element with the `shadowroot` attribute. |
| 99 | */ |
| Mason Freed | 3492750 | 2023-03-06 19:15:13 | [diff] [blame] | 100 | NonStandardDeclarativeShadowDOM: 'The older, non-standardized `shadowroot` attribute is deprecated, and will *no longer function* in M119. Please use the new, standardized `shadowrootmode` attribute instead.', |
| Mason Freed | 0cd010d | 2023-02-14 00:17:39 | [diff] [blame] | 101 | /** |
| Simon Zünd | 2ce6754 | 2023-02-07 10:15:14 | [diff] [blame] | 102 | * @description This warning occurs when the browser requests Web MIDI access as sysex (system exclusive messages) can be allowed via prompt even if the browser did not specifically request it. |
| 103 | */ |
| 104 | NoSysexWebMIDIWithoutPermission: 'Web MIDI will ask a permission to use even if the sysex is not specified in the `MIDIOptions`.', |
| 105 | /** |
| 106 | * @description Warning displayed to developers when the Notification API is used from an insecure origin (one that isn't localhost or doesn't use HTTPS) to notify them that this use is no longer supported. |
| 107 | */ |
| 108 | NotificationInsecureOrigin: 'The Notification API may no longer be used from insecure origins. You should consider switching your application to a secure origin, such as HTTPS. See https://goo.gle/chrome-insecure-origins for more details.', |
| 109 | /** |
| 110 | * @description Warning displayed to developers when permission to use notifications has been requested by a cross-origin iframe, to notify them that this use is no longer supported. |
| 111 | */ |
| 112 | NotificationPermissionRequestedIframe: 'Permission for the Notification API may no longer be requested from a cross-origin iframe. You should consider requesting permission from a top-level frame or opening a new window instead.', |
| 113 | /** |
| 114 | * @description Warning displayed to developers when CreateImageBitmap is used with the newly deprecated option imageOrientation: 'none'. |
| 115 | */ |
| 116 | ObsoleteCreateImageBitmapImageOrientationNone: 'Option `imageOrientation: \'none\'` in createImageBitmap is deprecated. Please use createImageBitmap with option {imageOrientation: \'from-image\'} instead.', |
| 117 | /** |
| 118 | * @description This warning occurs when the WebRTC protocol attempts to negotiate a connection using an obsolete cipher and risks connection security. |
| 119 | */ |
| 120 | ObsoleteWebRtcCipherSuite: 'Your partner is negotiating an obsolete (D)TLS version. Please check with your partner to have this fixed.', |
| 121 | /** |
| 122 | * @description Warning displayed to developers that use overflow:visible for replaced elements. This declaration was earlier ignored but will now change the element's painting based on whether the overflow value allows the element to paint outside its bounds. |
| 123 | */ |
| 124 | OverflowVisibleOnReplacedElement: 'Specifying `overflow: visible` on img, video and canvas tags may cause them to produce visual content outside of the element bounds. See https://github.com/WICG/shared-element-transitions/blob/main/debugging_overflow_on_images.md.', |
| 125 | /** |
| 126 | * @description Warning displayed to developers when they use the PaymentInstruments API to let them know this API is deprecated. |
| 127 | */ |
| 128 | PaymentInstruments: '`paymentManager.instruments` is deprecated. Please use just-in-time install for payment handlers instead.', |
| 129 | /** |
| 130 | * @description Warning displayed to developers when their Web Payment API usage violates their Content-Security-Policy (CSP) connect-src directive to let them know this CSP bypass has been deprecated. |
| 131 | */ |
| 132 | PaymentRequestCSPViolation: 'Your `PaymentRequest` call bypassed Content-Security-Policy (CSP) `connect-src` directive. This bypass is deprecated. Please add the payment method identifier from the `PaymentRequest` API (in `supportedMethods` field) to your CSP `connect-src` directive.', |
| 133 | /** |
| 134 | * @description Warning displayed to developers when persistent storage type is used to notify that storage type is deprecated. |
| 135 | */ |
| 136 | PersistentQuotaType: '`StorageType.persistent` is deprecated. Please use standardized `navigator.storage` instead.', |
| 137 | /** |
| 138 | * @description This issue indicates that a `<source>` element with a `<picture>` parent was using an `src` attribute, which is not valid and is ignored by the browser. The `srcset` attribute should be used instead. |
| 139 | */ |
| 140 | PictureSourceSrc: '`<source src>` with a `<picture>` parent is invalid and therefore ignored. Please use `<source srcset>` instead.', |
| 141 | /** |
| 142 | * @description Warning displayed to developers when the vendor-prefixed method (webkitCancelAnimationFrame) is used rather than the equivalent unprefixed method (cancelAnimationFrame). |
| 143 | */ |
| 144 | PrefixedCancelAnimationFrame: 'webkitCancelAnimationFrame is vendor-specific. Please use the standard cancelAnimationFrame instead.', |
| 145 | /** |
| 146 | * @description Warning displayed to developers when the vendor-prefixed method (webkitRequestAnimationFrame) is used rather than the equivalent unprefixed method (requestAnimationFrame). |
| 147 | */ |
| 148 | PrefixedRequestAnimationFrame: 'webkitRequestAnimationFrame is vendor-specific. Please use the standard requestAnimationFrame instead.', |
| 149 | /** |
| Simon Zünd | 2ce6754 | 2023-02-07 10:15:14 | [diff] [blame] | 150 | * @description Standard message when one web API is deprecated in favor of another. |
| 151 | */ |
| 152 | PrefixedVideoDisplayingFullscreen: 'HTMLVideoElement.webkitDisplayingFullscreen is deprecated. Please use Document.fullscreenElement instead.', |
| 153 | /** |
| 154 | * @description Standard message when one web API is deprecated in favor of another. |
| 155 | */ |
| 156 | PrefixedVideoEnterFullScreen: 'HTMLVideoElement.webkitEnterFullScreen() is deprecated. Please use Element.requestFullscreen() instead.', |
| 157 | /** |
| 158 | * @description Standard message when one web API is deprecated in favor of another. |
| 159 | */ |
| 160 | PrefixedVideoEnterFullscreen: 'HTMLVideoElement.webkitEnterFullscreen() is deprecated. Please use Element.requestFullscreen() instead.', |
| 161 | /** |
| 162 | * @description Standard message when one web API is deprecated in favor of another. |
| 163 | */ |
| 164 | PrefixedVideoExitFullScreen: 'HTMLVideoElement.webkitExitFullScreen() is deprecated. Please use Document.exitFullscreen() instead.', |
| 165 | /** |
| 166 | * @description Standard message when one web API is deprecated in favor of another. |
| 167 | */ |
| 168 | PrefixedVideoExitFullscreen: 'HTMLVideoElement.webkitExitFullscreen() is deprecated. Please use Document.exitFullscreen() instead.', |
| 169 | /** |
| 170 | * @description Standard message when one web API is deprecated in favor of another. |
| 171 | */ |
| 172 | PrefixedVideoSupportsFullscreen: 'HTMLVideoElement.webkitSupportsFullscreen is deprecated. Please use Document.fullscreenEnabled instead.', |
| 173 | /** |
| Ari Chivukula | 6b47192 | 2023-02-08 17:21:27 | [diff] [blame] | 174 | * @description Warning displayed to developers that the API `chrome.privacy.websites.privacySandboxEnabled` is being deprecated in favour of three new more granular APIs: topicsEnabled, FledgeEnabled and adMeasurementEnabled. The `privacySandboxEnabled` API allowed extensions to control the homologous Chrome Setting. The existing Chrome Setting for Privacy Sandbox is also going away in favor of more granular settings that are matched by the new extensions APIs- topicsEnabled, FledgeEnabled and adMeasurementEnabled. |
| 175 | */ |
| Mason Freed | 0cd010d | 2023-02-14 00:17:39 | [diff] [blame] | 176 | PrivacySandboxExtensionsAPI: 'We\'re deprecating the API `chrome.privacy.websites.privacySandboxEnabled`, though it will remain active for backward compatibility until release M113. Instead, please use `chrome.privacy.websites.topicsEnabled`, `chrome.privacy.websites.fledgeEnabled` and `chrome.privacy.websites.adMeasurementEnabled`. See https://developer.chrome.com/docs/extensions/reference/privacy/#property-websites-privacySandboxEnabled.', |
| Ari Chivukula | 6b47192 | 2023-02-08 17:21:27 | [diff] [blame] | 177 | /** |
| Simon Zünd | 2ce6754 | 2023-02-07 10:15:14 | [diff] [blame] | 178 | * @description Standard message when one web API is deprecated in favor of another. |
| 179 | */ |
| 180 | RangeExpand: 'Range.expand() is deprecated. Please use Selection.modify() instead.', |
| 181 | /** |
| 182 | * @description This warning occurs when a subresource loaded by a page has a URL with an authority portion. These are disallowed. |
| 183 | */ |
| 184 | RequestedSubresourceWithEmbeddedCredentials: 'Subresource requests whose URLs contain embedded credentials (e.g. `https://user:pass@host/`) are blocked.', |
| 185 | /** |
| 186 | * @description A deprecation warning shown in the DevTools Issues tab. It's shown when a video conferencing website attempts to use a non-standard crypto method when performing a handshake to set up a connection with another endpoint. |
| 187 | */ |
| 188 | RTCConstraintEnableDtlsSrtpFalse: 'The constraint `DtlsSrtpKeyAgreement` is removed. You have specified a `false` value for this constraint, which is interpreted as an attempt to use the removed `SDES key negotiation` method. This functionality is removed; use a service that supports `DTLS key negotiation` instead.', |
| 189 | /** |
| 190 | * @description A deprecation warning shown in the DevTools Issues tab. It's shown when a video conferencing website uses a non-standard API for controlling the crypto method used, but is not having an effect because the desired behavior is already enabled-by-default. |
| 191 | */ |
| 192 | RTCConstraintEnableDtlsSrtpTrue: 'The constraint `DtlsSrtpKeyAgreement` is removed. You have specified a `true` value for this constraint, which had no effect, but you can remove this constraint for tidiness.', |
| 193 | /** |
| Henrik Boström | f5ad49e | 2023-02-27 08:59:15 | [diff] [blame] | 194 | * @description WebRTC is set of JavaScript APIs for sending and receiving data, audio and video. getStats() is a method used to obtain network and quality metrics. There are two versions of this method, one is being deprecated because it is non-standard. |
| 195 | */ |
| 196 | RTCPeerConnectionGetStatsLegacyNonCompliant: 'The callback-based getStats() is deprecated and will be removed. Use the spec-compliant getStats() instead.', |
| 197 | /** |
| Simon Zünd | 2ce6754 | 2023-02-07 10:15:14 | [diff] [blame] | 198 | * @description A deprecation warning shown in the DevTools Issues tab. It's shown then a video conferencing website attempts to use the `RTCP MUX` policy. |
| 199 | */ |
| 200 | RtcpMuxPolicyNegotiate: 'The `rtcpMuxPolicy` option is deprecated and will be removed.', |
| 201 | /** |
| 202 | * @description A deprecation warning shown in the DevTools Issues tab. The placeholder is always the noun 'SharedArrayBuffer' which refers to a JavaScript construct. |
| 203 | */ |
| 204 | SharedArrayBufferConstructedWithoutIsolation: '`SharedArrayBuffer` will require cross-origin isolation. See https://developer.chrome.com/blog/enabling-shared-array-buffer/ for more details.', |
| 205 | /** |
| 206 | * @description A deprecation warning shown in the DevTools Issues tab. It's shown when the speech synthesis API is called before the page receives a user activation. |
| 207 | */ |
| 208 | TextToSpeech_DisallowedByAutoplay: '`speechSynthesis.speak()` without user activation is deprecated and will be removed.', |
| 209 | /** |
| 210 | * @description A deprecation warning shown in the DevTools Issues tab. The placeholder is always the noun 'SharedArrayBuffer' which refers to a JavaScript construct. 'Extensions' refers to Chrome extensions. The warning is shown when Chrome Extensions attempt to use 'SharedArrayBuffer's under insecure circumstances. |
| 211 | */ |
| 212 | V8SharedArrayBufferConstructedInExtensionWithoutIsolation: 'Extensions should opt into cross-origin isolation to continue using `SharedArrayBuffer`. See https://developer.chrome.com/docs/extensions/mv3/cross-origin-isolation/.', |
| 213 | /** |
| Mason Freed | 3492750 | 2023-03-06 19:15:13 | [diff] [blame] | 214 | * @description A deprecation warning shown in the DevTools Issues tab. 'window-placement' and 'window-management' are the name of the javascript descriptors (do not translate). The warning is shown when web pages attempt to use 'window-placement' in permission APIs (e.g. navigator.permissions.query(...)) |
| 215 | */ |
| 216 | WindowPlacementPermissionDescriptorUsed: 'The permission descriptor `window-placement` is deprecated. Use `window-management` instead. For more help, check https://bit.ly/window-placement-rename.', |
| 217 | /** |
| 218 | * @description A deprecation warning shown in the DevTools Issues tab. 'window-placement' and 'window-management' are the name of the policy descriptors (do not translate). The warning is shown when web pages attempt to use 'window-placement' as a permission policy (parsed in iframe or header). |
| 219 | */ |
| 220 | WindowPlacementPermissionPolicyParsed: 'The permission policy `window-placement` is deprecated. Use `window-management` instead. For more help, check https://bit.ly/window-placement-rename.', |
| 221 | /** |
| Simon Zünd | 2ce6754 | 2023-02-07 10:15:14 | [diff] [blame] | 222 | * @description Warning displayed to developers that they are using `XMLHttpRequest` API in a way that they expect an unsupported character encoding `UTF-16` could be used in the server reply. |
| 223 | */ |
| 224 | XHRJSONEncodingDetection: 'UTF-16 is not supported by response json in `XMLHttpRequest`', |
| 225 | /** |
| 226 | * @description Warning displayed to developers. It is shown when the `XMLHttpRequest` API is used in a way that it slows down the page load of the next page. The `main thread` refers to an operating systems thread used to run most of the processing of HTML documents, so please use a consistent wording. |
| 227 | */ |
| Ari Chivukula | 52c774a | 2023-02-10 18:14:09 | [diff] [blame] | 228 | XMLHttpRequestSynchronousInNonWorkerOutsideBeforeUnload: 'Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to the end user\'s experience. For more help, check https://xhr.spec.whatwg.org/.', |
| Simon Zünd | 2ce6754 | 2023-02-07 10:15:14 | [diff] [blame] | 229 | /** |
| 230 | * @description Warning displayed to developers that instead of using `supportsSession()`, which returns a promise that resolves if the XR session can be supported and rejects if not, they should use `isSessionSupported()` which will return a promise which resolves to a boolean indicating if the XR session can be supported or not, but may reject to throw an exception. |
| 231 | */ |
| 232 | XRSupportsSession: '`supportsSession()` is deprecated. Please use `isSessionSupported()` and check the resolved boolean value instead.', |
| 233 | }; |
| 234 | |
| 235 | export interface DeprecationDescriptor { |
| 236 | milestone?: number; |
| 237 | chromeStatusFeature?: number; |
| 238 | } |
| 239 | |
| Ari Chivukula | 6b47192 | 2023-02-08 17:21:27 | [diff] [blame] | 240 | export const DEPRECATIONS_METADATA: Partial<Record<string, DeprecationDescriptor>> = { |
| Simon Zünd | 2ce6754 | 2023-02-07 10:15:14 | [diff] [blame] | 241 | "AuthorizationCoveredByWildcard": { |
| 242 | "milestone": 97 |
| 243 | }, |
| 244 | "CSSSelectorInternalMediaControlsOverlayCastButton": { |
| 245 | "chromeStatusFeature": 5714245488476160 |
| 246 | }, |
| 247 | "CanRequestURLHTTPContainingNewline": { |
| 248 | "chromeStatusFeature": 5735596811091968 |
| 249 | }, |
| 250 | "ChromeLoadTimesConnectionInfo": { |
| 251 | "chromeStatusFeature": 5637885046816768 |
| 252 | }, |
| 253 | "ChromeLoadTimesFirstPaintAfterLoadTime": { |
| 254 | "chromeStatusFeature": 5637885046816768 |
| 255 | }, |
| 256 | "ChromeLoadTimesWasAlternateProtocolAvailable": { |
| 257 | "chromeStatusFeature": 5637885046816768 |
| 258 | }, |
| 259 | "CookieWithTruncatingChar": { |
| 260 | "milestone": 103 |
| 261 | }, |
| 262 | "CrossOriginAccessBasedOnDocumentDomain": { |
| 263 | "milestone": 109 |
| 264 | }, |
| 265 | "DocumentDomainSettingWithoutOriginAgentClusterHeader": { |
| 266 | "milestone": 109 |
| 267 | }, |
| 268 | "EventPath": { |
| 269 | "chromeStatusFeature": 5726124632965120, |
| 270 | "milestone": 109 |
| 271 | }, |
| 272 | "ExpectCTHeader": { |
| 273 | "chromeStatusFeature": 6244547273687040, |
| 274 | "milestone": 107 |
| 275 | }, |
| 276 | "IdentityInCanMakePaymentEvent": { |
| 277 | "chromeStatusFeature": 5190978431352832 |
| 278 | }, |
| 279 | "InsecurePrivateNetworkSubresourceRequest": { |
| 280 | "chromeStatusFeature": 5436853517811712, |
| 281 | "milestone": 92 |
| 282 | }, |
| 283 | "LocalCSSFileExtensionRejected": { |
| 284 | "milestone": 64 |
| 285 | }, |
| 286 | "MediaSourceAbortRemove": { |
| 287 | "chromeStatusFeature": 6107495151960064 |
| 288 | }, |
| 289 | "MediaSourceDurationTruncatingBuffered": { |
| 290 | "chromeStatusFeature": 6107495151960064 |
| 291 | }, |
| 292 | "NoSysexWebMIDIWithoutPermission": { |
| 293 | "chromeStatusFeature": 5138066234671104, |
| 294 | "milestone": 82 |
| 295 | }, |
| Mason Freed | 0cd010d | 2023-02-14 00:17:39 | [diff] [blame] | 296 | "NonStandardDeclarativeShadowDOM": { |
| 297 | "chromeStatusFeature": 6239658726391808, |
| Mason Freed | 3492750 | 2023-03-06 19:15:13 | [diff] [blame] | 298 | "milestone": 119 |
| Mason Freed | 0cd010d | 2023-02-14 00:17:39 | [diff] [blame] | 299 | }, |
| Simon Zünd | 2ce6754 | 2023-02-07 10:15:14 | [diff] [blame] | 300 | "NotificationPermissionRequestedIframe": { |
| 301 | "chromeStatusFeature": 6451284559265792 |
| 302 | }, |
| 303 | "ObsoleteCreateImageBitmapImageOrientationNone": { |
| 304 | "milestone": 111 |
| 305 | }, |
| 306 | "ObsoleteWebRtcCipherSuite": { |
| 307 | "milestone": 81 |
| 308 | }, |
| 309 | "OverflowVisibleOnReplacedElement": { |
| 310 | "chromeStatusFeature": 5137515594383360, |
| 311 | "milestone": 108 |
| 312 | }, |
| 313 | "PaymentInstruments": { |
| 314 | "chromeStatusFeature": 5099285054488576 |
| 315 | }, |
| 316 | "PaymentRequestCSPViolation": { |
| 317 | "chromeStatusFeature": 6286595631087616 |
| 318 | }, |
| 319 | "PersistentQuotaType": { |
| 320 | "chromeStatusFeature": 5176235376246784, |
| 321 | "milestone": 106 |
| 322 | }, |
| 323 | "RTCConstraintEnableDtlsSrtpFalse": { |
| 324 | "milestone": 97 |
| 325 | }, |
| 326 | "RTCConstraintEnableDtlsSrtpTrue": { |
| 327 | "milestone": 97 |
| 328 | }, |
| Henrik Boström | f5ad49e | 2023-02-27 08:59:15 | [diff] [blame] | 329 | "RTCPeerConnectionGetStatsLegacyNonCompliant": { |
| 330 | "chromeStatusFeature": 4631626228695040, |
| 331 | "milestone": 117 |
| 332 | }, |
| Simon Zünd | 2ce6754 | 2023-02-07 10:15:14 | [diff] [blame] | 333 | "RequestedSubresourceWithEmbeddedCredentials": { |
| 334 | "chromeStatusFeature": 5669008342777856 |
| 335 | }, |
| 336 | "RtcpMuxPolicyNegotiate": { |
| 337 | "chromeStatusFeature": 5654810086866944, |
| 338 | "milestone": 62 |
| 339 | }, |
| 340 | "SharedArrayBufferConstructedWithoutIsolation": { |
| 341 | "milestone": 106 |
| 342 | }, |
| 343 | "TextToSpeech_DisallowedByAutoplay": { |
| 344 | "chromeStatusFeature": 5687444770914304, |
| 345 | "milestone": 71 |
| 346 | }, |
| 347 | "V8SharedArrayBufferConstructedInExtensionWithoutIsolation": { |
| 348 | "milestone": 96 |
| 349 | }, |
| Mason Freed | 3492750 | 2023-03-06 19:15:13 | [diff] [blame] | 350 | "WindowPlacementPermissionDescriptorUsed": { |
| 351 | "chromeStatusFeature": 5137018030391296, |
| 352 | "milestone": 112 |
| 353 | }, |
| 354 | "WindowPlacementPermissionPolicyParsed": { |
| 355 | "chromeStatusFeature": 5137018030391296, |
| 356 | "milestone": 112 |
| 357 | }, |
| Simon Zünd | 2ce6754 | 2023-02-07 10:15:14 | [diff] [blame] | 358 | "XHRJSONEncodingDetection": { |
| 359 | "milestone": 93 |
| 360 | }, |
| 361 | "XRSupportsSession": { |
| 362 | "milestone": 80 |
| 363 | } |
| 364 | }; |