diff --git a/.remarkrc.js b/.remarkrc.js index d433a877342b..7b7d7dabdd34 100644 --- a/.remarkrc.js +++ b/.remarkrc.js @@ -46,4 +46,5 @@ exports.plugins = [ // Custom plugins. require('./tools/linting/no-unescaped-template-tags.js'), + require('./tools/linting/bad-urls.js'), ]; diff --git a/site/en/blog/_example/index.md b/site/en/blog/_example/index.md index 889e55cb27b2..2e6b81c6116c 100644 --- a/site/en/blog/_example/index.md +++ b/site/en/blog/_example/index.md @@ -60,8 +60,8 @@ A few rules: - Make sure all of your images have `alt` text unless they are purely decorative. - Make sure authors appear in the `authorsData.json` file and that they have - uploaded a headshot to our image CDN. See [How to add an author](https://developer.chrome.com/docs/handbook/how-to/add-an-author/). -- Make sure tags have been added to `tags.yml`. See [How to add a tag](https://developer.chrome.com/docs/handbook/how-to/add-a-tag/). + uploaded a headshot to our image CDN. See [How to add an author](/docs/handbook/how-to/add-an-author/). +- Make sure tags have been added to `tags.yml`. See [How to add a tag](/docs/handbook/how-to/add-a-tag/). - Code blocks should use triple backticks and include a language name. Example: ```html diff --git a/site/en/blog/auto-dark-theme/index.md b/site/en/blog/auto-dark-theme/index.md index 956bfc40dcb8..10d1f914f476 100644 --- a/site/en/blog/auto-dark-theme/index.md +++ b/site/en/blog/auto-dark-theme/index.md @@ -14,7 +14,7 @@ tags: - origin-trials --- -Chrome 96 introduces an [origin trial](https://developer.chrome.com/blog/origin-trials/) for Auto Dark Themes on Android. +Chrome 96 introduces an [origin trial](/blog/origin-trials/) for Auto Dark Themes on Android. With this feature, the browser applies an automatically generated dark theme to light themed sites, when the user has opted into dark themes in the operating system. Users can opt-out of dark themes by either disabling the option on the OS level or in a specific setting in Chrome. diff --git a/site/en/blog/autoplay/index.md b/site/en/blog/autoplay/index.md index 504a32340fc3..d7e15582c1b2 100644 --- a/site/en/blog/autoplay/index.md +++ b/site/en/blog/autoplay/index.md @@ -296,7 +296,7 @@ on the Chromium site. [permissions policy for autoplay]: https://github.com/WICG/feature-policy/blob/main/features.md [policy list]: https://chromeenterprise.google/policies/ [progressive-web-apps]: https://web.dev/progressive-web-apps/ -[promise]: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise +[promise]: https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Promise [pull request]: https://github.com/GoogleChromeLabs/airhorn/pull/37 [rejected]: https://developers.google.com/web/updates/2017/06/play-request-was-interrupted -[web audio api]: https://developer.mozilla.org/en-US/docs/Web/API/Web_Audio_API +[web audio api]: https://developer.mozilla.org/docs/Web/API/Web_Audio_API diff --git a/site/en/blog/coep-credentialless-origin-trial/index.md b/site/en/blog/coep-credentialless-origin-trial/index.md index adda18b04738..432c12f273f5 100644 --- a/site/en/blog/coep-credentialless-origin-trial/index.md +++ b/site/en/blog/coep-credentialless-origin-trial/index.md @@ -31,10 +31,10 @@ Some web APIs increase the risk of side-channel attacks such as mitigate that risk, browsers offer an opt-in-based isolated environment called [cross-origin isolation](https://web.dev/coop-coep/). With a cross-origin isolated state, the webpage can use privileged features including -[`SharedArrayBuffer`](https://developer.chrome.com/blog/enabling-shared-array-buffer/), +[`SharedArrayBuffer`](/blog/enabling-shared-array-buffer/), [`performance.measureUserAgentSpecificMemory()`](https://web.dev/monitor-total-page-memory-usage/) and [high-precision timers with better -resolution](https://developer.chrome.com/blog/cross-origin-isolated-hr-timers/) +resolution](/blog/cross-origin-isolated-hr-timers/) while isolating the origin from others unless they are opted in. The webpage must send two HTTP headers to enable cross-origin isolation: @@ -150,7 +150,7 @@ You can register for it to allowlist your website to make the `Cross-Origin-Embedder-Policy: credentialless` header to take effect. 1. [Request a - token](https://developer.chrome.com/origintrials/#/view_trial/3036552048754556929) + token](/origintrials/#/view_trial/3036552048754556929) for your origin. 2. Apply an `Origin-Trial` HTTP header to the document you want to apply `Cross-Origin-Embedder-Policy: credentialless` header. The resulting response @@ -181,7 +181,7 @@ cross-origin isolation: Those who registered for [the Chrome origin trial to extend the SharedArrayBuffer -change](https://developer.chrome.com/blog/enabling-shared-array-buffer/) due to +change](/blog/enabling-shared-array-buffer/) due to the above obstacles might be wondering when it will be terminated. Originally we announced that it will be terminated in Chrome 96, but we have decided to postpone this to Chrome 103. @@ -195,7 +195,7 @@ postpone this to Chrome 103. * [A guide to enable cross-origin isolation](https://web.dev/cross-origin-isolation-guide/) * [SharedArrayBuffer updates in Android Chrome 88 and Desktop Chrome - 92](https://developer.chrome.com/blog/enabling-shared-array-buffer/) + 92](/blog/enabling-shared-array-buffer/) Photo by [Martin Adams](https://unsplash.com/@martinadams?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText) diff --git a/site/en/blog/crx-scripting-api/index.md b/site/en/blog/crx-scripting-api/index.md index 515a01d8cbb7..6697cc43157b 100644 --- a/site/en/blog/crx-scripting-api/index.md +++ b/site/en/blog/crx-scripting-api/index.md @@ -300,7 +300,7 @@ improving the developer experience. By introducing `chrome.scripting` in Manifes to help clean up the Tabs API, to reimagine `executeScript` for a more secure extensions platform, and to lay the groundwork for new scripting capabilities that will be coming later this year. -[content-scripts]: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Content_scripts +[content-scripts]: https://developer.mozilla.org/docs/Mozilla/Add-ons/WebExtensions/Content_scripts [iframe-demo]: https://simple-iframe-demo.glitch.me/ [scripting-api]: /docs/extensions/reference/scripting/ [scripting-executescript]: /docs/extensions/reference/scripting/#method-executeScript diff --git a/site/en/blog/csp-issues/index.md b/site/en/blog/csp-issues/index.md index dea83790d812..7597dbf85f77 100644 --- a/site/en/blog/csp-issues/index.md +++ b/site/en/blog/csp-issues/index.md @@ -127,7 +127,7 @@ Once we had settled on which information we wanted to make available, we needed ### Step 3: issue detection -To make the information available to the Chrome DevTools Protocol (CDP) in the format described in the last section, we needed to find the place where the information was actually available in the back-end. Fortunately, the CSP code already had a bottle-neck used for report-only mode, where we could hook into: [`ContentSecurityPolicy::ReportViolation`](https://source.chromium.org/chromium/chromium/src/+/master:third_party/blink/renderer/core/frame/csp/content_security_policy.cc;l=1128;drc=c7101018b828047f762bab9f0f129cdd53e03180) reports issues to an (optional) reporting end-point that can be configured in the [CSP HTTP header](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/report-to). Most of the information we wanted to report was already available, so no big changes in the back-end were necessary for our instrumentation to work. +To make the information available to the Chrome DevTools Protocol (CDP) in the format described in the last section, we needed to find the place where the information was actually available in the back-end. Fortunately, the CSP code already had a bottle-neck used for report-only mode, where we could hook into: [`ContentSecurityPolicy::ReportViolation`](https://source.chromium.org/chromium/chromium/src/+/master:third_party/blink/renderer/core/frame/csp/content_security_policy.cc;l=1128;drc=c7101018b828047f762bab9f0f129cdd53e03180) reports issues to an (optional) reporting end-point that can be configured in the [CSP HTTP header](https://developer.mozilla.org/docs/Web/HTTP/Headers/Content-Security-Policy/report-to). Most of the information we wanted to report was already available, so no big changes in the back-end were necessary for our instrumentation to work. ### Step 4: save and display the issues @@ -171,7 +171,7 @@ After iteration, we then arrived at: As you can see, involving the feature team and DevRel makes the description a lot more clear and precise! -CSP issues on your page can also be discovered in the [tab specifically dedicated to CSP violations](https://developer.chrome.com/blog/new-in-devtools-89/#csp). +CSP issues on your page can also be discovered in the [tab specifically dedicated to CSP violations](/blog/new-in-devtools-89/#csp). ## Debugging Trusted Types problems @@ -196,7 +196,7 @@ Hence, moving that part of the code to Blink or any embedder sounds like a logic ### Break-on-violation (in report-only mode) -Currently, the [only way of debugging TT violations](https://developer.chrome.com/blog/new-in-devtools-89/#trusted-types) is by setting breakpoints on JS exceptions. Since enforced TT violations will trigger an exception, this feature can be somehow useful. However, in real world scenarios you need a more fine-grained control over TT violations. In particular, we would like to break only on TT violations (not other exceptions), break also in report-only mode and distinguish between the different types of TT violations. +Currently, the [only way of debugging TT violations](/blog/new-in-devtools-89/#trusted-types) is by setting breakpoints on JS exceptions. Since enforced TT violations will trigger an exception, this feature can be somehow useful. However, in real world scenarios you need a more fine-grained control over TT violations. In particular, we would like to break only on TT violations (not other exceptions), break also in report-only mode and distinguish between the different types of TT violations. DevTools already has support for a wide variety of breakpoints so the architecture is quite extensible. Adding a new breakpoint type requires changes in the backend (Blink), CDP and the frontend. We should introduce a new CDP command, let's call it `setBreakOnTTViolation`. This command will be used by the frontend to tell the backend on what sort of TT violations it should break. The backend, in particular `InspectorDOMDebuggerAgent`, will provide a "probe", `onTTViolation()` that will be called every time a TT violation occurs. Then, `InspectorDOMDebuggerAgent` will check if that violation should trigger a breakpoint, and if that is the case it will send a message to the frontend to pause the execution. @@ -206,10 +206,10 @@ We should introduce a new CDP command, let's call it `setBreakOnTTViolation`. Th Since the issues described here were introduced, the **Issues** tab has undergone quite some changes: -- Its [interconnectedness](https://developer.chrome.com/blog/new-in-devtools-89/#trusted-type-link) with other panels in DevTools has been improved. -- Reporting of a number of further problems has moved to the **Issues** tab: [low-contrast](https://developer.chrome.com/blog/new-in-devtools-90/#low-contrast), [trusted web-activity](https://developer.chrome.com/blog/new-in-devtools-90/#twa), [quirks mode](https://developer.chrome.com/blog/new-in-devtools-92/#quirks-mode), [attribution reporting API](https://developer.chrome.com/blog/new-in-devtools-93/#attribution-reporting) and -[CORS-related issues](https://developer.chrome.com/blog/new-in-devtools-93/#cors) among others. -- An opportunity to [hide issues](https://developer.chrome.com/blog/new-in-devtools-94/#hide-issues) was introduced +- Its [interconnectedness](/blog/new-in-devtools-89/#trusted-type-link) with other panels in DevTools has been improved. +- Reporting of a number of further problems has moved to the **Issues** tab: [low-contrast](/blog/new-in-devtools-90/#low-contrast), [trusted web-activity](/blog/new-in-devtools-90/#twa), [quirks mode](/blog/new-in-devtools-92/#quirks-mode), [attribution reporting API](/blog/new-in-devtools-93/#attribution-reporting) and +[CORS-related issues](/blog/new-in-devtools-93/#cors) among others. +- An opportunity to [hide issues](/blog/new-in-devtools-94/#hide-issues) was introduced Moving forward, we plan to use the **Issues** tab to surface more problems, which will make it possible to unload the Console of the unreadable error-message flow in the long run. diff --git a/site/en/blog/css-grid-tooling/index.md b/site/en/blog/css-grid-tooling/index.md index 110084e2cbdc..3cfd013ba8c7 100644 --- a/site/en/blog/css-grid-tooling/index.md +++ b/site/en/blog/css-grid-tooling/index.md @@ -101,7 +101,7 @@ where each `GridNodeHighlightConfig` contains information about which node to dr ## Real-time Grid badges -To help developers easily toggle on and off the Grid overlays, we decided to add small badges next to Grid containers in the [DOM Tree](https://developer.chrome.com/docs/devtools/dom/). These badges can also help developers identify Grid containers in their DOM structures. +To help developers easily toggle on and off the Grid overlays, we decided to add small badges next to Grid containers in the [DOM Tree](/docs/devtools/dom/). These badges can also help developers identify Grid containers in their DOM structures. {% Img src="image/1D9D0Ls1ATa2ZPA9x2ZWrGFyZzT2/JuOPl5pjlitbTTptxRw4.png", alt="ALT_TEXT_HERE", width="608", height="322" %} diff --git a/site/en/blog/deps-rems-94/index.md b/site/en/blog/deps-rems-94/index.md index a92844bfb301..c78a75f7ab45 100644 --- a/site/en/blog/deps-rems-94/index.md +++ b/site/en/blog/deps-rems-94/index.md @@ -21,9 +21,9 @@ stable version in late September, 2021. Removal is expected in Chrome 97. The Web SQL Database standard was first proposed in April 2009 and abandoned in November 2010. Gecko never implemented this feature and WebKit deprecated this feature in 2019. The W3C encourages -[Web Storage](https://developer.mozilla.org/en-US/docs/Web/API/Web_Storage_API) +[Web Storage](https://developer.mozilla.org/docs/Web/API/Web_Storage_API) and -[Indexed Database](https://developer.mozilla.org/en-US/docs/Web/API/IndexedDB_API) +[Indexed Database](https://developer.mozilla.org/docs/Web/API/IndexedDB_API) for those needing alternatives. Developers should expect that WebSQL itself will be deprecated and removed when diff --git a/site/en/blog/deps-rems-95/index.md b/site/en/blog/deps-rems-95/index.md index 8b3ad9189060..119cb483819c 100644 --- a/site/en/blog/deps-rems-95/index.md +++ b/site/en/blog/deps-rems-95/index.md @@ -61,7 +61,7 @@ Chrome's legacy U2F API for interacting with security keys is deprecated. It will be disabled by default in Chrome 98. Affected sites should migrate to the [Web Authentication -API](https://developer.mozilla.org/en-US/docs/Web/API/Web_Authentication_API). +API](https://developer.mozilla.org/docs/Web/API/Web_Authentication_API). Credentials that were originally registered via the U2F API can be challenged via web authentication. USB security keys that are supported by the U2F API are also supported by the Web Authentication API. U2F security keys themselves are @@ -93,7 +93,7 @@ were implemented: + Gated U2F API requests behind a user permission prompt. The permission prompt can be suppressed by enrolling in the [U2FSecurityKeyAPI -deprecation trial](https://developer.chrome.com/origintrials/#/view_trial/-6366963973195038719) +deprecation trial](/origintrials/#/view_trial/-6366963973195038719) or enabling the [U2fSecurityKeyApiEnabled](https://chromeenterprise.google/policies/#U2fSecurityKeyApiEnabled) enterprise policy. @@ -101,7 +101,7 @@ enterprise policy. Beta expected in early January 2022, stable in February. The U2F API will be disabled by default. Only sites enrolled in the [deprecation -trial](https://developer.chrome.com/origintrials/#/view_trial/-6366963973195038719) +trial](/origintrials/#/view_trial/-6366963973195038719) or enterprises that turned on the [U2fSecurityKeyApiEnabled](https://chromeenterprise.google/policies/#U2fSecurityKeyApiEnabled) policy will be able to use U2F at this point. diff --git a/site/en/blog/deps-rems-97/index.md b/site/en/blog/deps-rems-97/index.md index eaa0c80e2dd6..db232a1ab1a6 100644 --- a/site/en/blog/deps-rems-97/index.md +++ b/site/en/blog/deps-rems-97/index.md @@ -33,9 +33,9 @@ removed](https://www.chromestatus.com/feature/5695324321480704) as of Chrome The Web SQL Database standard was first proposed in April 2009 and abandoned in November 2010. Gecko never implemented this feature and WebKit deprecated it in 2019. The W3C encourages -[Web Storage](https://developer.mozilla.org/en-US/docs/Web/API/Web_Storage_API) +[Web Storage](https://developer.mozilla.org/docs/Web/API/Web_Storage_API) and -[Indexed Database](https://developer.mozilla.org/en-US/docs/Web/API/IndexedDB_API) +[Indexed Database](https://developer.mozilla.org/docs/Web/API/IndexedDB_API) for those needing alternatives. ## Remove SDP Plan B diff --git a/site/en/blog/enabling-shared-array-buffer/index.md b/site/en/blog/enabling-shared-array-buffer/index.md index c2d9885f1729..c3fe011427d2 100644 --- a/site/en/blog/enabling-shared-array-buffer/index.md +++ b/site/en/blog/enabling-shared-array-buffer/index.md @@ -60,7 +60,7 @@ Cross-Origin-Opener-Policy: same-origin Once you do this, your page will not be able to load cross-origin content unless the resource explicitly allows it via a [`Cross-Origin-Resource-Policy`][corp] -header or [CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS) headers +header or [CORS](https://developer.mozilla.org/docs/Web/HTTP/CORS) headers (`Access-Control-Allow-*` and so forth). There's also a [reporting @@ -147,7 +147,7 @@ These APIs have a 'legacy' behavior that allows content from other origins to be used without opt-in from the other origin. These requests are made with the cookies of the other origin, so it's a full 'logged in' request. Nowadays, new APIs require the other origin to opt-in using -[CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS). +[CORS](https://developer.mozilla.org/docs/Web/HTTP/CORS). We worked around these legacy APIs by preventing content from entering the webpage's process if it looked 'incorrect', and called it [cross-origin read @@ -170,8 +170,8 @@ This declaration is done via [COOP and COEP headers](https://web.dev/coop-coep/) served with the page. The browser enforces that, and in exchange the page gains access to `SharedArrayBuffer` and other APIs with similar powers. Other origins can opt-in to content embedding via -[`Cross-Origin-Resource-Policy`]() -or [CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS). +[`Cross-Origin-Resource-Policy`]() +or [CORS](https://developer.mozilla.org/docs/Web/HTTP/CORS). Firefox was the first to ship `SharedArrayBuffer` with this restriction, in version 79 (July 2020). @@ -214,6 +214,6 @@ href="https://unsplash.com/@yeeeeeeha?utm_source=unsplash&utm_medium=referra Gregoire on Unsplash -[mdn]: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/SharedArrayBuffer -[compat]: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/SharedArrayBuffer#browser_compatibility -[corp]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Cross-Origin_Resource_Policy_(CORP) +[mdn]: https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/SharedArrayBuffer +[compat]: https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/SharedArrayBuffer#browser_compatibility +[corp]: https://developer.mozilla.org/docs/Web/HTTP/Cross-Origin_Resource_Policy_(CORP) diff --git a/site/en/blog/faster-stack-traces/index.md b/site/en/blog/faster-stack-traces/index.md index e0e0986932b4..2c8acf235035 100644 --- a/site/en/blog/faster-stack-traces/index.md +++ b/site/en/blog/faster-stack-traces/index.md @@ -104,13 +104,13 @@ The first thing that stood out was the cumulative cost for computing line and co The more interesting finding for us was that `v8::StackFrame::GetFunctionName` was surprisingly high in all the profiles we looked at. Digging deeper here we realized that it was unnecessarily costly to compute the name we'd show for the function in the stack frame in DevTools, -1. first looking for the [non-standard `"displayName"` property](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Function/displayName) and if that yielded a data property with a string value, we'd use that, -2. otherwise falling back to looking for the [standard `"name"` property](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Function/name) and again checking if that yields a data property whose value is a string, +1. first looking for the [non-standard `"displayName"` property](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Function/displayName) and if that yielded a data property with a string value, we'd use that, +2. otherwise falling back to looking for the [standard `"name"` property](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Function/name) and again checking if that yields a data property whose value is a string, 3. and eventually falling back to an internal debug name that's inferred by the V8 parser and stored on the function literal. The `"displayName"` property was added as a work-around for the `"name"` property on `Function` instances being read-only and non-configurable in JavaScript, but was never standardized and didn't see wide-spread use, since the browser developer tools added function name inference that does the job in 99.9% of the cases. On top of that ES2015 made the `"name"` property on `Function` instances configurable, completely removing the need for a special `"displayName"` property. Since the negative lookup for `"displayName"` is quite costly and not really necessary (ES2015 was released over five years ago), we decided to [remove support for the non-standard `fn.displayName` property](https://bit.ly/devtools-function-displayName-removal) from V8 (and DevTools). -With the negative lookup of `"displayName"` out of the way, half of the cost of `v8::StackFrame::GetFunctionName` was removed. The other half goes to the generic `"name"` property lookup. Fortunately we already had some logic in place to avoid costly lookups of `"name"` property on (untouched) `Function` instances, which we introduced in V8 a while ago to make [`Function.prototype.bind()`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_objects/Function/bind) itself faster. We [ported the necessary checks](https://crrev.com/c/2695593) which allow us to skip the costly generic lookup in the first place, with the result that `v8::StackFrame::GetFunctionName` doesn't show up in any profiles we've considered anymore. +With the negative lookup of `"displayName"` out of the way, half of the cost of `v8::StackFrame::GetFunctionName` was removed. The other half goes to the generic `"name"` property lookup. Fortunately we already had some logic in place to avoid costly lookups of `"name"` property on (untouched) `Function` instances, which we introduced in V8 a while ago to make [`Function.prototype.bind()`](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_objects/Function/bind) itself faster. We [ported the necessary checks](https://crrev.com/c/2695593) which allow us to skip the costly generic lookup in the first place, with the result that `v8::StackFrame::GetFunctionName` doesn't show up in any profiles we've considered anymore. ## Conclusion With the above improvements, we've significantly reduced the overhead of DevTools in terms of stack traces. diff --git a/site/en/blog/first-party-sets-sameparty/index.md b/site/en/blog/first-party-sets-sameparty/index.md index 55fbd91d4876..6dc9cf5e1052 100644 --- a/site/en/blog/first-party-sets-sameparty/index.md +++ b/site/en/blog/first-party-sets-sameparty/index.md @@ -196,7 +196,7 @@ There are a few constraints for first-party sets: {% Aside %} You may already be hosting a similar file if you are using [Digital -Asset Links to link sites](https://developer.chrome.com/blog/site-affiliation/) +Asset Links to link sites](/blog/site-affiliation/) that share the same account management backend. This is specifically to allow the same credentials to be suggested by the Chrome password manager across the affiliated sites. @@ -307,7 +307,7 @@ first-party set would affect the cookies. If you have the bandwidth for experimentation and feedback, you can also sign up for the [Origin Trial for First Party Sets and -SameParty](https://developer.chrome.com/origintrials/#/view_trial/988540118207823873) +SameParty](/origintrials/#/view_trial/988540118207823873) which is available in Chrome from version 89 to 93. {% Aside 'key-term' %} diff --git a/site/en/blog/floc/index.md b/site/en/blog/floc/index.md index a189d67fcecc..76fd152783f9 100644 --- a/site/en/blog/floc/index.md +++ b/site/en/blog/floc/index.md @@ -16,7 +16,7 @@ tags: {% Aside 'warning' %} The origin trial for the initial version of FLoC ran from Chrome 89 to 91 and -[is now closed](https://developer.chrome.com/origintrials/#/view_trial/213920982300098561). +[is now closed](/origintrials/#/view_trial/213920982300098561). This post refers to the API implemented in Chrome for the first origin trial of FLoC. @@ -48,7 +48,7 @@ To find out more about FLoC, see [What is Federated Learning of Cohorts?](https: An origin trial for FLoC started in Chrome 89, and has been made available as a [third-party origin trial](https://web.dev/third-party-origin-trials/). -To take part, you will need to [register](https://developer.chrome.com/origintrials/#/view_trial/213920982300098561) for a FLoC origin trial token. +To take part, you will need to [register](/origintrials/#/view_trial/213920982300098561) for a FLoC origin trial token. {% Aside %} The initial testing of FLoC is taking place with a [small percentage of users](https://blog.google/products/chrome/privacy-sustainability-and-the-importance-of-and/#jump-content:~:text=The%20initial%20testing%20of%20FLoC%20is%20taking%20place%20with%20a%20small%20percentage%20of%20users), and FLoC is subject to [origin trial usage limits](https://github.com/GoogleChrome/OriginTrials/blob/gh-pages/developer-guide.md#19-are-there-any-usage-limits-on-experimental-features). This means that initially during the @@ -76,7 +76,7 @@ You will need to inject the origin trial token in a meta tag in order to test th ### Submit feedback -Do this through Chrome's [origin trial site](https://developer.chrome.com/origintrials/#/trials/active). This feedback is not public and is available only to a limited group of people on the Chrome team. +Do this through Chrome's [origin trial site](/origintrials/#/trials/active). This feedback is not public and is available only to a limited group of people on the Chrome team. When your token expires, you will get an email with a renewal link. Before renewing the token, you are again asked to submit feedback. ## Try out FLoC as a web developer diff --git a/site/en/blog/media-updates-in-chrome-61/index.md b/site/en/blog/media-updates-in-chrome-61/index.md index 97833737a098..01471cceaaa4 100644 --- a/site/en/blog/media-updates-in-chrome-61/index.md +++ b/site/en/blog/media-updates-in-chrome-61/index.md @@ -108,5 +108,5 @@ This magic behavior only happens when: [Page Visibility API]: https://www.w3.org/TR/page-visibility/ [keyframe]: https://en.wikipedia.org/wiki/Key_frame#Video_compression [Mobile Web Video Playback]: https://developers.google.com/web/fundamentals/media/mobile-web-video-playback#fullscreen -[fullscreen element]: https://developer.mozilla.org/en-US/docs/Web/API/Document/fullscreenElement +[fullscreen element]: https://developer.mozilla.org/docs/Web/API/Document/fullscreenElement [Screen Orientation API]: https://w3c.github.io/screen-orientation/ diff --git a/site/en/blog/modernising-css-infra-in-devtools/index.md b/site/en/blog/modernising-css-infra-in-devtools/index.md index 18c045f63598..33669bc5bfb4 100644 --- a/site/en/blog/modernising-css-infra-in-devtools/index.md +++ b/site/en/blog/modernising-css-infra-in-devtools/index.md @@ -92,7 +92,7 @@ We looked into different potential solutions for each part and these are outline The goal with importing and utilising CSS in the TypeScript files was to stick as close to web standards as possible, **enforce consistency throughout DevTools and avoid duplicated CSS** in our HTML. We also wanted to be able to pick a solution that would make it possible to migrate our changes to new web platform standards, such as CSS Module Scripts. -For these reasons the [@import](https://developer.mozilla.org/en-US/docs/Web/CSS/@import) statements and [](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/link) tags did not seem like the right fit for DevTools. They would not be uniform with imports throughout the rest of DevTools and result in a [Flash Of Unstyled Content (FOUC)](https://en.wikipedia.org/wiki/Flash_of_unstyled_content). The migration to CSS Module Scripts would be harder because the imports would have to be explicitly added and dealt with differently than they would with `` tags. +For these reasons the [@import](https://developer.mozilla.org/docs/Web/CSS/@import) statements and [](https://developer.mozilla.org/docs/Web/HTML/Element/link) tags did not seem like the right fit for DevTools. They would not be uniform with imports throughout the rest of DevTools and result in a [Flash Of Unstyled Content (FOUC)](https://en.wikipedia.org/wiki/Flash_of_unstyled_content). The migration to CSS Module Scripts would be harder because the imports would have to be explicitly added and dealt with differently than they would with `` tags. ```js const output = LitHtml.html` @@ -107,7 +107,7 @@ const output = LitHtml.html` ``` Potential solutions using `@import` or ``. -Instead we opted to find a way to import the CSS file as a [`CSSStyleSheet`](https://developer.mozilla.org/en-US/docs/Web/API/CSSStyleSheet) object so that we can add it to the [Shadow Dom](https://developers.google.com/web/fundamentals/web-components/shadowdom) (DevTools uses Shadow DOM for a couple of years now) using its [`adoptedStyleSheets`](https://developers.google.com/web/updates/2019/02/constructable-stylesheets#using_constructed_stylesheets) property. +Instead we opted to find a way to import the CSS file as a [`CSSStyleSheet`](https://developer.mozilla.org/docs/Web/API/CSSStyleSheet) object so that we can add it to the [Shadow Dom](https://developers.google.com/web/fundamentals/web-components/shadowdom) (DevTools uses Shadow DOM for a couple of years now) using its [`adoptedStyleSheets`](https://developers.google.com/web/updates/2019/02/constructable-stylesheets#using_constructed_stylesheets) property. ### Bundler options {: #bundler-options } diff --git a/site/en/blog/new-in-chrome-55/index.md b/site/en/blog/new-in-chrome-55/index.md index f2bcaef929be..9a161030c2f8 100644 --- a/site/en/blog/new-in-chrome-55/index.md +++ b/site/en/blog/new-in-chrome-55/index.md @@ -39,7 +39,7 @@ work so well on here. Touch events are good, but to support [touch](https://www.w3.org/TR/touch-events/) and -[mouse](https://developer.mozilla.org/en-US/docs/Web/API/MouseEvent), you had +[mouse](https://developer.mozilla.org/docs/Web/API/MouseEvent), you had to support two event models: ```js @@ -48,7 +48,7 @@ elem.addEventListener('touchmove', touchMoveEvent); ``` Chrome now enables unified input handling by dispatching -[PointerEvents](https://developer.mozilla.org/en-US/docs/Web/API/PointerEvent): +[PointerEvents](https://developer.mozilla.org/docs/Web/API/PointerEvent): ```js elem.addEventListener('pointermove', pointerMoveEvent); diff --git a/site/en/blog/new-in-chrome-56/index.md b/site/en/blog/new-in-chrome-56/index.md index 5dd25831cf85..f08ea3272d0e 100644 --- a/site/en/blog/new-in-chrome-56/index.md +++ b/site/en/blog/new-in-chrome-56/index.md @@ -59,7 +59,7 @@ switching an element's position from relative to fixed at a specified threshold. It was difficult to synchronize, and often results in small visual jumps. Chrome now supports CSS -[`position: sticky;`](//developer.mozilla.org/en-US/docs/Web/CSS/position#Sticky_positioning), +[`position: sticky;`](//developer.mozilla.org/docs/Web/CSS/position#Sticky_positioning), a new way to position elements. An element that is position sticky, starts relative; but becomes fixed, diff --git a/site/en/blog/new-in-chrome-57/index.md b/site/en/blog/new-in-chrome-57/index.md index 4def676e9ffd..9c03f0ea431f 100644 --- a/site/en/blog/new-in-chrome-57/index.md +++ b/site/en/blog/new-in-chrome-57/index.md @@ -33,7 +33,7 @@ I'm [Pete LePage](https://petelepage.com/), let's dive in and see what's new for Flexbox is a powerful layout tool. It makes many complex layouts possible, but it can only do layout in one dimension. Chrome 57 adds support for -[`display: grid`](https://developer.mozilla.org/en-US/docs/Learn/CSS/CSS_layout/Grids) - +[`display: grid`](https://developer.mozilla.org/docs/Learn/CSS/CSS_layout/Grids) - the new [CSS Grid Layout specification](https://www.w3.org/TR/css3-grid-layout/), adding a powerful new tool for creating two-dimensional grid-based layout systems, optimized for responsive user interface design. @@ -79,21 +79,21 @@ And there's lots more! [`caret-color`](https://www.chromestatus.com/feature/5720917787279360) property. * Visual effects such as line color and style can be specified with new - [`text-decoration`](https://developer.mozilla.org/en-US/docs/Web/CSS/text-decoration) + [`text-decoration`](https://developer.mozilla.org/docs/Web/CSS/text-decoration) properties. -* The [Fetch API](https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API) - [Response class](https://developer.mozilla.org/en-US/docs/Web/API/Response) +* The [Fetch API](https://developer.mozilla.org/docs/Web/API/Fetch_API) + [Response class](https://developer.mozilla.org/docs/Web/API/Response) now supports the - [`.redirected`](https://developer.mozilla.org/en-US/docs/Web/API/Response/redirected) + [`.redirected`](https://developer.mozilla.org/docs/Web/API/Response/redirected) attribute to help avoid untrustworthy responses and reduce the risk of open redirectors. -* All `-webkit-` prefixed [IndexedDB](https://developer.mozilla.org/en-US/docs/Web/API/IndexedDB_API) +* All `-webkit-` prefixed [IndexedDB](https://developer.mozilla.org/docs/Web/API/IndexedDB_API) global aliases have been removed, after their deprecation in M38. * And one of my favorites — new - [`padStart`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/padStart) + [`padStart`](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/String/padStart) and - [`padEnd`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/padEnd) + [`padEnd`](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/String/padEnd) formatting methods that simplify string padding when aligning console output or printing numbers with a fixed number of digits. diff --git a/site/en/blog/new-in-chrome-61/index.md b/site/en/blog/new-in-chrome-61/index.md index c5a355be1f06..c65ccab06df2 100644 --- a/site/en/blog/new-in-chrome-61/index.md +++ b/site/en/blog/new-in-chrome-61/index.md @@ -110,7 +110,7 @@ on updates. * You can now specify scrolling smoothness with the [`scroll-behavior`](https://drafts.csswg.org/cssom-view/#smooth-scrolling) CSS property. -* [CSS hex color values](https://developer.mozilla.org/en-US/docs/Web/CSS/color_value#rgba) +* [CSS hex color values](https://developer.mozilla.org/docs/Web/CSS/color_value#rgba) can now specify alpha transparency by adding digits to the end of the string. * You can access the relative positions of the screen content with the [Visual Viewport API](https://github.com/WICG/ViewportAPI), exposing complex diff --git a/site/en/blog/new-in-chrome-65/index.md b/site/en/blog/new-in-chrome-65/index.md index 2c4dc2ec174b..1783f5cdd7d9 100644 --- a/site/en/blog/new-in-chrome-65/index.md +++ b/site/en/blog/new-in-chrome-65/index.md @@ -166,7 +166,7 @@ there's plenty more. * The syntax for specifying `HSL` and `HSLA`, and `RGB` and `RGBA` coordinates for the color property now [match](https://drafts.csswg.org/css-color/#the-hsl-notation) the - [CSS Color 4 spec](https://developer.mozilla.org/en-US/docs/Web/CSS/color_value). + [CSS Color 4 spec](https://developer.mozilla.org/docs/Web/CSS/color_value). * There's a new [feature policy](http://xhr.featurepolicy.rocks/) that allows you to control synchronous XHRs through an HTTP header or the iframe `allow` attribute. diff --git a/site/en/blog/new-in-chrome-67/index.md b/site/en/blog/new-in-chrome-67/index.md index 7c864a8af414..e93603574390 100644 --- a/site/en/blog/new-in-chrome-67/index.md +++ b/site/en/blog/new-in-chrome-67/index.md @@ -143,7 +143,7 @@ These are just a few of the changes in Chrome 67 for developers, of course, there's plenty more. The -[Credential Management API](https://developer.mozilla.org/en-US/docs/Web/API/Credential_Management_API) +[Credential Management API](https://developer.mozilla.org/docs/Web/API/Credential_Management_API) has been supported since Chrome 51, and provides a framework for creating, retrieving and storing credentials. It did this through two credential types: `PasswordCredential` and `FederatedCredential`. The diff --git a/site/en/blog/new-in-chrome-69/index.md b/site/en/blog/new-in-chrome-69/index.md index 8201016d96ef..0af8a487e9ae 100644 --- a/site/en/blog/new-in-chrome-69/index.md +++ b/site/en/blog/new-in-chrome-69/index.md @@ -58,7 +58,7 @@ is no longer on the standards track. -[CSS Scroll Snap](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Scroll_Snap) +[CSS Scroll Snap](https://developer.mozilla.org/docs/Web/CSS/CSS_Scroll_Snap) allows you to create smooth, slick, scroll experiences, by declaring scroll snap positions that tell the browser where to stop after each scrolling operation. This is super helpful for image carousels, or paginated sections @@ -142,7 +142,7 @@ for more details. ## Web Locks API {: #web-locks } -The [Web Locks API](https://developer.mozilla.org/en-US/docs/Web/API/Web_Locks_API) +The [Web Locks API](https://developer.mozilla.org/docs/Web/API/Web_Locks_API) allows you to asynchronously acquire a lock, hold it while work is performed, then release it. While the lock is held, no other script in the origin can acquire the same lock, helping to coordinate the usage of shared resources. @@ -164,7 +164,7 @@ The first tab to acquire the lock will sync the data to the network. If another tab tries to acquire the same lock, it'll be queued. Once the lock has been released, the next queued request will be granted the lock, and execute. -MDN has a great [Web Locks primer](https://developer.mozilla.org/en-US/docs/Web/API/Web_Locks_API) +MDN has a great [Web Locks primer](https://developer.mozilla.org/docs/Web/API/Web_Locks_API) and includes a more in-depth explanation and lots of examples. Or dive in deeper and check out the [spec](https://github.com/WICG/web-locks). @@ -183,9 +183,9 @@ there's plenty more. that you can use, and the page includes a whole bunch of really cool community submitted samples. * There's a new - [`toggleAttribute()`](https://developer.mozilla.org/en-US/docs/Web/API/Element/toggleAttribute) + [`toggleAttribute()`](https://developer.mozilla.org/docs/Web/API/Element/toggleAttribute) method on elements that toggles the existence of an attribute, similar to - [`classList.toggle()`](https://developer.mozilla.org/en-US/docs/Web/API/Element/classList). + [`classList.toggle()`](https://developer.mozilla.org/docs/Web/API/Element/classList). * JavaScript arrays are getting two new methods: [`flat()` and `flatMap()`](https://developers.google.com/web/updates/2018/03/smooshgate). They return a new array with all sub-array elements smooshed into it. diff --git a/site/en/blog/new-in-chrome-70/index.md b/site/en/blog/new-in-chrome-70/index.md index 0b4c364474fb..e28aa9a7b1ac 100644 --- a/site/en/blog/new-in-chrome-70/index.md +++ b/site/en/blog/new-in-chrome-70/index.md @@ -73,16 +73,16 @@ in Chrome 70, but was accidentally left out of the original version of this post ## Credential Management API: Public Key Credentials {: #pki } -The [Credential Management API](https://developer.mozilla.org/en-US/docs/Web/API/Credential_Management_API) +The [Credential Management API](https://developer.mozilla.org/docs/Web/API/Credential_Management_API) makes sign in super simple for users. It allows your site to interact with the -browser's [credential manager](https://developer.mozilla.org/en-US/docs/Web/API/PasswordCredential) -or [federated account services](https://developer.mozilla.org/en-US/docs/Web/API/FederatedCredential) +browser's [credential manager](https://developer.mozilla.org/docs/Web/API/PasswordCredential) +or [federated account services](https://developer.mozilla.org/docs/Web/API/FederatedCredential) like Google and Facebook to sign. {% Img src="image/0g2WvpbGRGdVs0aAPc6ObG7gkud2/dlNQwA1kTHjDdHTTOPMK.png", alt="", class="float-right", height="458", width="624" %} Chrome 70 adds support for a third type of credential: -[**Public Key Credential**](https://developer.mozilla.org/en-US/docs/Web/API/PublicKeyCredential), +[**Public Key Credential**](https://developer.mozilla.org/docs/Web/API/PublicKeyCredential), which allows web applications to create and use, strong, cryptographically attested, and application-scoped credentials to strongly authenticate users. @@ -96,7 +96,7 @@ for more details or give it a try with the ## Named `workers` {: #named-workers } -[Workers](https://developer.mozilla.org/en-US/docs/Web/API/Worker) are an easy +[Workers](https://developer.mozilla.org/docs/Web/API/Worker) are an easy way to move JavaScript off the main thread and into the background. This is critical to keeping your site interactive, because it means that the main thread won't lock up when it's running an expensive or complex JavaScript diff --git a/site/en/blog/new-in-chrome-71/index.md b/site/en/blog/new-in-chrome-71/index.md index 9f573a86fb2a..4e87afcb0a8e 100644 --- a/site/en/blog/new-in-chrome-71/index.md +++ b/site/en/blog/new-in-chrome-71/index.md @@ -120,7 +120,7 @@ We've all been surprised when we hit a site and it suddenly starts talking to us. [Autoplay policies](https://developers.google.com/web/updates/2018/11/web-audio-autoplay) prevent sites from automatically playing playing audio, or video files with audio. Some sites have tried to get around this by using the -[speech synthesis API](https://developer.mozilla.org/en-US/docs/Web/API/SpeechSynthesis) +[speech synthesis API](https://developer.mozilla.org/docs/Web/API/SpeechSynthesis) instead. Starting in Chrome 71, the speech synthesis API now requires some kind of user @@ -204,7 +204,7 @@ and you'll get an email notification whenever we launch a new video. I'm Pete LePage, and as soon as Chrome 72 is released, I'll be right here to tell you -- what's new in Chrome! -[mdn-reltimefmt]: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl.RelativeTimeFormat +[mdn-reltimefmt]: https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Intl.RelativeTimeFormat [css3-td-spec]: https://www.w3.org/TR/css-text-decor-3/ [css3-td-line]: https://www.w3.org/TR/css-text-decor-3/#text-decoration-style-property [css3-td-style]: https://www.w3.org/TR/css-text-decor-3/#text-decoration-style-property diff --git a/site/en/blog/new-in-chrome-72/index.md b/site/en/blog/new-in-chrome-72/index.md index c9465a665624..294207610dee 100644 --- a/site/en/blog/new-in-chrome-72/index.md +++ b/site/en/blog/new-in-chrome-72/index.md @@ -80,7 +80,7 @@ More details are in Mathias's article on [class fields](https://developers.google.com/web/updates/2018/12/class-fields) for more details. -[mdn-classes]: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes +[mdn-classes]: https://developer.mozilla.org/docs/Web/JavaScript/Reference/Classes ## User Activation API {: #user-activation } diff --git a/site/en/blog/new-in-chrome-86/index.md b/site/en/blog/new-in-chrome-86/index.md index b24b4854bf8d..68e670aae3aa 100644 --- a/site/en/blog/new-in-chrome-86/index.md +++ b/site/en/blog/new-in-chrome-86/index.md @@ -255,7 +255,7 @@ and you'll get an email notification whenever we launch a new video, or add our I'm Pete LePage, and as soon as Chrome 87 is released, I'll be right here to tell you -- what's new in Chrome! -[a-download]: https://developer.mozilla.org/en-US/docs/Web/API/HTMLAnchorElement/download +[a-download]: https://developer.mozilla.org/docs/Web/API/HTMLAnchorElement/download [fs-article]: https://web.dev/file-system-access/ [wd-window]: https://web.dev/multi-screen-window-placement/ [ot-hid]: /origintrials/#/view_trial/1074108511127863297 diff --git a/site/en/blog/new-in-chrome-87/index.md b/site/en/blog/new-in-chrome-87/index.md index e2bc22bada00..c49bb10f7c15 100644 --- a/site/en/blog/new-in-chrome-87/index.md +++ b/site/en/blog/new-in-chrome-87/index.md @@ -244,7 +244,7 @@ tell you -- what's new in Chrome! [wd-ptz]: https://web.dev/camera-pan-tilt-zoom/ [wd-fonts]: https://web.dev/local-fonts/ -[mdn-rr]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Range_requests +[mdn-rr]: https://developer.mozilla.org/docs/Web/HTTP/Range_requests [wd-rr]: https://web.dev/sw-range-requests/ [cds2020]: /devsummit/?utm_source=nic87&utm_medium=website [cds-schedule]: /devsummit/schedule/?utm_source=nic87&utm_medium=website diff --git a/site/en/blog/new-in-chrome-96/index.md b/site/en/blog/new-in-chrome-96/index.md index ce887e2b06f1..a96756b4d93f 100644 --- a/site/en/blog/new-in-chrome-96/index.md +++ b/site/en/blog/new-in-chrome-96/index.md @@ -213,7 +213,7 @@ tell you what's new in Chrome! [dcc]: /blog/ [manifest-id]: /blog/pwa-manifest-id/ -[mdn-regph]: https://developer.mozilla.org/en-US/docs/Web/API/Navigator/registerProtocolHandler +[mdn-regph]: https://developer.mozilla.org/docs/Web/API/Navigator/registerProtocolHandler [wd-phreg]: https://web.dev/url-protocol-handler/ [wd-phints]: https://web.dev/priority-hints/ [ph-ot]: /origintrials/#/view_trial/365917469723852801 diff --git a/site/en/blog/new-in-devtools-62/index.md b/site/en/blog/new-in-devtools-62/index.md index 6af4a811c0b0..39ae890862d5 100644 --- a/site/en/blog/new-in-devtools-62/index.md +++ b/site/en/blog/new-in-devtools-62/index.md @@ -218,7 +218,7 @@ Starting in Chrome 62, the **Coverage** tab now tells you which code within a fu [12]: /docs/devtools/css/reference#select [13]: /docs/devtools/command-menu/ [14]: /docs/devtools/console/reference/#context -[15]: https://developer.mozilla.org/en-US/docs/Web/API/Cache +[15]: https://developer.mozilla.org/docs/Web/API/Cache [16]: https://googlechrome.github.io/devtools-samples/whatsnew/m62/cache.html [17]: /blog/new-in-devtools-59#coverage [18]: /blog/new-in-devtools-59#screenshots diff --git a/site/en/blog/new-in-devtools-68/index.md b/site/en/blog/new-in-devtools-68/index.md index 93ed3cc1ebb7..047205cd4f9a 100644 --- a/site/en/blog/new-in-devtools-68/index.md +++ b/site/en/blog/new-in-devtools-68/index.md @@ -176,8 +176,8 @@ The **Show timestamps** checkbox previously in **Console Settings** [7]: #watch [8]: #timestamps [9]: https://stackoverflow.com/a/8129277/1669860 -[10]: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Functions/Default_parameters -[11]: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Spread_syntax +[10]: https://developer.mozilla.org/docs/Web/JavaScript/Reference/Functions/Default_parameters +[11]: https://developer.mozilla.org/docs/Web/JavaScript/Reference/Operators/Spread_syntax [12]: #eagerevaluation [13]: https://developers.google.com/web/updates/2018/05/lighthouse3 [14]: https://developers.google.com/web/updates/2018/05/bigint diff --git a/site/en/blog/new-in-devtools-70/index.md b/site/en/blog/new-in-devtools-70/index.md index 07b4f6f4b43c..97b43fcae17b 100644 --- a/site/en/blog/new-in-devtools-70/index.md +++ b/site/en/blog/new-in-devtools-70/index.md @@ -222,8 +222,8 @@ lifecycle function. React does this in development mode. [14]: /docs/devtools/javascript/breakpoints#conditional-loc [15]: https://codemirror.net/ [16]: /docs/devtools/javascript/breakpoints#event-listeners -[17]: https://developer.mozilla.org/en-US/docs/Web/API/AudioContext +[17]: https://developer.mozilla.org/docs/Web/API/AudioContext [18]: https://medium.com/@paul_irish/debugging-node-js-nightlies-with-chrome-devtools-7c4a1b95ae27 [19]: https://github.com/GoogleChromeLabs/ndb/blob/master/README.md -[20]: https://developer.mozilla.org/en-US/docs/Web/API/User_Timing_API +[20]: https://developer.mozilla.org/docs/Web/API/User_Timing_API [21]: https://en.wikipedia.org/wiki/Call_to_action_(marketing) diff --git a/site/en/blog/new-in-devtools-75/index.md b/site/en/blog/new-in-devtools-75/index.md index f45cc1b3f39a..aef8ad4c95d6 100644 --- a/site/en/blog/new-in-devtools-75/index.md +++ b/site/en/blog/new-in-devtools-75/index.md @@ -165,16 +165,16 @@ Check out Rob's [Navigate Chrome DevTools With Assistive Technology][28] to lear {% include 'partials/devtools/en/whats-new.md' %} [1]: /docs/devtools -[2]: https://developer.mozilla.org/en-US/docs/Web/CSS/filter +[2]: https://developer.mozilla.org/docs/Web/CSS/filter [3]: https://crbug.com/931145 [4]: https://developers.google.com/web/ilt/pwa/introduction-to-service-worker -[5]: https://developer.mozilla.org/en-US/docs/Web/API/Window/localStorage -[6]: https://developer.mozilla.org/en-US/docs/Web/API/Window/sessionStorage -[7]: https://developer.mozilla.org/en-US/docs/Web/API/IndexedDB_API +[5]: https://developer.mozilla.org/docs/Web/API/Window/localStorage +[6]: https://developer.mozilla.org/docs/Web/API/Window/sessionStorage +[7]: https://developer.mozilla.org/docs/Web/API/IndexedDB_API [8]: https://www.w3.org/TR/webdatabase/ -[9]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Cookies -[10]: https://developer.mozilla.org/en-US/docs/Web/API/Cache -[11]: https://developer.mozilla.org/en-US/docs/Web/HTML/Using_the_application_cache +[9]: https://developer.mozilla.org/docs/Web/HTTP/Cookies +[10]: https://developer.mozilla.org/docs/Web/API/Cache +[11]: https://developer.mozilla.org/docs/Web/HTML/Using_the_application_cache [12]: https://crbug.com/942503 [13]: https://crbug.com/943770 [14]: /docs/devtools/network diff --git a/site/en/blog/new-in-devtools-84/index.md b/site/en/blog/new-in-devtools-84/index.md index 6baec573bdc7..941f1e47afe1 100644 --- a/site/en/blog/new-in-devtools-84/index.md +++ b/site/en/blog/new-in-devtools-84/index.md @@ -171,7 +171,7 @@ Check out [Get things done quickly with app shortcuts][25] to learn more. [12]: https://web.dev/vitals/#core-web-vitals [13]: https://github.com/domenic/promises-unwrapping/blob/master/docs/states-and-fates.md [14]: https://bugs.chromium.org/p/v8/issues/detail?id=6751 -[15]: https://developer.mozilla.org/en-US/docs/Web/CSS/revert +[15]: https://developer.mozilla.org/docs/Web/CSS/revert [16]: https://crbug.com/1075437 [17]: https://crbug.com/1040019 [18]: https://drafts.csswg.org/css-color/#changes-from-3 diff --git a/site/en/blog/new-in-devtools-91/index.md b/site/en/blog/new-in-devtools-91/index.md index 39e82266ac9c..cde6ab940d1a 100644 --- a/site/en/blog/new-in-devtools-91/index.md +++ b/site/en/blog/new-in-devtools-91/index.md @@ -191,7 +191,7 @@ Chromium issue: [1186049](https://crbug.com/1186049) ### Support for new JavaScript features {: #javascript } DevTools now support the new [private brand check](https://v8.dev/features/private-brand-checks) JavaScript language feature, a.k.a `#foo in obj`. -This private brand checks feature extends the [in operator](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/in) to support the [private class fields](https://v8.dev/features/class-fields#private-class-fields) testing on any given object. +This private brand checks feature extends the [in operator](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Operators/in) to support the [private class fields](https://v8.dev/features/class-fields#private-class-fields) testing on any given object. Try it out in the **Console** and **Sources** panel. You can inspect the private fields in the **Scope** section under the **debugger** pane as well. diff --git a/site/en/blog/new-in-devtools-93/index.md b/site/en/blog/new-in-devtools-93/index.md index 5e2d9ad5a419..d6c84660b1ce 100644 --- a/site/en/blog/new-in-devtools-93/index.md +++ b/site/en/blog/new-in-devtools-93/index.md @@ -52,7 +52,7 @@ Chromium issue: [1182537](https://crbug.com/1182537) ## Attribution Reporting API debugging {: #attribution-reporting } Attribution Reporting API errors are now reported in the **Issues** tab. -[Attribution Reporting](https://developer.chrome.com/docs/privacy-sandbox/attribution-reporting/) is a new API to help you measure when a user action (such as an ad click or view) leads to a conversion, without using cross-site identifiers. +[Attribution Reporting](/docs/privacy-sandbox/attribution-reporting/) is a new API to help you measure when a user action (such as an ad click or view) leads to a conversion, without using cross-site identifiers. {% Img src="image/dPDCek3EhZgLQPGtEG3y0fTn4v82/bkEGVEv5kKc9M6qBUmLz.png", alt="Attribution Reporting API errors in the Issues tab", width="800", height="501" %} diff --git a/site/en/blog/new-in-devtools-95/index.md b/site/en/blog/new-in-devtools-95/index.md index 496f1d90029a..2d50ad49552e 100644 --- a/site/en/blog/new-in-devtools-95/index.md +++ b/site/en/blog/new-in-devtools-95/index.md @@ -78,7 +78,7 @@ link.access = 'admin'; link.search = `?access=${link.access}`; ``` -Try logging `link` in the **Console**. Own properties are now bold and sorted first. These changes make it easier to spot custom properties, especially for [Web APIs](https://developer.mozilla.org/en-US/docs/Web/API) (e.g. `URL`) with many inherited properties. +Try logging `link` in the **Console**. Own properties are now bold and sorted first. These changes make it easier to spot custom properties, especially for [Web APIs](https://developer.mozilla.org/docs/Web/API) (e.g. `URL`) with many inherited properties. {% Img src="image/dPDCek3EhZgLQPGtEG3y0fTn4v82/Ngjx6YRQsH3Fhl6DUZYl.png", alt="Own properties are bold and sorted first", width="800", height="561" %} diff --git a/site/en/blog/new-in-devtools-96/index.md b/site/en/blog/new-in-devtools-96/index.md index e7835202a10c..a5cba9f8f593 100644 --- a/site/en/blog/new-in-devtools-96/index.md +++ b/site/en/blog/new-in-devtools-96/index.md @@ -174,7 +174,7 @@ Chromium issues: [1232937](https://crbug.com/1232937), [1255586](https://crbug.c ## Deprecated Application cache pane in the Application panel {: #app-cache } -The [Application cache](https://developer.chrome.com/docs/devtools/storage/applicationcache/) pane in the Application panel is now removed as the support for [AppCache](https://web.dev/appcache-removal/) is removed from Chrome and other Chromium-based browsers. +The [Application cache](/docs/devtools/storage/applicationcache/) pane in the Application panel is now removed as the support for [AppCache](https://web.dev/appcache-removal/) is removed from Chrome and other Chromium-based browsers. {# https://chromium.googlesource.com/devtools/devtools-frontend/+/de4d15e955d6145674e3885cde8a5a70f1269b79 #} diff --git a/site/en/blog/origin-trial-troubleshooting/index.md b/site/en/blog/origin-trial-troubleshooting/index.md index dbe2ae236d35..cc06788fe5d6 100644 --- a/site/en/blog/origin-trial-troubleshooting/index.md +++ b/site/en/blog/origin-trial-troubleshooting/index.md @@ -134,7 +134,7 @@ available, despite the presence of a valid token. token. * **Expiry Time**: the maximum (latest) possible expiry date/time for the token, which will normally match the end of the trial. This is not the same as the Valid Until date for the token displayed -on your origin trial's My Registrations](https://developer.chrome.com/origintrials/#/trials/my) +on your origin trial's My Registrations](/origintrials/#/trials/my) page, which shows how long the token is currently valid for, and [can be extended](https://github.com/GoogleChrome/OriginTrials/blob/gh-pages/developer-guide.md#21-what-does-the-valid-until-date-mean-for-my-tokens). * **Usage Restriction**: Usage limits, which [can be set](https://github.com/GoogleChrome/OriginTrials/blob/gh-pages/developer-guide.md#20-what-are-the-options-for-usage-restrictions-on-tokens) for some trials. * **Third Party**: Whether [third-party matching](https://github.com/GoogleChrome/OriginTrials/blob/gh-pages/developer-guide.md#18-how-can-i-enable-an-experimental-feature-as-embedded-content-on-different-domains) @@ -192,7 +192,7 @@ Enrollment in an Edge origin trial won't enable a feature in Chrome. Access to trials is limited to specific versions of Chrome. In some cases, this may mean a trial feature is only available to pre-Stable Chrome channels: Canary, Dev and Beta. -You can check version availability from the [registration page](https://developer.chrome.com/origintrials/#/trials/active) +You can check version availability from the [registration page](/origintrials/#/trials/active) for the trial: {% Img src="image/80mq7dk16vVEg8BBhsVe42n6zn82/I6CRBeKSEhsqzAdQQvzm.png", alt="Chrome Origin Trials @@ -380,7 +380,7 @@ default to all users. more detail about trial timelines. {% endAside %} -You can check for active tokens on your Chrome Origin Trials [My Registrations page](https://developer.chrome.com/origintrials/#/trials/my): +You can check for active tokens on your Chrome Origin Trials [My Registrations page](/origintrials/#/trials/my): {% Img src="image/80mq7dk16vVEg8BBhsVe42n6zn82/XRSqveK1hiuOxAfJrKDx.png", alt="Chrome origin trials My Registrations page showing Valid Until date", width="800", height="612" %} @@ -390,7 +390,7 @@ Chrome DevTools displays Status `Success` if the token is still valid: {% Img src="image/80mq7dk16vVEg8BBhsVe42n6zn82/fO8LVqZb8Hv0kIg6HdK7.png", alt="Chrome DevTools origin trials information in the Application panel, highlighting Status: Success", width="800", height="424" %} -If your token has expired, DevTools will display Status `Expired` and your [My Registrations page](https://developer.chrome.com/origintrials/#/trials/my) for the trial will display an **Expired Tokens** section: +If your token has expired, DevTools will display Status `Expired` and your [My Registrations page](/origintrials/#/trials/my) for the trial will display an **Expired Tokens** section: {% Img src="image/80mq7dk16vVEg8BBhsVe42n6zn82/l61ghrJpV0SvwGlRbXlz.png", alt="Chrome origin trials My Registrations page showing expired tokens", width="800", height="591" %} @@ -398,7 +398,7 @@ My Registrations page showing expired tokens", width="800", height="591" %} ### The origin trial hasn't ended {: #trial-ended} -You can check the end date for an origin trial from its [registration page](https://developer.chrome.com/origintrials/#/trials/active): +You can check the end date for an origin trial from its [registration page](/origintrials/#/trials/active): {% Img src="image/80mq7dk16vVEg8BBhsVe42n6zn82/0f2Wdcfj3D3UwZmWx33S.png", alt="Chrome Origin Trials page for First Party Sets & SameParty with Trial Available details highlighted", width="800", height="737" %} @@ -473,7 +473,7 @@ A demo showing access to an origin trial feature in an iframe is available at ### Permissions policies are correctly configured {: #permissions-policies} -Some origin trial features may be affected by a [`Permissions-Policy`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Feature-Policy) +Some origin trial features may be affected by a [`Permissions-Policy`](https://developer.mozilla.org/docs/Web/HTTP/Headers/Feature-Policy) header (previously known as a `Feature-Policy` header). You can check for this in the [Intent to Experiment](https://groups.google.com/a/chromium.org/g/blink-dev/search?q=subject%3Aintent%20subject%3Ato%20subject%3Aexperiment) for the trial feature, or in developer documentation for the feature on [web.dev](https://web.dev) diff --git a/site/en/blog/origin-trials/index.md b/site/en/blog/origin-trials/index.md index b44b7198efed..cdd232c6125b 100644 --- a/site/en/blog/origin-trials/index.md +++ b/site/en/blog/origin-trials/index.md @@ -53,7 +53,7 @@ referred to as "reverse" origin trials. For example, [from Chrome 85](https://web.dev/appcache-removal/#origin-trial) AppCache is no longer available in Chrome by default. Sites needing extra time to migrate off AppCache could register for -the [deprecation trial to continue using AppCache](https://developer.chrome.com/origintrials/#/view_trial/1776670052997660673) until Chrome 93. +the [deprecation trial to continue using AppCache](/origintrials/#/view_trial/1776670052997660673) until Chrome 93. ## How to register for an origin trial diff --git a/site/en/blog/policy-update-kwspam-and-circumvention/index.md b/site/en/blog/policy-update-kwspam-and-circumvention/index.md index d0153255a7d9..03684545e7f2 100644 --- a/site/en/blog/policy-update-kwspam-and-circumvention/index.md +++ b/site/en/blog/policy-update-kwspam-and-circumvention/index.md @@ -37,7 +37,7 @@ high, and the experience for developers consistent: * Unnatural repetition of the same keyword more than 5 times * Unattributed or anonymous user testimonials in the product's description. -More guidance on the Keyword Spam policy can be found in our [FAQs](https://developer.chrome.com/docs/webstore/spam-faq/). +More guidance on the Keyword Spam policy can be found in our [FAQs](/docs/webstore/spam-faq/). ## Enforcement Circumvention diff --git a/site/en/blog/private-network-access-update/index.md b/site/en/blog/private-network-access-update/index.md index bbfb7f8498cb..785a949b2fb3 100644 --- a/site/en/blog/private-network-access-update/index.md +++ b/site/en/blog/private-network-access-update/index.md @@ -117,7 +117,7 @@ Chrome will allow the use of the deprecated feature for a limited amount of time. For more information, check out [Getting started with Chrome's origin -trials](https://developer.chrome.com/blog/origin-trials/) and the [web developer +trials](/blog/origin-trials/) and the [web developer guide to origin trials](https://github.com/GoogleChrome/OriginTrials/blob/gh-pages/developer-guide.md) for instructions. @@ -159,7 +159,7 @@ the circumstances of each affected website. First, register for the "Private Network Access from non-secure contexts" trial using [the web developers -console](https://developer.chrome.com/origintrials/#/view_trial/4081387162304512001), +console](/origintrials/#/view_trial/4081387162304512001), and obtain a trial token for each affected origin. Then configure your web servers to attach the origin-specific `Origin-Trial: $token` header on responses. Note that this header need only be set on main resource and diff --git a/site/en/blog/progress-in-the-privacy-sandbox-2021-08/index.md b/site/en/blog/progress-in-the-privacy-sandbox-2021-08/index.md index 58639a60ac05..4e76064f6c1c 100644 --- a/site/en/blog/progress-in-the-privacy-sandbox-2021-08/index.md +++ b/site/en/blog/progress-in-the-privacy-sandbox-2021-08/index.md @@ -163,7 +163,7 @@ enable cross-site tracking. ### FLoC -[FLoC](https://developer.chrome.com/docs/privacy-sandbox/floc/) is a proposal to +[FLoC](/docs/privacy-sandbox/floc/) is a proposal to enable interest-based advertising **without** the need for individual cross-site tracking. The **origin trial for the first version of FLoC ended in mid-July** and we are evaluating improvements for the next version of FLoC before advancing @@ -197,13 +197,13 @@ ads. ### Attribution Reporting The core [**Attribution Reporting -API**](https://developer.chrome.com/docs/privacy-sandbox/attribution-reporting/) +API**](/docs/privacy-sandbox/attribution-reporting/) has been in origin trial since the end of 2020, under the name Event-Level Conversion Measurement API. There were a number of API changes from Chrome 92—we've published a [guide for migrating from Conversion Measurement API to Attribution Reporting -API](https://developer.chrome.com/docs/privacy-sandbox/attribution-reporting-migration/)—and +API](/docs/privacy-sandbox/attribution-reporting-migration/)—and we're also [**extending the trial** period through to Chrome 93 stable](https://groups.google.com/a/chromium.org/g/blink-dev/c/xCWP1ltlAgw). We have also extended the "Discussion" phase [on the @@ -217,7 +217,7 @@ data) defined by an adtech. Later, the browser sends the resulting reports to a predefined endpoint, with some delay and noise.", width="800", height="521" %} We've published an [**introduction to Attribution -Reporting**](https://developer.chrome.com/docs/privacy-sandbox/attribution-reporting-introduction/) +Reporting**](/docs/privacy-sandbox/attribution-reporting-introduction/) and [**video overview**](https://youtu.be/UGA74CIcom8) to cover how the API works, the main use cases, API implementation status, and how it compares with third-party cookies. @@ -242,7 +242,7 @@ overview** of the Trust Tokens API](https://youtu.be/bXB1Iwq6Eq4). {% YouTube id='bXB1Iwq6Eq4' %} The [**origin trial** for **Trust -Tokens**](https://developer.chrome.com/origintrials/#/view_trial/2479231594867458049) +Tokens**](/origintrials/#/view_trial/2479231594867458049) has been open since Chrome 84 and is planned to run through to Chrome 94, so there is still time to experiment on your sites. diff --git a/site/en/blog/progress-in-the-privacy-sandbox-2021-09/index.md b/site/en/blog/progress-in-the-privacy-sandbox-2021-09/index.md index ce29d840d762..fcec54eae2da 100644 --- a/site/en/blog/progress-in-the-privacy-sandbox-2021-09/index.md +++ b/site/en/blog/progress-in-the-privacy-sandbox-2021-09/index.md @@ -52,7 +52,7 @@ enables fingerprinting or covert tracking of users. We shared the full [timeline for reducing Chrome's **user-agent**](https://blog.chromium.org/2021/09/user-agent-reduction-origin-trial-and-dates.html) information and opened registration for the [**early opt-in origin -trial**](https://developer.chrome.com/blog/user-agent-reduction-origin-trial/) +trial**](/blog/user-agent-reduction-origin-trial/) for the new format. The end result retains the same string format to minimise compatibility issues, @@ -119,7 +119,7 @@ timeline and we'll have more docs and demos ready for you soon. If you set cookies for cross-site contexts, but only across sites you own—like you host a service on your .com that's used by your .co.uk—then you should follow [**First-Party -Sets**](https://developer.chrome.com/docs/privacy-sandbox/first-party-sets/). +Sets**](/docs/privacy-sandbox/first-party-sets/). This proposal defines a way of declaring which sites you want to form a set and then marking cookies as "SameParty" so that they are only sent for contexts inside of that set. @@ -134,7 +134,7 @@ flags and we'll update the docs as work progresses. We're also continuing to improve **DevTools** functionality for much of this early testing. You can now see origin trial status, upcoming deprecations, and raw cookie header values. There's more detail from Jecelyn on [What's New In -DevTools (Chrome 94)](https://developer.chrome.com/blog/new-in-devtools-94/). +DevTools (Chrome 94)](/blog/new-in-devtools-94/). {% Img src="image/dPDCek3EhZgLQPGtEG3y0fTn4v82/PbozcNJRd6rTME5hhqIq.png", alt="DevTools screenshot showing the raw Set-Cookie header for a cookie with an @@ -155,7 +155,7 @@ available for wider testing by sometime in Q1 2022. ### FLoC -[**FLoC**](https://developer.chrome.com/docs/privacy-sandbox/floc/) is a +[**FLoC**](/docs/privacy-sandbox/floc/) is a proposal to enable interest-based advertising without the need for individual cross-site tracking. The origin trial for the first version of FLoC ended in mid-July and we are evaluating improvements for the next version of FLoC before @@ -165,7 +165,7 @@ clean up. ### FLEDGE -[**FLEDGE**](https://developer.chrome.com/docs/privacy-sandbox/fledge/) is an +[**FLEDGE**](/docs/privacy-sandbox/fledge/) is an initial experiment in enabling remarketing use cases, showing ads based on the user's previous interactions with the advertiser's site, but without third-party tracking. @@ -178,7 +178,7 @@ explaining the concepts in more detail. {% YouTube id='HkvmYKqnytw' %} FLEDGE is [available via CLI -flags](https://developer.chrome.com/docs/privacy-sandbox/fledge/#:~:text=---,enable-features,-%3DFledgeInterestGroups%2CFledgeInterestGroupAPI) +flags](/docs/privacy-sandbox/fledge/#:~:text=---,enable-features,-%3DFledgeInterestGroups%2CFledgeInterestGroupAPI) for early developer testing (as opposed to scaled user testing) and we're updating the timeline to make these flags more visible. The feature is under active development, so you should run against a Canary or Dev build of Chrome to @@ -195,7 +195,7 @@ ads. ### Attribution Reporting API The [**Attribution Reporting -API**](https://developer.chrome.com/docs/privacy-sandbox/attribution-reporting/) +API**](/docs/privacy-sandbox/attribution-reporting/) enables functionality to measure events on one site, like clicking or viewing an ad, that lead to a conversion on another site—again, all without being able to track the individual on that cross-site journey. @@ -218,7 +218,7 @@ DevTools has added Issue support for the Attribution Reporting API. Common issues that may block source or report registration and prevent you from receiving reports will now appear along with tips on how to fix them. See [What's New In DevTools (Chrome -93)](https://developer.chrome.com/blog/new-in-devtools-93/#attribution-reporting) +93)](/blog/new-in-devtools-93/#attribution-reporting) for more details. ## Fight spam and fraud on the web @@ -230,7 +230,7 @@ protection. We need privacy-preserving alternatives here as well. ### Trust Tokens The [**Trust Token** -API](https://developer.chrome.com/docs/privacy-sandbox/trust-tokens/) is a +API](/docs/privacy-sandbox/trust-tokens/) is a proposal that allows one site to share a claim about a visitor—such as "I think they're human"—and enable other sites to verify that claim, again without identifying the individual. @@ -240,7 +240,7 @@ from the ecosystem feedback that more testing time is required here. As such, we've applied to extend the [**Trust Token origin trial**](https://groups.google.com/a/chromium.org/g/blink-dev/c/fpfbKgJF8Vc/m/lHcBFfxkBAAJ) through to Chrome 101. [Registration for the origin -trial](https://developer.chrome.com/origintrials/#/register_trial/2479231594867458049) +trial](/origintrials/#/register_trial/2479231594867458049) is available on the origin trials site. ## Feedback @@ -252,7 +252,7 @@ Twitter](https://twitter.com/ChromiumDev) if there's anything that we could improve in this series, we'll use your input to continue improving the format. We have also added an [**Privacy Sandbox FAQ** -section](https://developer.chrome.com/docs/privacy-sandbox/faq/) which we will +section](/docs/privacy-sandbox/faq/) which we will continue to expand based on the issues you submit to the [developer support repo](https://github.com/GoogleChromeLabs/privacy-sandbox-dev-support). If you have any questions around testing or implementation on any of the proposals, diff --git a/site/en/blog/progress-in-the-privacy-sandbox-2021-10/index.md b/site/en/blog/progress-in-the-privacy-sandbox-2021-10/index.md index bb86851e8760..8669f700dbdd 100644 --- a/site/en/blog/progress-in-the-privacy-sandbox-2021-10/index.md +++ b/site/en/blog/progress-in-the-privacy-sandbox-2021-10/index.md @@ -93,7 +93,7 @@ change as discussion progresses. The Federated Credentials Management API overlaps with and builds on some of the functionality already present in the [Credential Management -API](https://developer.mozilla.org/en-US/docs/Web/API/Credential_Management_API). +API](https://developer.mozilla.org/docs/Web/API/Credential_Management_API). {% endAside %} @@ -217,7 +217,7 @@ conversion on another site—without enabling cross-site tracking. We would like to continue testing the Attribution Reporting API and we plan on **[extending the origin -trial](https://developer.chrome.com/origintrials/#/view_trial/3411476717733150721)** +trial](/origintrials/#/view_trial/3411476717733150721)** through to Chrome 97. Current origin trial tokens expired on October 12th, so you will need to apply for updated tokens to continue testing. diff --git a/site/en/blog/pwa-install-features/index.md b/site/en/blog/pwa-install-features/index.md index 9b205b6f8871..c4f994cbb345 100644 --- a/site/en/blog/pwa-install-features/index.md +++ b/site/en/blog/pwa-install-features/index.md @@ -168,7 +168,7 @@ Richer Install UI, collapsed and expanded states. -Earlier this year, we launched [Richer Install](https://developer.chrome.com/blog/richer-pwa-installation/), +Earlier this year, we launched [Richer Install](/blog/richer-pwa-installation/), an extended install UI on Chrome on Android that allows developers to add screenshots to their manifest. Developers can also add a description, which is recommended but not necessary. Due to this diff --git a/site/en/blog/renderingng-architecture/index.md b/site/en/blog/renderingng-architecture/index.md index 2f121124ff5c..d9222a080057 100644 --- a/site/en/blog/renderingng-architecture/index.md +++ b/site/en/blog/renderingng-architecture/index.md @@ -151,7 +151,7 @@ I'll write "always" below, but this caveat applies throughout.) Multiple browser tabs or windows of the same site usually go in different render processes, -unless the tabs are related (one [opening](https://developer.mozilla.org/en-US/docs/Web/API/Window/opener) +unless the tabs are related (one [opening](https://developer.mozilla.org/docs/Web/API/Window/opener) the other). Under strong memory pressure on desktop Chromium may put multiple tabs from the same site into the same render process even if not related. @@ -205,7 +205,7 @@ width="800", height="556" %} - The _main thread_ runs scripts, the rendering event loop, the document lifecycle, hit testing, script event dispatching, and parsing of HTML, CSS and other data formats. - _Main thread helpers_ perform tasks such as creating image bitmaps and blobs that require encoding or decoding. - - _[Web Workers](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API)_ + - _[Web Workers](https://developer.mozilla.org/docs/Web/API/Web_Workers_API)_ run script, and a rendering event loop for OffscreenCanvas. - The _Compositor thread_ processes input events, performs scrolling and animations of web content, diff --git a/site/en/blog/renderingng-data-structures/index.md b/site/en/blog/renderingng-data-structures/index.md index 54c9ad8784fd..987f4cba39bd 100644 --- a/site/en/blog/renderingng-data-structures/index.md +++ b/site/en/blog/renderingng-data-structures/index.md @@ -206,7 +206,7 @@ this is very similar to how as it was built initially in a similar way as a text editor. The flat list is created for each -[inline formatting context](https://developer.mozilla.org/en-US/docs/Web/CSS/Inline_formatting_context) +[inline formatting context](https://developer.mozilla.org/docs/Web/CSS/Inline_formatting_context) in the order of a depth-first search of its inline layout subtree. Each entry in the list is a tuple of (object, number of descendants). For example, consider this DOM: @@ -251,8 +251,8 @@ The flat list looks like this: There are many consumers of this data structure: accessibility APIs, and geometry APIs such as -[getClientRects](https://developer.mozilla.org/en-US/docs/Web/API/Range/getClientRects), -and [contenteditable](https://developer.mozilla.org/en-US/docs/Web/API/HTMLElement/contentEditable). +[getClientRects](https://developer.mozilla.org/docs/Web/API/Range/getClientRects), +and [contenteditable](https://developer.mozilla.org/docs/Web/API/HTMLElement/contentEditable). Each has different requirements. These components access the flat data structure through a convenience cursor. @@ -314,7 +314,7 @@ RenderingNG uses property trees for many purposes, including: - Separating compositing from paint, and compositing from the main thread. - Determining an optimal compositing / draw strategy. - Measuring -[IntersectionObserver](https://developer.mozilla.org/en-US/docs/Web/API/Intersection_Observer_API) +[IntersectionObserver](https://developer.mozilla.org/docs/Web/API/Intersection_Observer_API) geometry. - Avoiding work for offscreen elements and GPU texture tiles. - Efficiently and accurately invalidating paint and raster. @@ -326,12 +326,12 @@ Every web document has four separate property trees: transform, clip, effect, an The transform tree represents CSS transforms and scrolling. (A scroll transform is represented as a 2D transform matrix.) The clip tree represents -[overflow clips](https://developer.mozilla.org/en-US/docs/Web/CSS/overflow). +[overflow clips](https://developer.mozilla.org/docs/Web/CSS/overflow). The effect tree represents all other visual effects: opacity, filters, masks, blend modes, and other kinds of clips such as clip-path. The scroll tree represents information about scrolling, such as how scrolls -[chain](https://developer.mozilla.org/en-US/docs/Web/CSS/overscroll-behavior) together; +[chain](https://developer.mozilla.org/docs/Web/CSS/overscroll-behavior) together; it is needed to perform scrolling on the compositor thread. Each node in a property tree represents a scroll or visual effect applied by a DOM element. If it happens to have multiple effects, @@ -406,7 +406,7 @@ width="800", height="1162" %} {% Aside %} There are several more complexities that I have omitted from this diagram, such as nodes representing the -[visual viewport](https://developer.mozilla.org/en-US/docs/Web/API/Visual_Viewport_API) +[visual viewport](https://developer.mozilla.org/docs/Web/API/Visual_Viewport_API) and nodes used for engine-internal performance optimizations, such as [paint offset and isolation](https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/core/paint/object_paint_properties.h;l=96). diff --git a/site/en/blog/shared-element-transitions-for-spas/index.md b/site/en/blog/shared-element-transitions-for-spas/index.md index 4a6c231a9b6b..7a38b079deb8 100644 --- a/site/en/blog/shared-element-transitions-for-spas/index.md +++ b/site/en/blog/shared-element-transitions-for-spas/index.md @@ -54,7 +54,7 @@ Origin trials allow you to try new features and give feedback on their usability ### Register for the origin trial -1. [Request a token](https://developer.chrome.com/origintrials/#/view_trial/451485862643892225) for your origin. +1. [Request a token](/origintrials/#/view_trial/451485862643892225) for your origin. 2. Add the token to your pages. There are two ways to do that: - Add an origin-trial `` tag to the head of each page. For example, this may look something like: @@ -164,7 +164,7 @@ The elements don't need to be the same node. In this case, `element2` will trans **Shared transition elements must have [`contain: paint`](https://web.dev/content-visibility/#containment).** This makes it difficult to transition elements that have paint effects outside their content rectangle, such as shadows, blurs, and outlines. Hopefully this will change in future. -**Shared transition elements cannot have background effects.** Things like [`mix-blend-mode`](https://developer.mozilla.org/en-US/docs/Web/CSS/mix-blend-mode) and [`backdrop-filter`](https://developer.mozilla.org/en-US/docs/Web/CSS/backdrop-filter) won't interact correctly with the background during a transition. +**Shared transition elements cannot have background effects.** Things like [`mix-blend-mode`](https://developer.mozilla.org/docs/Web/CSS/mix-blend-mode) and [`backdrop-filter`](https://developer.mozilla.org/docs/Web/CSS/backdrop-filter) won't interact correctly with the background during a transition. **Control over the transition is limited.** Right now, when one element transitions to another, their "screenshots" quickly cross-fade while they scale and translate into position. Future versions of the API will add additional configuration, but this will always be limited to things that can be done with a screenshot of state, such as transforms, opacity, and crops. diff --git a/site/en/blog/timer-throttling-in-chrome-88/index.md b/site/en/blog/timer-throttling-in-chrome-88/index.md index 61371c53d562..bbe70c4bbaeb 100644 --- a/site/en/blog/timer-throttling-in-chrome-88/index.md +++ b/site/en/blog/timer-throttling-in-chrome-88/index.md @@ -29,7 +29,7 @@ Generally, _hidden_ means a different tab is active, or the window has been minimized, but browsers may consider a page hidden whenever its content is totally not-visible. Some browsers go further than others here, but you can always use the [page visibility -API](https://developer.mozilla.org/en-US/docs/Web/API/Page_Visibility_API) to +API](https://developer.mozilla.org/docs/Web/API/Page_Visibility_API) to track when the browser thinks visibility has changed. ### JavaScript timers @@ -131,18 +131,18 @@ checking. Look to see if there's an event that achieves the same thing. Some examples: - If you need to know when an element enters in the viewport, use - [`IntersectionObserver`](https://developer.mozilla.org/en-US/docs/Web/API/Intersection_Observer_API). + [`IntersectionObserver`](https://developer.mozilla.org/docs/Web/API/Intersection_Observer_API). - If you need to know when an element changes size, use [`ResizeObserver`](https://web.dev/resize-observer/). - If you need to know when the DOM changes, use - [`MutationObserver`](https://developer.mozilla.org/en-US/docs/Web/API/MutationObserver), + [`MutationObserver`](https://developer.mozilla.org/docs/Web/API/MutationObserver), or maybe [custom element lifecycle - callbacks](https://developer.mozilla.org/en-US/docs/Web/Web_Components/Using_custom_elements). + callbacks](https://developer.mozilla.org/docs/Web/Web_Components/Using_custom_elements). - Rather than poll a server, consider [web - sockets](https://developer.mozilla.org/en-US/docs/Web/API/WebSockets_API), + sockets](https://developer.mozilla.org/docs/Web/API/WebSockets_API), [server-sent - events](https://developer.mozilla.org/en-US/docs/Web/API/EventSource), [push - messages](https://developer.mozilla.org/en-US/docs/Web/API/Push_API), or + events](https://developer.mozilla.org/docs/Web/API/EventSource), [push + messages](https://developer.mozilla.org/docs/Web/API/Push_API), or [fetch streams](https://web.dev/fetch-upload-streaming/#previously-on-the-exciting-adventures-of-fetch-streams). - If you need to react to stage changes in audio/video, [use events like @@ -158,7 +158,7 @@ you want to show a notification at a particular time. Animation is a visual thing, so it shouldn't use CPU time when the page is _hidden_. -[`requestAnimationFrame`](https://developer.mozilla.org/en-US/docs/Web/API/window/requestAnimationFrame) +[`requestAnimationFrame`](https://developer.mozilla.org/docs/Web/API/window/requestAnimationFrame) is much better at scheduling animation work than JavaScript timers. It synchronizes with the refresh rate of the device, ensuring you only get one callback per displayable frame, and you get the maximum amount of time to @@ -166,9 +166,9 @@ construct that frame. Also, `requestAnimationFrame` will wait for the page to be visible, so it doesn't use any CPU when the page is hidden. If you can declare your whole animation up-front, consider using [CSS -animations](https://developer.mozilla.org/en-US/docs/Web/CSS/animation) or the +animations](https://developer.mozilla.org/docs/Web/CSS/animation) or the [web animations -API](https://developer.mozilla.org/en-US/docs/Web/API/Web_Animations_API). These +API](https://developer.mozilla.org/docs/Web/API/Web_Animations_API). These have the same advantages as `requestAnimationFrame`, but the browser can perform additional optimizations like automatic compositing, and they're generally easier to use. diff --git a/site/en/blog/user-agent-reduction-origin-trial/index.md b/site/en/blog/user-agent-reduction-origin-trial/index.md index cb0ff2ba1be5..1ee75c0efe89 100644 --- a/site/en/blog/user-agent-reduction-origin-trial/index.md +++ b/site/en/blog/user-agent-reduction-origin-trial/index.md @@ -19,7 +19,7 @@ tags: User-Agent Reduction is an effort to reduce passive fingerprinting surfaces by reducing the information in the -[User-Agent](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/User-Agent) +[User-Agent](https://developer.mozilla.org/docs/Web/HTTP/Headers/User-Agent) (UA) string to only the browser's brand and significant version, its desktop or mobile distinction, and the platform it's running on. Currently, the UA string is shared on every HTTP request and exposed in JavaScript to all resources @@ -31,7 +31,7 @@ information that they need. Beginning with the [Chrome 95](https://chromiumdash.appspot.com/schedule) Beta, we'll open up the -[origin trial](https://developer.chrome.com/origintrials/#/view_trial/-7123568710593282047) +[origin trial](/origintrials/#/view_trial/-7123568710593282047) for [User-Agent Reduction](https://blog.chromium.org/2021/09/user-agent-reduction-origin-trial-and-dates.html) to allow sites to opt into receiving the reduced UA string now. This will enable @@ -50,7 +50,7 @@ repository](https://github.com/abeyad/user-agent-reduction/issues). ## What is the User-Agent? The -[User-Agent](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/User-Agent) +[User-Agent](https://developer.mozilla.org/docs/Web/HTTP/Headers/User-Agent) (UA) string is shared on every HTTP request and exposed in JavaScript to all resources loaded by the browser. Currently, it contains significant information on the browser and the platform it's running on. @@ -107,7 +107,7 @@ provided that the permissions policy allows it. 1. To register for the origin trial and get a token for your domains, visit the - [Trial for User Agent Reduction page](https://developer.chrome.com/origintrials/#/view_trial/-7123568710593282047). + [Trial for User Agent Reduction page](/origintrials/#/view_trial/-7123568710593282047). 1. Update your HTTP response headers: @@ -140,7 +140,7 @@ can participate in the origin trial without requiring the top-level site to be enrolled. To enroll as a third-party embed, follow the same steps as for a [top-level site](#enroll-top-level), -except when [registering for an origin trial token](https://developer.chrome.com/origintrials/#/view_trial/-7123568710593282047), +except when [registering for an origin trial token](/origintrials/#/view_trial/-7123568710593282047), select the third-party token checkbox. Some important points about running the origin trial on third-party embeds: diff --git a/site/en/blog/wasm-module-sharing-restricted-to-same-origin/index.md b/site/en/blog/wasm-module-sharing-restricted-to-same-origin/index.md index b19be1f97c47..ad2d73dbd155 100644 --- a/site/en/blog/wasm-module-sharing-restricted-to-same-origin/index.md +++ b/site/en/blog/wasm-module-sharing-restricted-to-same-origin/index.md @@ -64,7 +64,7 @@ origin clusters: or [`WebAssembly.Memory`](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/WebAssembly/Memory) objects to other same-site cross-origin pages. This is [already in place since - Chrome 92](https://developer.chrome.com/blog/enabling-shared-array-buffer/). + Chrome 92](/blog/enabling-shared-array-buffer/). * You can no longer send [`WebAssembly.Module`](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/WebAssembly/Module) objects to other same-site cross-origin pages via `postMessage()`. This change diff --git a/site/en/blog/webauthn-tab/index.md b/site/en/blog/webauthn-tab/index.md index da6e4ee4de8e..da299395bf81 100644 --- a/site/en/blog/webauthn-tab/index.md +++ b/site/en/blog/webauthn-tab/index.md @@ -16,7 +16,7 @@ tags: {% include 'partials/devtools/en/banner.md' %} -The [Web Authentication API](https://developer.mozilla.org/en-US/docs/Web/API/Web_Authentication_API), also known as **WebAuthn**, allows servers to use public key cryptography - rather than passwords - to register and authenticate users. It does this by enabling integration between these servers and strong authenticators. These authenticators may be dedicated physical devices (e.g. security keys) or integrated with platforms (e.g. fingerprint readers). You can read more about WebAuthn here at [webauthn.guide](https://webauthn.guide/). +The [Web Authentication API](https://developer.mozilla.org/docs/Web/API/Web_Authentication_API), also known as **WebAuthn**, allows servers to use public key cryptography - rather than passwords - to register and authenticate users. It does this by enabling integration between these servers and strong authenticators. These authenticators may be dedicated physical devices (e.g. security keys) or integrated with platforms (e.g. fingerprint readers). You can read more about WebAuthn here at [webauthn.guide](https://webauthn.guide/). ## Developer pain points diff --git a/site/en/docs/_example/my-first-doc/index.md b/site/en/docs/_example/my-first-doc/index.md index 5e45fb3f38f3..7e9b595eea09 100644 --- a/site/en/docs/_example/my-first-doc/index.md +++ b/site/en/docs/_example/my-first-doc/index.md @@ -48,8 +48,8 @@ A few rules: - Don't forget to add your new doc to the `_data/docs/[project-name]/toc.yml` or else it won't show up in the site navigation! - Make sure authors appear in the `authorsData.json` file and that they have - uploaded a headshot to our image CDN. See [How to add an author](https://developer.chrome.com/docs/handbook/how-to/add-an-author/). -- Make sure tags have been added to `tags.yml`. See [How to add a tag](https://developer.chrome.com/docs/handbook/how-to/add-a-tag/). + uploaded a headshot to our image CDN. See [How to add an author](/docs/handbook/how-to/add-an-author/). +- Make sure tags have been added to `tags.yml`. See [How to add a tag](/docs/handbook/how-to/add-a-tag/). - Code blocks should use triple backticks and include a language name. Example: ```html diff --git a/site/en/docs/android/custom-tabs/headers/index.md b/site/en/docs/android/custom-tabs/headers/index.md index 2e6cddc0415d..6a6de36cb248 100644 --- a/site/en/docs/android/custom-tabs/headers/index.md +++ b/site/en/docs/android/custom-tabs/headers/index.md @@ -207,7 +207,7 @@ allowed only for clients and servers of the same origin, verified by a digital a [3]: /docs/android/custom-tabs/ [4]: https://fetch.spec.whatwg.org/#cors-safelisted-request-header [5]: https://developers.google.com/digital-asset-links/v1/getting-started -[6]: https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS +[6]: https://developer.mozilla.org/docs/Web/HTTP/CORS [7]: https://fetch.spec.whatwg.org/#cors-safelisted-request-header [8]: /docs/android/custom-tabs/ [9]: https://developer.android.com/reference/android/provider/Browser#EXTRA_HEADERS diff --git a/site/en/docs/android/trusted-web-activity/query-parameters/index.md b/site/en/docs/android/trusted-web-activity/query-parameters/index.md index ba0045064151..d223ad864613 100644 --- a/site/en/docs/android/trusted-web-activity/query-parameters/index.md +++ b/site/en/docs/android/trusted-web-activity/query-parameters/index.md @@ -146,7 +146,7 @@ We believe existing or upcoming Web Platform APIs enable most use cases needed b you are looking for new or upcoming Web APIs, check out the [New Capabilities status page][7]. [1]: https://developers.google.com/web/tools/lighthouse/audits/noopener -[2]: https://developer.mozilla.org/en-US/docs/Web/API/Location +[2]: https://developer.mozilla.org/docs/Web/API/Location [3]: https://github.com/GoogleChromeLabs/bubblewrap/issues [4]: https://github.com/GoogleChromeLabs/bubblewrap [5]: https://www.npmjs.com/package/@bubblewrap/cli diff --git a/site/en/docs/android/trusted-web-activity/quick-start/index.md b/site/en/docs/android/trusted-web-activity/quick-start/index.md index 3d853a30b40f..d37b03f2fbd9 100644 --- a/site/en/docs/android/trusted-web-activity/quick-start/index.md +++ b/site/en/docs/android/trusted-web-activity/quick-start/index.md @@ -69,7 +69,7 @@ Initializing an Android project that wraps a PWA is done by running the init com bubblewrap init --manifest=https://my-twa.com/manifest.json ``` -Bubblewrap will read the [Web Manifest](https://developer.mozilla.org/en-US/docs/Web/Manifest), +Bubblewrap will read the [Web Manifest](https://developer.mozilla.org/docs/Web/Manifest), ask developers to confirm values to be used in the Android project, and generate the project using those values. Once the project has been generated, generate an APK by running: diff --git a/site/en/docs/android/trusted-web-activity/whats-new/index.md b/site/en/docs/android/trusted-web-activity/whats-new/index.md index 14cab1a5af9c..f7e8a71241a5 100644 --- a/site/en/docs/android/trusted-web-activity/whats-new/index.md +++ b/site/en/docs/android/trusted-web-activity/whats-new/index.md @@ -412,7 +412,7 @@ release. [3]: https://developer.android.com/training/system-ui/immersive [4]: https://developer.android.com/guide/app-bundle [5]: https://android-developers.googleblog.com/2020/08/recent-android-app-bundle-improvements.html -[6]: https://developer.mozilla.org/en-US/docs/Web/API/Geolocation_API +[6]: https://developer.mozilla.org/docs/Web/API/Geolocation_API [7]: https://blog.chromium.org/2020/06/changes-to-quality-criteria-for-pwas.html [8]: /docs/android/trusted-web-activity/integration-guide#link-site-to-app [9]: https://developers.google.com/web/tools/workbox diff --git a/site/en/docs/apps/app_bluetooth/index.md b/site/en/docs/apps/app_bluetooth/index.md index 0b9345573638..8433dfa12aac 100644 --- a/site/en/docs/apps/app_bluetooth/index.md +++ b/site/en/docs/apps/app_bluetooth/index.md @@ -761,7 +761,7 @@ apps to write to this descriptor. Apps should instead use the [33]: /docs/extensions/reference/bluetoothSocket#method-create [34]: /docs/extensions/reference/bluetooth/#method-getDevice [35]: /docs/extensions/reference/bluetoothSocket#method-send -[36]: https://developer.mozilla.org/en-US/docs/JavaScript_typed_arrays +[36]: https://developer.mozilla.org/docs/JavaScript_typed_arrays [37]: https://updates.html5rocks.com/2012/06/How-to-convert-ArrayBuffer-to-and-from-String [38]: /docs/extensions/reference/bluetoothSocket#method-send [39]: /docs/extensions/reference/bluetoothSocket#event-onReceive diff --git a/site/en/docs/apps/app_codelab_filesystem/index.md b/site/en/docs/apps/app_codelab_filesystem/index.md index f63050faf3d3..97f2b5cd4835 100644 --- a/site/en/docs/apps/app_codelab_filesystem/index.md +++ b/site/en/docs/apps/app_codelab_filesystem/index.md @@ -265,9 +265,9 @@ Ready to continue onto the next step? Go to [Step 7 - Publish your app »][26] [4]: #launch [5]: /apps/fileSystem#method-chooseEntry [6]: /apps/fileSystem#method-getDisplayPath -[7]: https://developer.mozilla.org/en-US/docs/Web/API/Blob +[7]: https://developer.mozilla.org/docs/Web/API/Blob [8]: http://www.html5rocks.com/en/tutorials/file/filesystem/ -[9]: https://developer.mozilla.org/en-US/docs/Web/API/FileEntry +[9]: https://developer.mozilla.org/docs/Web/API/FileEntry [10]: /apps/fileSystem#method-restoreEntry [11]: /apps/fileSystem#method-retainEntry [12]: diff --git a/site/en/docs/apps/app_codelab_images/index.md b/site/en/docs/apps/app_codelab_images/index.md index 0ec71fa3a589..3263480b366f 100644 --- a/site/en/docs/apps/app_codelab_images/index.md +++ b/site/en/docs/apps/app_codelab_images/index.md @@ -220,9 +220,9 @@ Ready to continue onto the next step? Go to [Step 6 - Export todos to the filesy [2]: /apps/migration [3]: https://github.com/mangini/io13-codelab/archive/master.zip [4]: #launch -[5]: https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest -[6]: https://developer.mozilla.org/en-US/docs/Web/API/Blob -[7]: https://developer.mozilla.org/en-US/docs/Web/API/URL.createObjectURL +[5]: https://developer.mozilla.org/docs/Web/API/XMLHttpRequest +[6]: https://developer.mozilla.org/docs/Web/API/Blob +[7]: https://developer.mozilla.org/docs/Web/API/URL.createObjectURL [8]: https://github.com/GoogleChrome/apps-resource-loader#readme [9]: /apps/contentSecurityPolicy "Read 'Content Security Policy' in the Chrome developer docs" [10]: diff --git a/site/en/docs/apps/app_codelab_import_todomvc/index.md b/site/en/docs/apps/app_codelab_import_todomvc/index.md index ada60d0e4105..bf506a58c962 100644 --- a/site/en/docs/apps/app_codelab_import_todomvc/index.md +++ b/site/en/docs/apps/app_codelab_import_todomvc/index.md @@ -727,7 +727,7 @@ Ready to continue onto the next step? Go to [Step 3 - Add alarms and notificatio [13]: /docs/extensions/reference/storage#method-StorageArea-get "Read 'chrome.storage.local.get()' in the Chrome developer docs" -[14]: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Function/bind +[14]: https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Function/bind [15]: http://en.wikipedia.org/wiki/Hazard_(computer_architecture)#Read_After_Write_.28RAW.29 [16]: /docs/extensions/reference/storage#method-StorageArea-remove [17]: /apps/contentSecurityPolicy "Read 'Content Security Policy' in the Chrome developer docs" diff --git a/site/en/docs/apps/app_network/index.md b/site/en/docs/apps/app_network/index.md index 88869b00ba8a..c5dc0193bc46 100644 --- a/site/en/docs/apps/app_network/index.md +++ b/site/en/docs/apps/app_network/index.md @@ -262,7 +262,7 @@ chrome.sockets.tcpServer.disconnect(serverSocketId); [11]: /apps/sockets.tcp#method-connect [12]: /apps/sockets.tcp#method-send [13]: /apps/sockets.tcp#event-onReceive -[14]: https://developer.mozilla.org/en-US/docs/JavaScript_typed_arrays +[14]: https://developer.mozilla.org/docs/JavaScript_typed_arrays [15]: http://updates.html5rocks.com/2012/06/How-to-convert-ArrayBuffer-to-and-from-String [16]: /apps/sockets.tcp#method-disconnect [17]: /apps/sockets.udp#method-send diff --git a/site/en/docs/apps/migration/index.md b/site/en/docs/apps/migration/index.md index 5fc304b0ccf1..e86577940382 100644 --- a/site/en/docs/apps/migration/index.md +++ b/site/en/docs/apps/migration/index.md @@ -66,7 +66,7 @@ application for a better experience. Chrome App API/Capability migration recommendations (current as of Nov. 2019): -
Chrome App feature/functionalityWeb platform migration recommendationsAndroid migration recommendationsExtension migration recommendations
chrome.accessibilityFeatureschrome.accessibilityFeatures
chrome.alarmsNotification TriggersWorkManagerchrome.alarms
chrome.app.runtimeLaunch EventActivity Lifecycle
chrome.app.runtime.onRestartedPage Life CycleActivity.onResume
chrome.app.windowWindow Placement / Screen Enumerationchrome.windows
chrome.audioAudio Device ClientSome Audio APIs
chrome.bluetoothWeb Bluetooth APIBluetooth API
chrome.bluetoothLowEnergyWeb Bluetooth APIBTLE
chrome.bluetoothSocketWeb Bluetooth APIBluetooth Socket
chrome.browserwindow.openIntent system
chrome.commandsUI EventsHard-code keyboard commandschrome.commands
chrome.contextMenus(HTML/script)Native, Android has its own contextmenus
chrome.documentScanchrome.documentScan
chrome.eventsAlarmschrome.events
chrome.extensionTypesN/Achrome.extensionTypes
chrome.fileSystemNative FileSystem API
chrome.fileSystemProviderFileSystemProviderchrome.fileSystemProvider
chrome.gcmWeb Push NotificationsN/Achrome.gcm
chrome.hidWeb HID API
chrome.i18n(HTML/script)Localizationchrome.i18n
chrome.identityOAuth API or Credential Management APINativechrome.identity
chrome.idleUser Idle Detection APIchrome.idle
chrome.instanceIDWeb pushPer-App ID needs to be self-generatedchrome.instanceID
chrome.mdnsNDS discovery
chrome.mediaGalleriesNative FileSystem API
chrome.networking.onc
chrome.notificationsNotifications APINotifications show in lower right of CrOS as system level notificationschrome.notifications
chrome.permissionsWeb Permissions APIN/Achrome.permissions
chrome.powerWakeLock APIIn discussionchrome.power
chrome.printerProviderTransition to Extensionandroid.printservicechrome.printerProvider
chrome.runtimeService Workers + Page Lifecycle APIchrome.runtime
chrome.runtime.connectChannel Messaging APIchrome.runtime.connect
chrome.runtime.sendMessagechrome.runtime.sendMessage
chrome.serialWeb Serial API
chrome.sockets.tcpQuicTransport C/S (or WebSockets)android.net.ConnectivityManager and Java standard socket API
chrome.sockets.tcpServerandroid.net.ConnectivityManager and Java standard socket API
chrome.sockets.udpQuicTransport C/SDatagramSocket API for UDP
chrome.storageCache API
IndexedDB		chrome.storage
chrome.storage.managedManaged Configurationschrome.storage.managed
chrome.syncFileSystemJava - Drive REST API
chrome.system.cpunavigator.hardwareConcurrencychrome.system.cpu
chrome.system.displaywindow.screenDisplayMetrics, but high density displays are wonky
chrome.system.memorynavigator.deviceMemorychrome.system.memory
chrome.system.networkNetwork Information API
chrome.system.storagenavigator.storagechrome.system.storage
chrome.ttsWeb Speech API (Synthesis)Android TTS 2009chrome.tts
chrome.typeschrome.types
chrome.usbWeb USB APITemporary* private USB host API
chrome.virtualKeyboardSoft Input Method
chrome.vpnProviderVpnServicechrome.vpnProvider
chrome.wallpaperWallpaperManagerchrome.wallpaper
externally_connectable
kiosk_enabled
minimum_chrome_versionTarget Android versionminimum_chrome_version
offline_enabledOffline via Service WorkersNative
NaClMigration Guide
<webview> tagNativeWebView
+
Chrome App feature/functionalityWeb platform migration recommendationsAndroid migration recommendationsExtension migration recommendations
chrome.accessibilityFeatureschrome.accessibilityFeatures
chrome.alarmsNotification TriggersWorkManagerchrome.alarms
chrome.app.runtimeLaunch EventActivity Lifecycle
chrome.app.runtime.onRestartedPage Life CycleActivity.onResume
chrome.app.windowWindow Placement / Screen Enumerationchrome.windows
chrome.audioAudio Device ClientSome Audio APIs
chrome.bluetoothWeb Bluetooth APIBluetooth API
chrome.bluetoothLowEnergyWeb Bluetooth APIBTLE
chrome.bluetoothSocketWeb Bluetooth APIBluetooth Socket
chrome.browserwindow.openIntent system
chrome.commandsUI EventsHard-code keyboard commandschrome.commands
chrome.contextMenus(HTML/script)Native, Android has its own contextmenus
chrome.documentScanchrome.documentScan
chrome.eventsAlarmschrome.events
chrome.extensionTypesN/Achrome.extensionTypes
chrome.fileSystemNative FileSystem API
chrome.fileSystemProviderFileSystemProviderchrome.fileSystemProvider
chrome.gcmWeb Push NotificationsN/Achrome.gcm
chrome.hidWeb HID API
chrome.i18n(HTML/script)Localizationchrome.i18n
chrome.identityOAuth API or Credential Management APINativechrome.identity
chrome.idleUser Idle Detection APIchrome.idle
chrome.instanceIDWeb pushPer-App ID needs to be self-generatedchrome.instanceID
chrome.mdnsNDS discovery
chrome.mediaGalleriesNative FileSystem API
chrome.networking.onc
chrome.notificationsNotifications APINotifications show in lower right of CrOS as system level notificationschrome.notifications
chrome.permissionsWeb Permissions APIN/Achrome.permissions
chrome.powerWakeLock APIIn discussionchrome.power
chrome.printerProviderTransition to Extensionandroid.printservicechrome.printerProvider
chrome.runtimeService Workers + Page Lifecycle APIchrome.runtime
chrome.runtime.connectChannel Messaging APIchrome.runtime.connect
chrome.runtime.sendMessagechrome.runtime.sendMessage
chrome.serialWeb Serial API
chrome.sockets.tcpQuicTransport C/S (or WebSockets)android.net.ConnectivityManager and Java standard socket API
chrome.sockets.tcpServerandroid.net.ConnectivityManager and Java standard socket API
chrome.sockets.udpQuicTransport C/SDatagramSocket API for UDP
chrome.storageCache API
IndexedDB		chrome.storage
chrome.storage.managedManaged Configurationschrome.storage.managed
chrome.syncFileSystemJava - Drive REST API
chrome.system.cpunavigator.hardwareConcurrencychrome.system.cpu
chrome.system.displaywindow.screenDisplayMetrics, but high density displays are wonky
chrome.system.memorynavigator.deviceMemorychrome.system.memory
chrome.system.networkNetwork Information API
chrome.system.storagenavigator.storagechrome.system.storage
chrome.ttsWeb Speech API (Synthesis)Android TTS 2009chrome.tts
chrome.typeschrome.types
chrome.usbWeb USB APITemporary* private USB host API
chrome.virtualKeyboardSoft Input Method
chrome.vpnProviderVpnServicechrome.vpnProvider
chrome.wallpaperWallpaperManagerchrome.wallpaper
externally_connectable
kiosk_enabled
minimum_chrome_versionTarget Android versionminimum_chrome_version
offline_enabledOffline via Service WorkersNative
NaClMigration Guide
<webview> tagNativeWebView
## FAQs {: #faqs } @@ -220,7 +220,7 @@ programmatically.][203] [11]: /extensions/messaging#external-webpage [12]: /extensions/browserAction [13]: - https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Porting_a_Google_Chrome_extension + https://developer.mozilla.org/docs/Mozilla/Add-ons/WebExtensions/Porting_a_Google_Chrome_extension [14]: /apps/accessibilityFeatures [15]: /extensions/accessibilityFeatures [16]: /apps/alarms @@ -249,7 +249,7 @@ programmatically.][203] [39]: https://www.chromestatus.com/feature/5264933985976320 [40]: https://developer.android.com/reference/android/bluetooth/BluetoothSocket [41]: /apps/browser -[42]: https://developer.mozilla.org/en-US/docs/Web/API/Window/open +[42]: https://developer.mozilla.org/docs/Web/API/Window/open [43]: https://developer.android.com/reference/android/content/Intent [44]: /apps/commands [45]: https://w3c.github.io/uievents/ @@ -296,7 +296,7 @@ programmatically.][203] [86]: https://www.chromestatus.com/feature/5064350557536256 [87]: /extensions/notifications [88]: /apps/permissions -[89]: https://developer.mozilla.org/en-US/docs/Web/API/Permissions_API +[89]: https://developer.mozilla.org/docs/Web/API/Permissions_API [90]: /extensions/permissions [91]: /apps/power [92]: https://www.chromestatus.com/feature/4636879949398016 @@ -382,7 +382,7 @@ programmatically.][203] [172]: https://developers.google.com/web/fundamentals/app-install-banners/ [173]: https://developers.google.com/web/fundamentals/web-app-manifest/#display [174]: https://developers.google.com/web/fundamentals/web-app-manifest/ -[175]: https://developer.mozilla.org/en-US/docs/Web/Events/keydown +[175]: https://developer.mozilla.org/docs/Web/Events/keydown [176]: https://developers.google.com/web/fundamentals/web-app-manifest/#display [177]: https://chromestatus.com/feature/5642959835889664 [178]: /extensions/commands @@ -393,7 +393,7 @@ programmatically.][203] [183]: https://developers.google.com/web/updates/2015/07/interact-with-ble-devices-on-the-web [184]: https://developers.google.com/web/updates/2016/03/access-usb-devices-on-the-web [185]: https://developers.google.com/web/updates/2018/11/writable-files -[186]: https://developer.mozilla.org/en-US/docs/Web/API/WebSockets_API +[186]: https://developer.mozilla.org/docs/Web/API/WebSockets_API [187]: https://bit.ly/new-fugu-request [188]: https://developers.google.com/web/updates/capabilities [189]: https://developers.google.com/web/ilt/pwa/ @@ -405,7 +405,7 @@ programmatically.][203] [195]: https://bit.ly/new-fugu-request [196]: https://developers.google.com/web/fundamentals/engage-and-retain/push-notifications/ [197]: https://developers.google.com/web/updates/2016/06/persistent-storage?hl=en -[198]: https://developer.mozilla.org/en-US/docs/Web/API/Geolocation_API +[198]: https://developer.mozilla.org/docs/Web/API/Geolocation_API [199]: https://developers.google.com/web/ilt/pwa/introduction-to-service-worker [200]: https://developers.google.com/web/updates/2015/12/background-sync?hl=en [201]: https://developers.google.com/web/updates/2019/08/periodic-background-sync diff --git a/site/en/docs/apps/sencha_framework/index.md b/site/en/docs/apps/sencha_framework/index.md index 483a4d7cce8b..2f8e49a28649 100644 --- a/site/en/docs/apps/sencha_framework/index.md +++ b/site/en/docs/apps/sencha_framework/index.md @@ -500,7 +500,7 @@ player tree panel. [11]: contentSecurityPolicy [12]: https://github.com/GoogleChrome/sencha-video-player-app/blob/master/sandbox.html [13]: http://senchaprosvcs.github.com/GooglePlayer/docs/output/source/app.html#VP-Application -[14]: https://developer.mozilla.org/en-US/docs/DOM/window.postMessage +[14]: https://developer.mozilla.org/docs/DOM/window.postMessage [15]: https://github.com/GoogleChrome/sencha-video-player-app/blob/master/index.js [16]: https://github.com/GoogleChrome/sencha-video-player-app/blob/master/app/controller/MediaServers.js diff --git a/site/en/docs/devtools/accessibility/navigation/index.md b/site/en/docs/devtools/accessibility/navigation/index.md index dd866929abea..61a8ed170fcd 100644 --- a/site/en/docs/devtools/accessibility/navigation/index.md +++ b/site/en/docs/devtools/accessibility/navigation/index.md @@ -320,8 +320,8 @@ To run a new audit, use Shift+Tab to exit the report and l [10]: /docs/devtools/dom [11]: https://www.w3.org/TR/wai-aria-1.1/#tree [12]: /docs/devtools/dom#keynav -[13]: https://developer.mozilla.org/en-US/docs/Web/CSS/:active -[14]: https://developer.mozilla.org/en-US/docs/Web/CSS/:focus +[13]: https://developer.mozilla.org/docs/Web/CSS/:active +[14]: https://developer.mozilla.org/docs/Web/CSS/:focus [15]: #inspect [16]: /docs/devtools/shortcuts#styles [17]: /docs/devtools/css/reference#computed diff --git a/site/en/docs/devtools/console/index.md b/site/en/docs/devtools/console/index.md index ed2f5c9c6844..48b6e631dc40 100644 --- a/site/en/docs/devtools/console/index.md +++ b/site/en/docs/devtools/console/index.md @@ -106,7 +106,7 @@ the Console. [3]: /docs/devtools/console/log [4]: /docs/devtools/console/api [5]: https://en.wikipedia.org/wiki/Read%E2%80%93eval%E2%80%93print_loop -[6]: https://developer.mozilla.org/en-US/docs/Web/API/Window +[6]: https://developer.mozilla.org/docs/Web/API/Window [7]: /docs/devtools/console/utilities#debug -[8]: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/map +[8]: https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Array/map [9]: /docs/devtools/console/javascript diff --git a/site/en/docs/devtools/console/log/index.md b/site/en/docs/devtools/console/log/index.md index 37c9456eb6c8..32bc48c7b208 100644 --- a/site/en/docs/devtools/console/log/index.md +++ b/site/en/docs/devtools/console/log/index.md @@ -282,7 +282,7 @@ Congratulations, you have completed the tutorial. Click **Dispense Trophy** to r [3]: /docs/devtools/customize/#placement [4]: /docs/devtools/command-menu [5]: https://en.wikipedia.org/wiki/Stack_trace -[6]: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Regular_Expressions +[6]: https://developer.mozilla.org/docs/Web/JavaScript/Guide/Regular_Expressions [7]: https://regexr.com [8]: /docs/devtools/console/reference [9]: /docs/devtools/console/api diff --git a/site/en/docs/devtools/console/reference/index.md b/site/en/docs/devtools/console/reference/index.md index 5a931cc93e17..efe46e65219a 100644 --- a/site/en/docs/devtools/console/reference/index.md +++ b/site/en/docs/devtools/console/reference/index.md @@ -307,4 +307,4 @@ You can use any of the following workflows to clear the Console: [29]: /docs/devtools/console/live-expressions [30]: #settings [31]: #settings -[32]: https://developer.mozilla.org/en-US/docs/Glossary/Browsing_context +[32]: https://developer.mozilla.org/docs/Glossary/Browsing_context diff --git a/site/en/docs/devtools/console/utilities/index.md b/site/en/docs/devtools/console/utilities/index.md index 483aa8f7ef8c..414f746c25d4 100644 --- a/site/en/docs/devtools/console/utilities/index.md +++ b/site/en/docs/devtools/console/utilities/index.md @@ -422,8 +422,8 @@ values(object); ``` [1]: /docs/devtools/console/api -[2]: https://developer.mozilla.org/en-US/docs/Web/API/Document/querySelector -[3]: https://developer.mozilla.org/en-US/docs/Web/API/Document/querySelectorAll +[2]: https://developer.mozilla.org/docs/Web/API/Document/querySelector +[3]: https://developer.mozilla.org/docs/Web/API/Document/querySelectorAll [4]: /docs/devtools/javascript/breakpoints [console-dir]: /docs/devtools/console/api/#dir [console-dirxml]: /docs/devtools/console/api/#dirxml diff --git a/site/en/docs/devtools/css/overrides/index.md b/site/en/docs/devtools/css/overrides/index.md index 97a67b6c404b..64b81b5d2176 100644 --- a/site/en/docs/devtools/css/overrides/index.md +++ b/site/en/docs/devtools/css/overrides/index.md @@ -61,6 +61,6 @@ stylesheets][5], enable the **Show All** checkbox (next to the [**Filter**](#fil [1]: /docs/devtools/css [2]: /docs/devtools/css/reference#select -[3]: https://developer.mozilla.org/en-US/docs/Web/CSS/Specificity +[3]: https://developer.mozilla.org/docs/Web/CSS/Specificity [4]: /docs/devtools/javascript/reference#format -[5]: https://developer.mozilla.org/en-US/docs/Web/CSS/Cascade#User-agent_stylesheets +[5]: https://developer.mozilla.org/docs/Web/CSS/Cascade#User-agent_stylesheets diff --git a/site/en/docs/devtools/css/print-preview/index.md b/site/en/docs/devtools/css/print-preview/index.md index af06a07d8290..2d387cf664af 100644 --- a/site/en/docs/devtools/css/print-preview/index.md +++ b/site/en/docs/devtools/css/print-preview/index.md @@ -30,5 +30,5 @@ preview mode: From here, you can view and change your CSS, like any other web page. See [Get Started With Viewing And Changing CSS][2]. -[1]: https://developer.mozilla.org/en-US/docs/Web/CSS/Media_Queries/Using_media_queries +[1]: https://developer.mozilla.org/docs/Web/CSS/Media_Queries/Using_media_queries [2]: /docs/devtools/css diff --git a/site/en/docs/devtools/css/reference/index.md b/site/en/docs/devtools/css/reference/index.md index cfb1cd213108..485a1f56968d 100644 --- a/site/en/docs/devtools/css/reference/index.md +++ b/site/en/docs/devtools/css/reference/index.md @@ -394,14 +394,14 @@ To open the **Angle Clock**: [4]: #select [5]: #computed [6]: #computed -[7]: https://developer.mozilla.org/en-US/docs/Learn/CSS/Introduction_to_CSS/Box_model +[7]: https://developer.mozilla.org/docs/Learn/CSS/Introduction_to_CSS/Box_model [8]: #select [9]: /docs/devtools/css#pseudostates [10]: /docs/devtools/command-menu [11]: /docs/devtools/css/print-preview [12]: #add-declaration-inline [13]: #add-declaration-to-rule -[14]: https://developer.mozilla.org/en-US/docs/Web/CSS/Specificity#Selector_Types +[14]: https://developer.mozilla.org/docs/Web/CSS/Specificity#Selector_Types [15]: #select [16]: #select [17]: #values-shortcuts diff --git a/site/en/docs/devtools/device-mode/index.md b/site/en/docs/devtools/device-mode/index.md index 89d8a555bb47..16723efb82ac 100644 --- a/site/en/docs/devtools/device-mode/index.md +++ b/site/en/docs/devtools/device-mode/index.md @@ -278,7 +278,7 @@ own alpha, beta, and gamma values. [6]: https://en.wikipedia.org/wiki/Order_of_approximation#First-order [7]: /docs/devtools/remote-debugging [8]: #orientation -[9]: https://developer.mozilla.org/en-US/docs/Web/API/Window/devicePixelRatio -[10]: https://developer.mozilla.org/en-US/docs/Glossary/User_agent +[9]: https://developer.mozilla.org/docs/Web/API/Window/devicePixelRatio +[10]: https://developer.mozilla.org/docs/Glossary/User_agent [11]: #type [12]: /docs/devtools#community diff --git a/site/en/docs/devtools/device-mode/override-user-agent/index.md b/site/en/docs/devtools/device-mode/override-user-agent/index.md index 636f8f6b0910..5d292003edc6 100644 --- a/site/en/docs/devtools/device-mode/override-user-agent/index.md +++ b/site/en/docs/devtools/device-mode/override-user-agent/index.md @@ -30,4 +30,4 @@ To override the [user agent][1] string from Chrome DevTools: 4. Select a user agent string from the list, or enter your own custom string. -[1]: https://developer.mozilla.org/en-US/docs/Glossary/User_agent +[1]: https://developer.mozilla.org/docs/Glossary/User_agent diff --git a/site/en/docs/devtools/device-mode/testing-other-browsers/index.md b/site/en/docs/devtools/device-mode/testing-other-browsers/index.md index 95ec338a6425..d4d1485a24ad 100644 --- a/site/en/docs/devtools/device-mode/testing-other-browsers/index.md +++ b/site/en/docs/devtools/device-mode/testing-other-browsers/index.md @@ -140,7 +140,7 @@ is that you can automate unit tests for your site across different platforms. share it via integrations like MS Teams, Slack and more. Users can speed-up their testing by running tests in parallel. -[1]: https://developer.mozilla.org/en-US/docs/Tools/Responsive_Design_Mode +[1]: https://developer.mozilla.org/docs/Tools/Responsive_Design_Mode [2]: https://docs.microsoft.com/en-us/microsoft-edge/devtools-guide/emulation [3]: https://docs.microsoft.com/en-us/previous-versions/windows/internet-explorer/ie-developer/samples/dn255001(v=vs.85) diff --git a/site/en/docs/devtools/dom/index.md b/site/en/docs/devtools/dom/index.md index a79ccd57290f..8b89a177a7ca 100644 --- a/site/en/docs/devtools/dom/index.md +++ b/site/en/docs/devtools/dom/index.md @@ -392,7 +392,7 @@ The page's HTML is now different than its DOM. In other words, HTML represents initial page content, and the DOM represents current page content. When JavaScript adds, removes, or edits nodes, the DOM becomes different than the HTML. -[mdn]: https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model/Introduction +[mdn]: https://developer.mozilla.org/docs/Web/API/Document_Object_Model/Introduction See [Introduction to the DOM][mdn]{: .external } to learn more. diff --git a/site/en/docs/devtools/evaluate-performance/index.md b/site/en/docs/devtools/evaluate-performance/index.md index a6b6ab082046..9e1240350c0e 100644 --- a/site/en/docs/devtools/evaluate-performance/index.md +++ b/site/en/docs/devtools/evaluate-performance/index.md @@ -319,7 +319,7 @@ tips for improving various aspects of runtime performance, such as: [2]: https://developers.google.com/web/fundamentals/performance/rail [3]: https://support.google.com/chrome/answer/95464 [4]: /docs/devtools/customize/#placement -[5]: https://developer.mozilla.org/en-US/docs/Web/API/window/requestAnimationFrame +[5]: https://developer.mozilla.org/docs/Web/API/window/requestAnimationFrame [6]: https://developers.google.com/web/fundamentals/performance/rendering/avoid-large-complex-layouts-and-layout-thrashing#avoid_forced_synchronous_layouts [7]: diff --git a/site/en/docs/devtools/evaluate-performance/performance-reference/index.md b/site/en/docs/devtools/evaluate-performance/performance-reference/index.md index 451122c1d0e8..b62a90be2853 100644 --- a/site/en/docs/devtools/evaluate-performance/performance-reference/index.md +++ b/site/en/docs/devtools/evaluate-performance/performance-reference/index.md @@ -34,7 +34,7 @@ This section lists events that belong to Loading category and their properties. This section lists events that belong to the Scripting category and their properties. -
EventDescription
Animation Frame FiredA scheduled animation frame fired, and its callback handler invoked.
Cancel Animation FrameA scheduled animation frame was canceled.
GC EventGarbage collection occurred.
DOMContentLoadedThe DOMContentLoaded was fired by the browser. This event is fired when all of the page's DOM content has been loaded and parsed.
Evaluate ScriptA script was evaluated.
EventA JavaScript event ("mousedown", or "key", for example).
Function CallA top-level JavaScript function call was made (only appears when browser enters JavaScript engine).
Install TimerA timer was created with setInterval() or setTimeout().
Request Animation FrameA requestAnimationFrame() call scheduled a new frame
Remove TimerA previously created timer was cleared.
TimeA script called console.time()
Time EndA script called console.timeEnd()
Timer FiredA timer fired that was scheduled with setInterval() or setTimeout().
XHR Ready State ChangeThe ready state of an XMLHTTPRequest changed.
XHR LoadAn XMLHTTPRequest finished loading.
+
EventDescription
Animation Frame FiredA scheduled animation frame fired, and its callback handler invoked.
Cancel Animation FrameA scheduled animation frame was canceled.
GC EventGarbage collection occurred.
DOMContentLoadedThe DOMContentLoaded was fired by the browser. This event is fired when all of the page's DOM content has been loaded and parsed.
Evaluate ScriptA script was evaluated.
EventA JavaScript event ("mousedown", or "key", for example).
Function CallA top-level JavaScript function call was made (only appears when browser enters JavaScript engine).
Install TimerA timer was created with setInterval() or setTimeout().
Request Animation FrameA requestAnimationFrame() call scheduled a new frame
Remove TimerA previously created timer was cleared.
TimeA script called console.time()
Time EndA script called console.timeEnd()
Timer FiredA timer fired that was scheduled with setInterval() or setTimeout().
XHR Ready State ChangeThe ready state of an XMLHTTPRequest changed.
XHR LoadAn XMLHTTPRequest finished loading.
### Scripting event properties {: #scripting_event_properties } @@ -62,8 +62,8 @@ This section lists events that belong to Painting category and their properties. [1]: /docs/devtools/evaluate-performance/timeline-tool#view-nested-events [2]: /docs/devtools/evaluate-performance/timeline-tool#view-nested-events -[3]: https://developer.mozilla.org/en-US/docs/Web/Events/DOMContentLoaded -[4]: https://developer.mozilla.org/en-US/docs/Web/API/WindowTimers/setInterval -[5]: https://developer.mozilla.org/en-US/docs/Web/API/WindowTimers/setTimeout +[3]: https://developer.mozilla.org/docs/Web/Events/DOMContentLoaded +[4]: https://developer.mozilla.org/docs/Web/API/WindowTimers/setInterval +[5]: https://developer.mozilla.org/docs/Web/API/WindowTimers/setTimeout [6]: /docs/devtools/console/reference#consoletimelabel [7]: /docs/devtools/console/reference#consoletimeendlabel diff --git a/site/en/docs/devtools/javascript/background-services/index.md b/site/en/docs/devtools/javascript/background-services/index.md index 4a6f5e1f4eed..ef29b0d595d9 100644 --- a/site/en/docs/devtools/javascript/background-services/index.md +++ b/site/en/docs/devtools/javascript/background-services/index.md @@ -149,10 +149,10 @@ DevTools is not open: [10]: https://web.dev/service-workers-cache-storage/ [11]: /docs/devtools/open [12]: https://web.dev/service-workers-cache-storage/ -[13]: https://developer.mozilla.org/en-US/docs/Web/API/Push_API -[14]: https://developer.mozilla.org/en-US/docs/Web/API/Notifications_API +[13]: https://developer.mozilla.org/docs/Web/API/Push_API +[14]: https://developer.mozilla.org/docs/Web/API/Notifications_API [15]: /docs/devtools/open [16]: https://web.dev/service-workers-cache-storage/ -[17]: https://developer.mozilla.org/en-US/docs/Web/API/Push_API -[18]: https://developer.mozilla.org/en-US/docs/Web/API/Notifications_API +[17]: https://developer.mozilla.org/docs/Web/API/Push_API +[18]: https://developer.mozilla.org/docs/Web/API/Notifications_API [19]: /docs/devtools/open diff --git a/site/en/docs/devtools/javascript/breakpoints/index.md b/site/en/docs/devtools/javascript/breakpoints/index.md index bf3dcb881353..66651c7d9312 100644 --- a/site/en/docs/devtools/javascript/breakpoints/index.md +++ b/site/en/docs/devtools/javascript/breakpoints/index.md @@ -230,6 +230,6 @@ Console. Here's one strategy: [7]: #exceptions [8]: #function [9]: #loc -[10]: https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API +[10]: https://developer.mozilla.org/docs/Web/API/Fetch_API [11]: #loc [12]: #loc diff --git a/site/en/docs/devtools/javascript/snippets/index.md b/site/en/docs/devtools/javascript/snippets/index.md index 1a142df4204c..bf2835f657d5 100644 --- a/site/en/docs/devtools/javascript/snippets/index.md +++ b/site/en/docs/devtools/javascript/snippets/index.md @@ -150,7 +150,7 @@ See [Rename Snippets][6] if you'd like to give your new Snippet a custom name. [1]: /docs/devtools/console [2]: /docs/devtools/sources [3]: https://en.wikipedia.org/wiki/Bookmarklet -[4]: https://developer.mozilla.org/en-US/docs/Tools/Scratchpad +[4]: https://developer.mozilla.org/docs/Tools/Scratchpad [5]: #open [6]: #rename [7]: #open diff --git a/site/en/docs/devtools/memory-inspector/index.md b/site/en/docs/devtools/memory-inspector/index.md index 2431b2d64f5f..878385d85248 100644 --- a/site/en/docs/devtools/memory-inspector/index.md +++ b/site/en/docs/devtools/memory-inspector/index.md @@ -41,7 +41,7 @@ There are a few ways to open the **Memory inspector**. ### Inspect multiple objects {: #open-multiple } -1. You can inspect [DataView](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/DataView) or [TypedArray](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/TypedArray) as well. For example, `b2` is a `TypedArray`. To inspect that, right click on the `b2` property and select **Reveal in Memory Inspector panel** (No icon for `TypedArray` or `DataView` yet). +1. You can inspect [DataView](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/DataView) or [TypedArray](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/TypedArray) as well. For example, `b2` is a `TypedArray`. To inspect that, right click on the `b2` property and select **Reveal in Memory Inspector panel** (No icon for `TypedArray` or `DataView` yet). 2. A new tab is opened in the **Memory inspector**. Please note that you can inspect multiple objects at once. {% Img src="image/dPDCek3EhZgLQPGtEG3y0fTn4v82/ZaLWbrktT6N3sHMhyLHA.png", alt="New tab in the Memory inspector", width="800", height="602" %} diff --git a/site/en/docs/devtools/network/index.md b/site/en/docs/devtools/network/index.md index da5e49b6ab8c..27edac37fb39 100644 --- a/site/en/docs/devtools/network/index.md +++ b/site/en/docs/devtools/network/index.md @@ -388,7 +388,7 @@ network activity. [4]: /docs/devtools/open [5]: /docs/devtools/customize/#placement [6]: /docs/devtools/network/reference#hide-overview -[7]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Caching +[7]: https://developer.mozilla.org/docs/Web/HTTP/Caching [8]: #throttle [9]: https://web.dev/uses-long-cache-ttl/ [10]: /docs/devtools/network/reference#filter-by-property diff --git a/site/en/docs/devtools/network/reference/index.md b/site/en/docs/devtools/network/reference/index.md index 765890829319..75170b36216a 100644 --- a/site/en/docs/devtools/network/reference/index.md +++ b/site/en/docs/devtools/network/reference/index.md @@ -679,12 +679,12 @@ overview** checkbox to hide it. [4]: #network-conditions [5]: #network-conditions [6]: #hide-filters -[7]: https://developer.mozilla.org/en-US/docs/web/http/headers/set-cookie#attributes -[8]: https://developer.mozilla.org/en-US/docs/web/http/headers/set-cookie#attributes -[9]: https://developer.mozilla.org/en-US/docs/web/http/headers/set-cookie#attributes -[10]: https://developer.mozilla.org/en-US/docs/web/http/headers/set-cookie#attributes +[7]: https://developer.mozilla.org/docs/web/http/headers/set-cookie#attributes +[8]: https://developer.mozilla.org/docs/web/http/headers/set-cookie#attributes +[9]: https://developer.mozilla.org/docs/web/http/headers/set-cookie#attributes +[10]: https://developer.mozilla.org/docs/web/http/headers/set-cookie#attributes [11]: #hide-filters -[12]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/Data_URIs +[12]: https://developer.mozilla.org/docs/Web/HTTP/Basics_of_HTTP/Data_URIs [13]: #waterfall [14]: #sort-by-activity [15]: #headers diff --git a/site/en/docs/devtools/progressive-web-apps/index.md b/site/en/docs/devtools/progressive-web-apps/index.md index f7b0edc37100..206b52009a19 100644 --- a/site/en/docs/devtools/progressive-web-apps/index.md +++ b/site/en/docs/devtools/progressive-web-apps/index.md @@ -198,7 +198,7 @@ Related Guides: [9]: /docs/devtools/command-menu/ [10]: https://developers.google.com/web/fundamentals/push-notifications/how-push-works [11]: #clear-storage -[12]: https://developer.mozilla.org/en-US/docs/Web/API/Cache +[12]: https://developer.mozilla.org/docs/Web/API/Cache [13]: https://developers.google.com/web/fundamentals/glossary#opaque-response [14]: https://developers.google.com/web/fundamentals/glossary#CDN [15]: https://fetch.spec.whatwg.org/#http-cors-protocol diff --git a/site/en/docs/devtools/resources/index.md b/site/en/docs/devtools/resources/index.md index e6564c7f32cb..8cd280407caa 100644 --- a/site/en/docs/devtools/resources/index.md +++ b/site/en/docs/devtools/resources/index.md @@ -143,11 +143,11 @@ See [Filter by resource type][8]. **Figure 12**. Filtering for CSS in the Network Log -[1]: https://developer.mozilla.org/en-US/docs/Learn +[1]: https://developer.mozilla.org/docs/Learn [2]: /docs/devtools/overview/#start [3]: /docs/devtools/network#details [4]: #browse [5]: /docs/devtools/network#load -[6]: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/iframe +[6]: https://developer.mozilla.org/docs/Web/HTML/Element/iframe [7]: #directory [8]: /docs/devtools/network#type diff --git a/site/en/docs/devtools/speed/get-started/index.md b/site/en/docs/devtools/speed/get-started/index.md index 4245746e5b56..a6fa72141317 100644 --- a/site/en/docs/devtools/speed/get-started/index.md +++ b/site/en/docs/devtools/speed/get-started/index.md @@ -635,16 +635,16 @@ Tony's fans love how fast the site feels now, and Tony is very thankful for your [2]: https://glitch.com/edit/#!/tony [3]: /web/tools/lighthouse [4]: https://support.google.com/chrome/answer/95464 -[5]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Encoding#Directives +[5]: https://developer.mozilla.org/docs/Web/HTTP/Headers/Content-Encoding#Directives [6]: https://developers.google.com/web/fundamentals/design-and-ux/responsive/images#relative_sized_images [7]: https://images.guide/ [8]: https://developers.google.com/web/fundamentals/performance/critical-rendering-path [9]: https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/loading-third-party-javascript#use_async_or_defer [10]: https://webpack.js.org/guides/tree-shaking/ -[11]: https://developer.mozilla.org/en-US/docs/Web/API/User_Timing_API +[11]: https://developer.mozilla.org/docs/Web/API/User_Timing_API [12]: /docs/devtools/evaluate-performance/reference -[13]: https://developer.mozilla.org/en-US/docs/Web/API/User_Timing_API +[13]: https://developer.mozilla.org/docs/Web/API/User_Timing_API [14]: #feedback [15]: #feedback [16]: https://github.com/google/webfundamentals/issues/new diff --git a/site/en/docs/devtools/storage/applicationcache/index.md b/site/en/docs/devtools/storage/applicationcache/index.md index 694aced884c6..6e2cb8a1b667 100644 --- a/site/en/docs/devtools/storage/applicationcache/index.md +++ b/site/en/docs/devtools/storage/applicationcache/index.md @@ -8,7 +8,7 @@ date: 2019-03-25 description: "How to view Application Cache data from the Application panel of Chrome DevTools." --- -[mdn]: https://developer.mozilla.org/en-US/docs/Web/API/Window/applicationCache +[mdn]: https://developer.mozilla.org/docs/Web/API/Window/applicationCache {% Aside 'warning' %} Support for [AppCache][mdn] will be removed from Chrome and other Chromium-based browsers. We encourage developers to migrate off of AppCache now, rather than waiting any longer. Read [more](https://web.dev/appcache-removal/). diff --git a/site/en/docs/devtools/storage/cache/index.md b/site/en/docs/devtools/storage/cache/index.md index 91199ddfd72f..77d237064bf2 100644 --- a/site/en/docs/devtools/storage/cache/index.md +++ b/site/en/docs/devtools/storage/cache/index.md @@ -91,8 +91,8 @@ column of the **Network Log** has the information you're looking for. See [Log n **Figure 9**. The **Clear Site Data** button. [1]: /docs/devtools -[2]: https://developer.mozilla.org/en-US/docs/Web/API/Cache -[3]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Caching +[2]: https://developer.mozilla.org/docs/Web/API/Cache +[3]: https://developer.mozilla.org/docs/Web/HTTP/Caching [4]: /docs/devtools/network#load [5]: #view [6]: #view diff --git a/site/en/docs/devtools/storage/cookies/index.md b/site/en/docs/devtools/storage/cookies/index.md index 7f9b6cef978b..5e6d28a0003c 100644 --- a/site/en/docs/devtools/storage/cookies/index.md +++ b/site/en/docs/devtools/storage/cookies/index.md @@ -79,8 +79,8 @@ cookies. **Figure 5**. Clearing all cookies -[1]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Cookies +[1]: https://developer.mozilla.org/docs/Web/HTTP/Cookies [2]: /docs/devtools/open [3]: /docs/privacy-sandbox/first-party-sets/ -[6]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Cookies#define_the_lifetime_of_a_cookie +[6]: https://developer.mozilla.org/docs/Web/HTTP/Cookies#define_the_lifetime_of_a_cookie [10]: https://bugs.chromium.org/p/chromium/issues/detail?id=232693 diff --git a/site/en/docs/devtools/storage/indexeddb/index.md b/site/en/docs/devtools/storage/indexeddb/index.md index 1c3510abc5a4..de3e0fa8392e 100644 --- a/site/en/docs/devtools/storage/indexeddb/index.md +++ b/site/en/docs/devtools/storage/indexeddb/index.md @@ -146,14 +146,14 @@ edits an IndexedDB database. **Figure 12**. The **Clear storage** pane [1]: /docs/devtools -[2]: https://developer.mozilla.org/en-US/docs/Web/API/IndexedDB_API +[2]: https://developer.mozilla.org/docs/Web/API/IndexedDB_API [3]: /docs/devtools/overview/#start -[4]: https://developer.mozilla.org/en-US/docs/Web/API/IndexedDB_API/Using_IndexedDB -[5]: https://developer.mozilla.org/en-US/docs/Web/API/IndexedDB_API/Using_IndexedDB#Using_an_index +[4]: https://developer.mozilla.org/docs/Web/API/IndexedDB_API/Using_IndexedDB +[5]: https://developer.mozilla.org/docs/Web/API/IndexedDB_API/Using_IndexedDB#Using_an_index [6]: https://crbug.com/943770 [7]: #refresh [8]: - https://developer.mozilla.org/en-US/docs/Web/API/IndexedDB_API/Basic_Concepts_Behind_IndexedDB#gloss_keygenerator + https://developer.mozilla.org/docs/Web/API/IndexedDB_API/Basic_Concepts_Behind_IndexedDB#gloss_keygenerator [9]: /docs/devtools/snippets [10]: #view [11]: #view diff --git a/site/en/docs/devtools/storage/localstorage/index.md b/site/en/docs/devtools/storage/localstorage/index.md index fcbf43b05c0c..75ab96dce98d 100644 --- a/site/en/docs/devtools/storage/localstorage/index.md +++ b/site/en/docs/devtools/storage/localstorage/index.md @@ -85,7 +85,7 @@ JavaScript contexts, it's possible to interact with `localStorage` from the **Co **Figure 8**. Interacting with `localStorage` from the **Console** [1]: /docs/devtools -[2]: https://developer.mozilla.org/en-US/docs/Web/API/Window/localStorage +[2]: https://developer.mozilla.org/docs/Web/API/Window/localStorage [3]: #view [4]: #view [5]: #view diff --git a/site/en/docs/devtools/storage/sessionstorage/index.md b/site/en/docs/devtools/storage/sessionstorage/index.md index 45b079f7facd..46c8e80bd40a 100644 --- a/site/en/docs/devtools/storage/sessionstorage/index.md +++ b/site/en/docs/devtools/storage/sessionstorage/index.md @@ -85,7 +85,7 @@ JavaScript contexts, it's possible to interact with `sessionStorage` from the ** **Figure 7**. Interacting with `sessionStorage` from the **Console** [1]: /docs/devtools -[2]: https://developer.mozilla.org/en-US/docs/Web/API/Window/sessionStorage +[2]: https://developer.mozilla.org/docs/Web/API/Window/sessionStorage [3]: #view [4]: #view [5]: #view diff --git a/site/en/docs/devtools/workspaces/index.md b/site/en/docs/devtools/workspaces/index.md index 9a35bc73dfc5..c52d13beca3e 100644 --- a/site/en/docs/devtools/workspaces/index.md +++ b/site/en/docs/devtools/workspaces/index.md @@ -247,10 +247,10 @@ to your site. There's a way to have the **Sources** panel open alongside other p Congratulations, you have completed the tutorial. -[1]: https://developer.mozilla.org/en-US/docs/Learn/Getting_started_with_the_web +[1]: https://developer.mozilla.org/docs/Learn/Getting_started_with_the_web [2]: /docs/devtools/css [3]: - https://developer.mozilla.org/en-US/docs/Learn/Common_questions/set_up_a_local_testing_server#Running_a_simple_local_HTTP_server + https://developer.mozilla.org/docs/Learn/Common_questions/set_up_a_local_testing_server#Running_a_simple_local_HTTP_server [4]: http://blog.teamtreehouse.com/introduction-source-maps [5]: https://groups.google.com/forum/#!forum/google-chrome-developer-tools [6]: https://stackoverflow.com/questions/ask?tags=google-chrome-devtools @@ -258,8 +258,8 @@ Congratulations, you have completed the tutorial. [8]: https://glitch.com/edit/#!/remix/workspaces [9]: https://en.wikipedia.org/wiki/Port_(computer_networking)#Use_in_URLs [10]: #elements -[11]: https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model/Introduction -[12]: https://developer.mozilla.org/en-US/docs/Web/CSS/content +[11]: https://developer.mozilla.org/docs/Web/API/Document_Object_Model/Introduction +[12]: https://developer.mozilla.org/docs/Web/CSS/content [13]: https://groups.google.com/forum/#!forum/google-chrome-developer-tools [14]: https://stackoverflow.com/questions/ask?tags=google-chrome-devtools [15]: https://groups.google.com/forum/#!forum/google-chrome-developer-tools diff --git a/site/en/docs/extensions/api_other/index.md b/site/en/docs/extensions/api_other/index.md index eb81a3791543..5d53dd9a33e2 100644 --- a/site/en/docs/extensions/api_other/index.md +++ b/site/en/docs/extensions/api_other/index.md @@ -64,7 +64,7 @@ that library's JavaScript files with your extension. Bundled libraries work in e they do in other web pages. [1]: /docs/extensions/reference -[2]: https://developer.mozilla.org/en-US/docs/Web/API +[2]: https://developer.mozilla.org/docs/Web/API [3]: /docs/extensions/mv2/xhr [4]: /docs/extensions/mv2/declare_permissions [5]: http://www.html5rocks.com/tutorials/audio/quick/ diff --git a/site/en/docs/extensions/mv2/a11y/index.md b/site/en/docs/extensions/mv2/a11y/index.md index 15c69905605c..4b96ff52665c 100644 --- a/site/en/docs/extensions/mv2/a11y/index.md +++ b/site/en/docs/extensions/mv2/a11y/index.md @@ -235,7 +235,7 @@ Learn more about accessibility in Chrome by checking out the [A11ycasts][17] cha through the [Chromium Accessibility Technical Documentation][18]. [1]: https://webaim.org/techniques/screenreader/ -[2]: https://developer.mozilla.org/en-US/docs/Learn/Accessibility/HTML +[2]: https://developer.mozilla.org/docs/Learn/Accessibility/HTML [3]: https://www.w3.org/WAI/standards-guidelines/aria/ [4]: https://www.w3.org/TR/wai-aria/#roles [5]: https://www.w3.org/TR/wai-aria/#states_and_properties diff --git a/site/en/docs/extensions/mv2/content_scripts/index.md b/site/en/docs/extensions/mv2/content_scripts/index.md index ee3665208cd2..7f77891ff435 100644 --- a/site/en/docs/extensions/mv2/content_scripts/index.md +++ b/site/en/docs/extensions/mv2/content_scripts/index.md @@ -419,7 +419,7 @@ window.setTimeout(function() { [24]: /docs/extensions/mv2/match_patterns [25]: http://www.whatwg.org/specs/web-apps/current-work/#handler-onload [26]: http://www.whatwg.org/specs/web-apps/current-work/#dom-document-readystate -[27]: https://developer.mozilla.org/en-US/docs/Web/API/Window/postMessage +[27]: https://developer.mozilla.org/docs/Web/API/Window/postMessage [28]: /docs/extensions/mv2/xhr [29]: http://en.wikipedia.org/wiki/Cross-site_scripting [30]: http://en.wikipedia.org/wiki/Man-in-the-middle_attack diff --git a/site/en/docs/extensions/mv2/cross-origin-isolation/index.md b/site/en/docs/extensions/mv2/cross-origin-isolation/index.md index 9d12bf18d5c4..0c5eb75f0310 100644 --- a/site/en/docs/extensions/mv2/cross-origin-isolation/index.md +++ b/site/en/docs/extensions/mv2/cross-origin-isolation/index.md @@ -44,5 +44,5 @@ web-accessible subframe on a regular web page is not considered cross-origin iso [crbug-issue]: https://bugs.chromium.org/p/chromium/issues/detail?id=1131404 [doc-coep]: /docs/extensions/mv2/manifest/cross_origin_embedder_policy [doc-coop]: /docs/extensions/mv2/manifest/cross_origin_opener_policy -[mdn-sharedarraybuffer]: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/SharedArrayBuffer +[mdn-sharedarraybuffer]: https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/SharedArrayBuffer [web-coi-guide]: https://web.dev/cross-origin-isolation-guide/ diff --git a/site/en/docs/extensions/mv2/devtools/index.md b/site/en/docs/extensions/mv2/devtools/index.md index 460ff8a1f5b1..6fa59c736be3 100644 --- a/site/en/docs/extensions/mv2/devtools/index.md +++ b/site/en/docs/extensions/mv2/devtools/index.md @@ -479,7 +479,7 @@ You can find examples that use DevTools APIs in [Samples][42]. [29]: /docs/extensions/reference/tabs#method-sendMessage [30]: #injecting [32]: /docs/extensions/reference/runtime#method-sendMessage -[33]: https://developer.mozilla.org/en-US/docs/Web/API/Window.postMessage +[33]: https://developer.mozilla.org/docs/Web/API/Window.postMessage [34]: https://github.com/GoogleChrome/devtools-docs/issues/143 [35]: /docs/extensions/reference/runtime#event-onConnect [36]: /docs/extensions/reference/runtime#method-connect diff --git a/site/en/docs/extensions/mv2/manifest/cross_origin_embedder_policy/index.md b/site/en/docs/extensions/mv2/manifest/cross_origin_embedder_policy/index.md index 7cc018970998..b8d6b8e01bff 100644 --- a/site/en/docs/extensions/mv2/manifest/cross_origin_embedder_policy/index.md +++ b/site/en/docs/extensions/mv2/manifest/cross_origin_embedder_policy/index.md @@ -41,4 +41,4 @@ See the [Cross-origin isolation overview][doc-coi] for more information about th [doc-coi]: /docs/extensions/mv2/cross-origin-isolation/ [doc-coop]: /docs/extensions/mv2/manifest/cross_origin_opener_policy/ -[mdn-coep]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cross-Origin-Embedder-Policy +[mdn-coep]: https://developer.mozilla.org/docs/Web/HTTP/Headers/Cross-Origin-Embedder-Policy diff --git a/site/en/docs/extensions/mv2/manifest/cross_origin_opener_policy/index.md b/site/en/docs/extensions/mv2/manifest/cross_origin_opener_policy/index.md index 1f436a20ad89..e643b7708e8b 100644 --- a/site/en/docs/extensions/mv2/manifest/cross_origin_opener_policy/index.md +++ b/site/en/docs/extensions/mv2/manifest/cross_origin_opener_policy/index.md @@ -40,4 +40,4 @@ See [Cross-origin isolation overview][doc-coi] for more information about this f [doc-coep]: /docs/extensions/mv2/manifest/cross_origin_embedder_policy/ [doc-coi]: /docs/extensions/mv2/cross-origin-isolation/ -[mdn-coop]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cross-Origin-Opener-Policy +[mdn-coop]: https://developer.mozilla.org/docs/Web/HTTP/Headers/Cross-Origin-Opener-Policy diff --git a/site/en/docs/extensions/mv2/sandboxingEval/index.md b/site/en/docs/extensions/mv2/sandboxingEval/index.md index 3ce9787f40c6..b8a5a288ad70 100644 --- a/site/en/docs/extensions/mv2/sandboxingEval/index.md +++ b/site/en/docs/extensions/mv2/sandboxingEval/index.md @@ -163,6 +163,6 @@ time. [9]: /docs/apps/event_pages [10]: /docs/extensions/examples/howto/sandbox/eventpage.html [11]: /docs/extensions/examples/howto/sandbox/eventpage.js -[12]: https://developer.mozilla.org/en-US/docs/Web/API/Window/postMessage +[12]: https://developer.mozilla.org/docs/Web/API/Window/postMessage [13]: /docs/extensions/mv2/desktop_notifications [14]: http://www.youtube.com/watch?v=GBxv8SaX0gg diff --git a/site/en/docs/extensions/mv2/security/index.md b/site/en/docs/extensions/mv2/security/index.md index aca788688613..3681e099c4f6 100644 --- a/site/en/docs/extensions/mv2/security/index.md +++ b/site/en/docs/extensions/mv2/security/index.md @@ -272,7 +272,7 @@ function sanitizeInput(input) { [17]: #sanitize [18]: /messaging#cross-site-scripting [19]: /xhr#xhr-vs-content-scripts -[20]: https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API +[20]: https://developer.mozilla.org/docs/Web/API/Fetch_API [21]: /tabs#method-create [22]: /runtime#event-onMessageExternal [23]: /runtime#event-onMessage diff --git a/site/en/docs/extensions/mv3/a11y/index.md b/site/en/docs/extensions/mv3/a11y/index.md index 70c9c7eab726..9befb94a4a23 100644 --- a/site/en/docs/extensions/mv3/a11y/index.md +++ b/site/en/docs/extensions/mv3/a11y/index.md @@ -231,7 +231,7 @@ Learn more about accessibility in Chrome by checking out the [A11ycasts][17] cha through the [Chromium Accessibility Technical Documentation][18]. [1]: https://webaim.org/techniques/screenreader/ -[2]: https://developer.mozilla.org/en-US/docs/Learn/Accessibility/HTML +[2]: https://developer.mozilla.org/docs/Learn/Accessibility/HTML [3]: https://www.w3.org/WAI/standards-guidelines/aria/ [4]: https://www.w3.org/TR/wai-aria/#roles [5]: https://www.w3.org/TR/wai-aria/#states_and_properties diff --git a/site/en/docs/extensions/mv3/content_scripts/index.md b/site/en/docs/extensions/mv3/content_scripts/index.md index 38d56cb2d84a..d4dd258e866b 100644 --- a/site/en/docs/extensions/mv3/content_scripts/index.md +++ b/site/en/docs/extensions/mv3/content_scripts/index.md @@ -663,7 +663,7 @@ window.setTimeout(() => animate(elmt_id), 200); [24]: /docs/extensions/mv3/match_patterns [25]: https://www.whatwg.org/specs/web-apps/current-work/#handler-onload [26]: https://www.whatwg.org/specs/web-apps/current-work/#dom-document-readystate -[27]: https://developer.mozilla.org/en-US/docs/Web/API/Window/postMessage +[27]: https://developer.mozilla.org/docs/Web/API/Window/postMessage [28]: /docs/extensions/mv3/xhr [29]: https://en.wikipedia.org/wiki/Cross-site_scripting [30]: https://en.wikipedia.org/wiki/Man-in-the-middle_attack @@ -671,4 +671,4 @@ window.setTimeout(() => animate(elmt_id), 200); [32]: #dynamic-declarative [33]: /docs/extensions/reference/permissions -[ref-error]: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/ReferenceError +[ref-error]: https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/ReferenceError diff --git a/site/en/docs/extensions/mv3/cross-origin-isolation/index.md b/site/en/docs/extensions/mv3/cross-origin-isolation/index.md index 05c8f1cd6c22..ff04f10de9d6 100644 --- a/site/en/docs/extensions/mv3/cross-origin-isolation/index.md +++ b/site/en/docs/extensions/mv3/cross-origin-isolation/index.md @@ -44,5 +44,5 @@ web-accessible subframe on a regular web page is not considered cross-origin iso [crbug-issue]: https://bugs.chromium.org/p/chromium/issues/detail?id=1131404 [doc-coep]: /docs/extensions/mv3/manifest/cross_origin_embedder_policy [doc-coop]: /docs/extensions/mv3/manifest/cross_origin_opener_policy -[mdn-sharedarraybuffer]: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/SharedArrayBuffer +[mdn-sharedarraybuffer]: https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/SharedArrayBuffer [web-coi-guide]: https://web.dev/cross-origin-isolation-guide/ diff --git a/site/en/docs/extensions/mv3/devtools/index.md b/site/en/docs/extensions/mv3/devtools/index.md index b92b404a917c..d2d2a2f8b544 100644 --- a/site/en/docs/extensions/mv3/devtools/index.md +++ b/site/en/docs/extensions/mv3/devtools/index.md @@ -489,7 +489,7 @@ You can find examples that use DevTools APIs in [Samples][46]. [30]: #injecting [31]: /docs/extensions/mv3/devtools.inspectedWindow#method-eval [32]: /docs/extensions/runtime#method-sendMessage -[33]: https://developer.mozilla.org/en-US/docs/Web/API/Window.postMessage +[33]: https://developer.mozilla.org/docs/Web/API/Window.postMessage [34]: https://github.com/GoogleChrome/devtools-docs/issues/143 [35]: /docs/extensions/runtime#event-onConnect [36]: /docs/extensions/runtime#method-connect diff --git a/site/en/docs/extensions/mv3/faq/index.md b/site/en/docs/extensions/mv3/faq/index.md index 3ae6c5d1cf91..c5bafb185cab 100644 --- a/site/en/docs/extensions/mv3/faq/index.md +++ b/site/en/docs/extensions/mv3/faq/index.md @@ -335,5 +335,5 @@ The steps you should follow to ensure this are: https://bugs.chromium.org/p/chromium/issues/list?can=2&q=component%3DPlatform>Extensions+Type%3DFeature+shortcuts [61]: https://crbug.com/new [62]: https://groups.google.com/a/chromium.org/group/chromium-extensions/topics -[stringify]: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/JSON/stringify -[parse]: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/JSON/parse +[stringify]: https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/JSON/stringify +[parse]: https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/JSON/parse diff --git a/site/en/docs/extensions/mv3/manifest/cross_origin_embedder_policy/index.md b/site/en/docs/extensions/mv3/manifest/cross_origin_embedder_policy/index.md index d5b3182fae98..212eb6086f11 100644 --- a/site/en/docs/extensions/mv3/manifest/cross_origin_embedder_policy/index.md +++ b/site/en/docs/extensions/mv3/manifest/cross_origin_embedder_policy/index.md @@ -41,4 +41,4 @@ See the [Cross-origin isolation overview][doc-coi] for more information about th [doc-coi]: /docs/extensions/mv3/cross-origin-isolation/ [doc-coop]: /docs/extensions/mv3/manifest/cross_origin_opener_policy/ -[mdn-coep]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cross-Origin-Embedder-Policy +[mdn-coep]: https://developer.mozilla.org/docs/Web/HTTP/Headers/Cross-Origin-Embedder-Policy diff --git a/site/en/docs/extensions/mv3/manifest/cross_origin_opener_policy/index.md b/site/en/docs/extensions/mv3/manifest/cross_origin_opener_policy/index.md index 7fd75db9b85b..dd78637ef17a 100644 --- a/site/en/docs/extensions/mv3/manifest/cross_origin_opener_policy/index.md +++ b/site/en/docs/extensions/mv3/manifest/cross_origin_opener_policy/index.md @@ -40,4 +40,4 @@ See [Cross-origin isolation overview][doc-coi] for more information about this f [doc-coep]: /docs/extensions/mv3/manifest/cross_origin_embedder_policy/ [doc-coi]: /docs/extensions/mv3/cross-origin-isolation/ -[mdn-coop]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cross-Origin-Opener-Policy +[mdn-coop]: https://developer.mozilla.org/docs/Web/HTTP/Headers/Cross-Origin-Opener-Policy diff --git a/site/en/docs/extensions/mv3/migrating_to_service_workers/index.md b/site/en/docs/extensions/mv3/migrating_to_service_workers/index.md index f1427b37a4ff..c330c90cfb62 100644 --- a/site/en/docs/extensions/mv3/migrating_to_service_workers/index.md +++ b/site/en/docs/extensions/mv3/migrating_to_service_workers/index.md @@ -256,10 +256,10 @@ Operations with a Web Worker][18]. [3]: #events [4]: #workers [5]: https://developers.google.com/web/ilt/pwa/introduction-to-service-worker -[6]: https://developer.mozilla.org/en-US/docs/Web/API/Worker -[7]: https://developer.mozilla.org/en-US/docs/Web/API/Window -[8]: https://developer.mozilla.org/en-US/docs/Web/API/ServiceWorkerGlobalScope -[9]: https://developer.mozilla.org/en-US/docs/Web/API/DOMParser +[6]: https://developer.mozilla.org/docs/Web/API/Worker +[7]: https://developer.mozilla.org/docs/Web/API/Window +[8]: https://developer.mozilla.org/docs/Web/API/ServiceWorkerGlobalScope +[9]: https://developer.mozilla.org/docs/Web/API/DOMParser [10]: https://github.com/jsdom/jsdom [11]: https://github.com/developit/undom [12]: /docs/extensions/reference/windows#method-create @@ -271,5 +271,5 @@ Operations with a Web Worker][18]. [alarms]: /docs/extensions/reference/alarms/ [eventbgscripts]: /docs/extensions/mv2/background_migration/ [storage]: /docs/extensions/reference/storage/ -[fetch-link]: https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API +[fetch-link]: https://developer.mozilla.org/docs/Web/API/Fetch_API [manage-sw]: /docs/extensions/mv3/background_pages/#manifest diff --git a/site/en/docs/extensions/mv3/promises/index.md b/site/en/docs/extensions/mv3/promises/index.md index 4d41a8df18fb..9f0b4259df29 100644 --- a/site/en/docs/extensions/mv3/promises/index.md +++ b/site/en/docs/extensions/mv3/promises/index.md @@ -228,5 +228,5 @@ your extension's [manifest][doc-manifest]. [api-tabs-methods]: /docs/extensions/reference/tabs/#methods [doc-manifest]: /docs/extensions/mv3/manifest/ -[mdn-promise-chain]: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise#chained_promises -[mdn-promises]: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Using_promises +[mdn-promise-chain]: https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Promise#chained_promises +[mdn-promises]: https://developer.mozilla.org/docs/Web/JavaScript/Guide/Using_promises diff --git a/site/en/docs/extensions/mv3/security/index.md b/site/en/docs/extensions/mv3/security/index.md index 489e0abd6e5e..7b6e90deda45 100644 --- a/site/en/docs/extensions/mv3/security/index.md +++ b/site/en/docs/extensions/mv3/security/index.md @@ -270,7 +270,7 @@ function sanitizeInput(input) { [17]: #sanitize [18]: /docs/extensions/mv3/messaging#cross-site-scripting [19]: /docs/extensions/mv3/xhr#xhr-vs-content-scripts -[20]: https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API +[20]: https://developer.mozilla.org/docs/Web/API/Fetch_API [21]: /docs/extensions/reference/tabs#method-create [22]: /docs/extensions/reference/runtime#event-onMessageExternal [23]: /docs/extensions/reference/runtime#event-onMessage diff --git a/site/en/docs/extensions/reference/action/index.md b/site/en/docs/extensions/reference/action/index.md index 1e083e6bc719..f7b9d2f0461e 100644 --- a/site/en/docs/extensions/reference/action/index.md +++ b/site/en/docs/extensions/reference/action/index.md @@ -288,10 +288,10 @@ chrome.runtime.onInstalled.addListener(() => { [api-browser-action]: /docs/extensions/reference/browserAction/ [api-page-action]: /docs/extensions/reference/pageAction/ [api-declarative-content]: /docs/extensions/reference/declarativeContent/ -[css-color]: https://developer.mozilla.org/en-US/docs/Web/CSS/color +[css-color]: https://developer.mozilla.org/docs/Web/CSS/color [doc-manifest]: /docs/extensions/mv3/manifest [event-onclicked]: /docs/extensions/reference/action/#event-onClicked -[html-canvas]: https://developer.mozilla.org/en-US/docs/Web/API/HTMLCanvasElement -[html-offscreencanvas]: https://developer.mozilla.org/en-US/docs/Web/API/OffscreenCanvas +[html-canvas]: https://developer.mozilla.org/docs/Web/API/HTMLCanvasElement +[html-offscreencanvas]: https://developer.mozilla.org/docs/Web/API/OffscreenCanvas [repo-samples]: https://github.com/GoogleChrome/chrome-extensions-samples [sample-example]: https://github.com/GoogleChrome/chrome-extensions-samples/tree/main/api/action diff --git a/site/en/docs/extensions/reference/commands/index.md b/site/en/docs/extensions/reference/commands/index.md index 4028f9e538eb..28b753812633 100644 --- a/site/en/docs/extensions/reference/commands/index.md +++ b/site/en/docs/extensions/reference/commands/index.md @@ -310,7 +310,7 @@ function checkCommandShortcuts() { [api-browsesr-action]: /docs/extensions/reference/browserAction/ [api-page-action]: /docs/extensions/reference/pageAction/ [doc-manifest]: /docs/extension/mv3/manifest/ -[html-dcl]: https://developer.mozilla.org/en-US/docs/Web/API/Window/DOMContentLoaded_event +[html-dcl]: https://developer.mozilla.org/docs/Web/API/Window/DOMContentLoaded_event [event-oncommand]: #event-onCommand [header-usage]: #usage [header-key-combos]: #key-combinations diff --git a/site/en/docs/extensions/reference/fileBrowserHandler/index.md b/site/en/docs/extensions/reference/fileBrowserHandler/index.md index 3a93a909b1c4..42f8130b5652 100644 --- a/site/en/docs/extensions/reference/fileBrowserHandler/index.md +++ b/site/en/docs/extensions/reference/fileBrowserHandler/index.md @@ -47,7 +47,7 @@ You must declare the "fileBrowserHandler" permission in the [extension manifest] ## Implementing a file browser handler -To use this API, you must implement a function that handles the `onExecute` event of `chrome.fileBrowserHandler`. Your function will be called whenever the user clicks the button that represents your file browser handler. In your function, use the [File System API](https://developer.mozilla.org/en-US/docs/Web/API/FileSystemFileEntry) to get access to the file contents. Here is an example: +To use this API, you must implement a function that handles the `onExecute` event of `chrome.fileBrowserHandler`. Your function will be called whenever the user clicks the button that represents your file browser handler. In your function, use the [File System API](https://developer.mozilla.org/docs/Web/API/FileSystemFileEntry) to get access to the file contents. Here is an example: ```js chrome.fileBrowserHandler.onExecute.addListener(async (id, details) => { diff --git a/site/en/docs/extensions/reference/storage/index.md b/site/en/docs/extensions/reference/storage/index.md index bc6518142130..29e82e075324 100644 --- a/site/en/docs/extensions/reference/storage/index.md +++ b/site/en/docs/extensions/reference/storage/index.md @@ -205,7 +205,7 @@ function getAllStorageSyncData() { [api-storage]: /docs/extensions/mv2/manifest/storage [api-tabs]: /docs/extensions/mv2/tabs [incognito]: /docs/extensions/mv2/manifest/incognito -[local-storage]: https://developer.mozilla.org/en-US/docs/Web/API/Window/localStorage +[local-storage]: https://developer.mozilla.org/docs/Web/API/Window/localStorage [options-page]: https://developer.chrome.com/docs/extensions/mv3/options/ [prop-local]: #property-local [prop-sync]: #property-sync diff --git a/site/en/docs/extensions/whatsnew/index.md b/site/en/docs/extensions/whatsnew/index.md index d75d4e609453..0425b37c170b 100644 --- a/site/en/docs/extensions/whatsnew/index.md +++ b/site/en/docs/extensions/whatsnew/index.md @@ -140,7 +140,7 @@ Both [Manifest V2](/docs/extensions/mv2/cross-origin-isolation/) and [Manifest V3](/docs/extensions/mv3/cross-origin-isolation/) extensions can now opt into [cross origin isolation](https://web.dev/cross-origin-isolation-guide/). This feature limits which cross-origin resources can load an extension's pages and enables the use of low level web platform features like -[`SharedArrayBuffer`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/SharedArrayBuffer). Opt in will be required starting in Chrome 95. +[`SharedArrayBuffer`](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/SharedArrayBuffer). Opt in will be required starting in Chrome 95. ### 2021.08.04: Two step verification enforcement {: #two-step-verification-enforcement } diff --git a/site/en/docs/handbook/components/index.md b/site/en/docs/handbook/components/index.md index ccee0be8df12..c292f92c83c6 100644 --- a/site/en/docs/handbook/components/index.md +++ b/site/en/docs/handbook/components/index.md @@ -554,7 +554,7 @@ Shortcode object fields allow for modifying how the embed is presented: Images should always use the {% raw %}`{% Img %}`{% endraw %} shortcode. This shortcode will be generated for you when you upload your image to our CDN. -See the [Add an image or video guide](https://developer.chrome.com/docs/handbook/how-to/add-media/) for upload instructions. +See the [Add an image or video guide](/docs/handbook/how-to/add-media/) for upload instructions. ```md {% raw %}{% Img src="image/foR0vJZKULb5AGJExlazy1xYDgI2/w9i7lEqGw5J5b3jx5fAu.jpg", alt="ALT_TEXT_HERE", width="800", height="450" %}{% endraw %} @@ -1059,7 +1059,7 @@ responsive. To prevent this from happening add the `fixed-table` class. Videos should always use the {% raw %}`{% Video %}`{% endraw %} shortcode. This shortcode will be generated for you when you upload your video to our CDN. -See the [Add an image or video guide](https://developer.chrome.com/docs/handbook/how-to/add-media/) for upload instructions. +See the [Add an image or video guide](/docs/handbook/how-to/add-media/) for upload instructions. ```md {% raw %}{% Video src='video/tcFciHGuF3MxnTr1y5ue01OGLBn2/1601081394086.mp4' %}{% endraw %} @@ -1072,7 +1072,7 @@ Note that the video `src` property can either be a string or an array of strings for multiple sources. {% endAside %} -See the [Add an image or video guide](https://developer.chrome.com/docs/handbook/how-to/add-media/). +See the [Add an image or video guide](/docs/handbook/how-to/add-media/). ## YouTube diff --git a/site/en/docs/multidevice/android/index.md b/site/en/docs/multidevice/android/index.md index 4b723a0dccfb..419037e176b2 100644 --- a/site/en/docs/multidevice/android/index.md +++ b/site/en/docs/multidevice/android/index.md @@ -159,39 +159,39 @@ Overflow][46] using the `[google-chrome]` and `[android]` tags. [6]: http://www.html5rocks.com/tutorials/canvas/performance [7]: /devtools/index.html [8]: /devtools/docs/remote-debugging -[9]: https://developer.mozilla.org/en-US/docs/Web/API/Resource_Timing_API/Using_the_Resource_Timing_API +[9]: https://developer.mozilla.org/docs/Web/API/Resource_Timing_API/Using_the_Resource_Timing_API [10]: http://www.html5rocks.com/en/tutorials/webperformance/usertiming/ -[11]: https://developer.mozilla.org/en-US/docs/Web/HTML/Using_the_application_cache -[12]: https://developer.mozilla.org/en-US/docs/Web/API/FileSystem -[13]: https://developer.mozilla.org/en-US/docs/Web/API/File +[11]: https://developer.mozilla.org/docs/Web/HTML/Using_the_application_cache +[12]: https://developer.mozilla.org/docs/Web/API/FileSystem +[13]: https://developer.mozilla.org/docs/Web/API/File [14]: https://web.dev/storage-for-the-web/ [15]: https://web.dev/storage-for-the-web/ -[16]: https://developer.mozilla.org/en-US/docs/IndexedDB +[16]: https://developer.mozilla.org/docs/IndexedDB [17]: https://web.dev/storage-for-the-web/ [18]: https://chromestatus.com -[19]: https://developer.mozilla.org/en-US/docs/Web/CSS/calc() -[20]: https://developer.mozilla.org/en-US/docs/Web/CSS/filter -[21]: https://developer.mozilla.org/en-US/docs/CSS/Using_CSS_flexible_boxes -[22]: https://developer.mozilla.org/en-US/docs/CSS/length -[23]: https://developer.mozilla.org/en-US/docs/Web/CSS/@supports +[19]: https://developer.mozilla.org/docs/Web/CSS/calc() +[20]: https://developer.mozilla.org/docs/Web/CSS/filter +[21]: https://developer.mozilla.org/docs/CSS/Using_CSS_flexible_boxes +[22]: https://developer.mozilla.org/docs/CSS/length +[23]: https://developer.mozilla.org/docs/Web/CSS/@supports [24]: http://www.html5rocks.com/en/tutorials/webcomponents/customelements/#fouc [25]: https://developers.google.com/web/fundamentals/web-components/customelements -[26]: https://developer.mozilla.org/en-US/docs/HTML/Element/iframe +[26]: https://developer.mozilla.org/docs/HTML/Element/iframe [27]: http://www.html5rocks.com/tutorials/webcomponents/shadowdom/ -[28]: https://developer.mozilla.org/en-US/docs/HTML/Element/track +[28]: https://developer.mozilla.org/docs/HTML/Element/track [29]: https://web.dev/responsive-web-design-basics/#viewport -[30]: https://developer.mozilla.org/en-US/docs/Web/API/Geolocation_API +[30]: https://developer.mozilla.org/docs/Web/API/Geolocation_API [31]: http://www.w3.org/TR/2010/WD-html-media-capture-20100928/ [32]: http://www.html5rocks.com/tutorials/device/orientation/ [33]: http://developer.android.com/guide/appendix/g-app-intents.html [34]: http://www.html5rocks.com/en/tutorials/speed/animations/ -[35]: https://developer.mozilla.org/en-US/docs/WebSockets +[35]: https://developer.mozilla.org/docs/WebSockets [36]: http://www.html5rocks.com/en/tutorials/workers/basics/ [37]: http://www.html5rocks.com/en/mobile/fullscreen/#toc-request -[38]: https://developer.mozilla.org/en-US/docs/Web/API/WebRTC_API -[39]: https://developer.mozilla.org/en-US/docs/Web/API/Web_Audio_API -[40]: https://developer.mozilla.org/en-US/docs/Web/API/WebGL_API -[41]: https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP +[38]: https://developer.mozilla.org/docs/Web/API/WebRTC_API +[39]: https://developer.mozilla.org/docs/Web/API/Web_Audio_API +[40]: https://developer.mozilla.org/docs/Web/API/WebGL_API +[41]: https://developer.mozilla.org/docs/Web/HTTP/CSP [42]: http://chromestatus.com/ [43]: https://web.dev/responsive-web-design-basics/ [44]: https://crbug.com diff --git a/site/en/docs/multidevice/webview/index.md b/site/en/docs/multidevice/webview/index.md index d3c2e10c1c3f..3ba2c22edae1 100644 --- a/site/en/docs/multidevice/webview/index.md +++ b/site/en/docs/multidevice/webview/index.md @@ -140,9 +140,9 @@ of Android you should try enabling it for KitKat based devices and see if it imp [13]: http://www.html5rocks.com/en/tutorials/file/filesystem/ [14]: http://updates.html5rocks.com/2012/08/Integrating-input-type-file-with-the-Filesystem-API [15]: http://updates.html5rocks.com/tag/datalist -[16]: https://developer.mozilla.org/en-US/docs/Web/API/Geolocation_API -[17]: https://developer.mozilla.org/en-US/docs/Web/API/Window/deviceorientation_event -[18]: https://developer.mozilla.org/en-US/docs/Web/API/Media_Streams_API -[19]: https://developer.mozilla.org/en-US/docs/Web/API/Vibration_API +[16]: https://developer.mozilla.org/docs/Web/API/Geolocation_API +[17]: https://developer.mozilla.org/docs/Web/API/Window/deviceorientation_event +[18]: https://developer.mozilla.org/docs/Web/API/Media_Streams_API +[19]: https://developer.mozilla.org/docs/Web/API/Vibration_API [20]: http://developer.android.com/guide/webapps/migrating.html [21]: /devtools/docs/remote-debugging diff --git a/site/en/docs/privacy-sandbox/attribution-reporting-event-guide/index.md b/site/en/docs/privacy-sandbox/attribution-reporting-event-guide/index.md index 8ff6b79adc9c..62183d95ce70 100644 --- a/site/en/docs/privacy-sandbox/attribution-reporting-event-guide/index.md +++ b/site/en/docs/privacy-sandbox/attribution-reporting-event-guide/index.md @@ -14,7 +14,7 @@ authors: ## Who is this blogpost for? -This post is for you if you're a developer planning on experimenting with the Attribution Reporting API with event-level reports, either locally or via an origin trial⏤for example, if you're planning on taking part in the [origin trial](https://developer.chrome.com/origintrials/#/view_trial/3411476717733150721) that was [extended in November 2021](https://groups.google.com/a/chromium.org/g/blink-dev/c/DdjaFmsb4fA/m/RTK45f9gBQAJ). +This post is for you if you're a developer planning on experimenting with the Attribution Reporting API with event-level reports, either locally or via an origin trial⏤for example, if you're planning on taking part in the [origin trial](/origintrials/#/view_trial/3411476717733150721) that was [extended in November 2021](https://groups.google.com/a/chromium.org/g/blink-dev/c/DdjaFmsb4fA/m/RTK45f9gBQAJ). In this post, you'll find: @@ -442,7 +442,7 @@ app.get('/conversion', (req, res) => { In order to use Attribution Reporting in **cross-origin iframes** to declare a click or trigger an attribution, you need to enable the feature via the `attribution-reporting` -[Permissions-Policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Feature-Policy). +[Permissions-Policy](https://developer.mozilla.org/docs/Web/HTTP/Headers/Feature-Policy). ```html @@ -898,7 +898,7 @@ If you're not able to see any clicks or attribution trigger event on `chrome://c that your browser is properly configured. The issue may be a result of your implementation or origin trial setup. Check for common issues in your origin trial setup and implementation: - If you're running an origin trial, follow the troubleshooting checklist in - [Troubleshooting origin trials](https://developer.chrome.com/origin-trial-troubleshooting/). + [Troubleshooting origin trials](/origin-trial-troubleshooting/). - Ensure that the feature is [allowed](#allow-the-feature-for-cross-origin-iframes) in your application. - Open Chrome DevTools and see if issues have been flagged with your implementation in the **Issues** tab. A misconfiguration in your code may have prevented clicks or attribution triggers from being registered. diff --git a/site/en/docs/privacy-sandbox/attribution-reporting-in-short/index.md b/site/en/docs/privacy-sandbox/attribution-reporting-in-short/index.md index 11ee4378f6b4..80499f19bca3 100644 --- a/site/en/docs/privacy-sandbox/attribution-reporting-in-short/index.md +++ b/site/en/docs/privacy-sandbox/attribution-reporting-in-short/index.md @@ -58,7 +58,7 @@ There may be use cases that are non-ads-related. [Engage](#engage) to share your ## Why is this API needed? {: #why-is-this-api-needed } Today, ad conversion measurement often relies on [third-party -cookies](https://developer.mozilla.org/en-US/docs/Web/HTTP/Cookies#Third-party_cookies). +cookies](https://developer.mozilla.org/docs/Web/HTTP/Cookies#Third-party_cookies). Browsers are restricting access to third-party cookies because these can be used to track users across sites and hinder user privacy. This API enables those measurements in a privacy-preserving way, without third-party cookies. diff --git a/site/en/docs/privacy-sandbox/attribution-reporting-introduction/index.md b/site/en/docs/privacy-sandbox/attribution-reporting-introduction/index.md index b582d5dfec0c..8c5ae1443673 100644 --- a/site/en/docs/privacy-sandbox/attribution-reporting-introduction/index.md +++ b/site/en/docs/privacy-sandbox/attribution-reporting-introduction/index.md @@ -45,7 +45,7 @@ Sandbox proposals](https://developers.chrome.com/docs/privacy-sandbox). ## Why is this API needed? Today, ad conversion measurement often relies on [third-party -cookies](https://developer.mozilla.org/en-US/docs/Web/HTTP/Cookies#Third-party_cookies). +cookies](https://developer.mozilla.org/docs/Web/HTTP/Cookies#Third-party_cookies). Browsers are restricting access to third-party cookies because these can be used to track users across sites and hinder user privacy. This API enables those measurements in a privacy-preserving way, without third-party cookies. @@ -123,10 +123,10 @@ ecosystem feedback is collected. #### Experiment with end users on a deployed site 1. Enable the API for end users by registering for an [origin - trial](https://developer.chrome.com/blog/origin-trials/) if available. An origin trial + trial](/blog/origin-trials/) if available. An origin trial gives you access to an experimental feature, to build functionality you can try out for a limited time. Note that [third-party origin - trials](https://developer.chrome.com/blog/third-party-origin-trials/) make it possible + trials](/blog/third-party-origin-trials/) make it possible for third-party actors such as ad serving and measurement providers to test an API across multiple sites. **To see the currently available origin trials for this API, head over to [Status](#status)**. To be informed of future origin trials, join the @@ -252,9 +252,9 @@ attribution](https://github.com/WICG/conversion-measurement-api/blob/main/cross_ In a future without third-party cookies, this API would be combined with other privacy-preserving ads APIs in order to cover end-to-end use cases: -- Remarketing: see [FLEDGE](https://developer.chrome.com/docs/privacy-sandbox/fledge/) +- Remarketing: see [FLEDGE](/docs/privacy-sandbox/fledge/) - Interest-based ad selection: see - [FLoC](https://developer.chrome.com/docs/privacy-sandbox/floc/) + [FLoC](/docs/privacy-sandbox/floc/) {% endAside %} @@ -274,7 +274,7 @@ Statuses: {% Aside %} [Current origin -trial](https://developer.chrome.com/origintrials/#/view_trial/3411476717733150721) (Chrome +trial](/origintrials/#/view_trial/3411476717733150721) (Chrome experiment 🧪) {% endAside %} {% Aside 'caution' %} @@ -578,7 +578,7 @@ the following privacy mechanisms: - By default, the feature is enabled in top-level contexts. Arbitrary third-parties can't use the API without a publisher's knowledge, because the Attribution Reporting API needs to be enabled in child iframes via a [Permission - policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Feature-Policy). + policy](https://developer.mozilla.org/docs/Web/HTTP/Headers/Feature-Policy). ## Attribution Reporting: all resources diff --git a/site/en/docs/privacy-sandbox/attribution-reporting/index.md b/site/en/docs/privacy-sandbox/attribution-reporting/index.md index b77725238839..5f73b5260ea4 100644 --- a/site/en/docs/privacy-sandbox/attribution-reporting/index.md +++ b/site/en/docs/privacy-sandbox/attribution-reporting/index.md @@ -47,7 +47,7 @@ _For developers:_ repo](https://github.com/GoogleChromeLabs/privacy-sandbox-dev-support) or on the [Attribution Reporting mailing list for developers](https://groups.google.com/u/0/a/chromium.org/g/attribution-reporting-api-dev). -- Register for an [origin trial](https://developer.chrome.com/origintrials/#/view_trial/3411476717733150721) to experiment with end +- Register for an [origin trial](/origintrials/#/view_trial/3411476717733150721) to experiment with end users on a deployed site. ## Join the discussion diff --git a/site/en/docs/privacy-sandbox/cds21-update/index.md b/site/en/docs/privacy-sandbox/cds21-update/index.md index a4131510c191..f7900ece0a2b 100644 --- a/site/en/docs/privacy-sandbox/cds21-update/index.md +++ b/site/en/docs/privacy-sandbox/cds21-update/index.md @@ -23,7 +23,7 @@ Here's what you need to know: * Share your feedback with [@ChromiumDev on Twitter](https://twitter.com/ChromiumDev) This update on the Privacy Sandbox was announced at the -[Chrome Developers Summit 2021 keynote](https://developer.chrome.com/devsummit/schedule/keynote/). +[Chrome Developers Summit 2021 keynote](/devsummit/schedule/keynote/). {% YouTube id='_Ah_ODU3CvA' %} @@ -235,7 +235,7 @@ alt="", width="800", height="338" %} In April 2022, gradual UA string reduction will begin in Chrome. UA-CH launched and was ready for scaled adoption starting in March of 2021—you can begin testing and migrating to it now. -[Participate in an origin trial](https://developer.chrome.com/origintrials/#/view_trial/-7123568710593282047) +[Participate in an origin trial](/origintrials/#/view_trial/-7123568710593282047) to opt-in to the reduced UA string so you can see what the future state looks like. diff --git a/site/en/docs/privacy-sandbox/first-party-sets/index.md b/site/en/docs/privacy-sandbox/first-party-sets/index.md index cd1596e00ccb..3ab1692abf09 100644 --- a/site/en/docs/privacy-sandbox/first-party-sets/index.md +++ b/site/en/docs/privacy-sandbox/first-party-sets/index.md @@ -15,7 +15,7 @@ authors: ## Implementation status -* The initial [origin trial](https://developer.chrome.com/origintrials/#/view_trial/988540118207823873) +* The initial [origin trial](/origintrials/#/view_trial/988540118207823873) for First-Party Sets and SameParty was available in Chrome from versions 89 to 93 and is now closed. * [Chrome Platform Status](https://chromestatus.com/feature/5640066519007232). * [Chromium Projects](https://www.chromium.org/updates/first-party-sets). @@ -100,7 +100,7 @@ cookie is included on that request. ## Engage and share feedback -* **Origin trial**: The initial [origin trial](https://developer.chrome.com/origintrials/#/view_trial/988540118207823873) +* **Origin trial**: The initial [origin trial](/origintrials/#/view_trial/988540118207823873) for First-Party Sets and SameParty was available in Chrome from versions 89 to 93 and is now closed. * **GitHub**: Read the [proposal](https://github.com/privacycg/first-party-sets), [raise questions and follow discussion](https://github.com/privacycg/first-party-sets/issues). @@ -110,7 +110,7 @@ follow discussion](https://github.com/privacycg/first-party-sets/issues). ## Find out more -* [First-Party Sets and the SameParty attribute](https://developer.chrome.com/blog/first-party-sets-sameparty/) +* [First-Party Sets and the SameParty attribute](/blog/first-party-sets-sameparty/) * [First-Party Sets technical explainer](https://github.com/privacycg/first-party-sets) * [Chrome Platform Status](https://chromestatus.com/feature/5640066519007232). * [Chromium Projects](https://www.chromium.org/updates/first-party-sets). diff --git a/site/en/docs/privacy-sandbox/overview/index.md b/site/en/docs/privacy-sandbox/overview/index.md index a4f22ec4eb6d..da46ec9011d4 100644 --- a/site/en/docs/privacy-sandbox/overview/index.md +++ b/site/en/docs/privacy-sandbox/overview/index.md @@ -94,7 +94,7 @@ of reports: event-level and aggregate. ### Prevent covert tracking * [**User-Agent Client Hints**](https://web.dev/user-agent-client-hints/): -The [User-Agent](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/User-Agent) (UA) string +The [User-Agent](https://developer.mozilla.org/docs/Web/HTTP/Headers/User-Agent) (UA) string is a significant passive [fingerprinting](https://w3c.github.io/fingerprinting-guidance/#passive) surface, as well as being difficult to process. Client Hints enable developers to actively request only the information they need about the user's device or conditions, rather than needing to diff --git a/site/en/docs/privacy-sandbox/status/index.md b/site/en/docs/privacy-sandbox/status/index.md index 90ade4642859..ce6cedca68b0 100644 --- a/site/en/docs/privacy-sandbox/status/index.md +++ b/site/en/docs/privacy-sandbox/status/index.md @@ -20,7 +20,7 @@ _Previously known as Conversion Measurement._ - [Current origin trial](https://web.dev/origin-trials/): from Chrome 86, [now extended](https://groups.google.com/u/1/a/chromium.org/g/attribution-reporting-api-dev/c/ZKf9T8sRqAM) to Chrome 93. - [Register for origin - trial](https://developer.chrome.com/origintrials/#/view_trial/3411476717733150721). + trial](/origintrials/#/view_trial/3411476717733150721). - [Demo](https://goo.gle/demo-event-level-conversion-measurement-api). - [Chrome Platform Status](https://www.chromestatus.com/features/6412002824028160). - [Blink @@ -56,7 +56,7 @@ See [Status](/docs/privacy-sandbox/attribution-reporting-introduction/#status). - [Current origin trial](https://web.dev/origin-trials/): from Chrome 84, [now extended](https://groups.google.com/a/chromium.org/g/blink-dev/c/-W90wVkS0Ks/m/Jfh5-ZWpAQAJ) to Chrome 94. - [Register for origin - trial](https://developer.chrome.com/origintrials/#/view_trial/2479231594867458049). + trial](/origintrials/#/view_trial/2479231594867458049). - [Demo](https://trust-token-demo.glitch.me/). - [Chrome Platform Status](https://www.chromestatus.com/feature/5078049450098688). - [Blink @@ -72,7 +72,7 @@ See [Status](/docs/privacy-sandbox/attribution-reporting-introduction/#status). - [Current origin trial](https://web.dev/origin-trials/): Chrome 89 to 93. - [Register for origin - trial](https://developer.chrome.com/origintrials/#/view_trial/988540118207823873). + trial](/origintrials/#/view_trial/988540118207823873). - [Chrome Platform Status](https://chromestatus.com/feature/5640066519007232). - [Blink status](https://groups.google.com/a/chromium.org/g/blink-dev/search?q=first-party%20sets). @@ -85,7 +85,7 @@ See [Status](/docs/privacy-sandbox/attribution-reporting-introduction/#status). ## User-Agent Client Hints (UA-CH) - [Origin trial and schedule](https://blog.chromium.org/2021/09/user-agent-reduction-origin-trial-and-dates.html) -- [Register for origin trial](https://developer.chrome.com/origintrials/#/view_trial/-7123568710593282047) +- [Register for origin trial](/origintrials/#/view_trial/-7123568710593282047) - [Demo](https://uar-ot.glitch.me/) - [UA-CH proposal](https://github.com/WICG/ua-client-hints) - Tutorial to [migrate from UA string to UA-CH](https://web.dev/migrate-to-ua-ch/) @@ -138,7 +138,7 @@ Descendant of [TURTLEDOVE](https://github.com/WICG/turtledove). - [Getting started with Chrome's origin trials](https://web.dev/origin-trials/) - [What are third-party origin trials?](https://web.dev/third-party-origin-trials) -- [Troubleshooting Chrome's origin trials](https://developer.chrome.com/blog/origin-trial-troubleshooting/) +- [Troubleshooting Chrome's origin trials](/blog/origin-trial-troubleshooting/) - [Origin trials guide for web developers](https://github.com/GoogleChrome/OriginTrials/blob/gh-pages/developer-guide.md) - [Origin trial diff --git a/site/en/docs/privacy-sandbox/trust-tokens/index.md b/site/en/docs/privacy-sandbox/trust-tokens/index.md index 8bc72196d86d..623edfa0085d 100644 --- a/site/en/docs/privacy-sandbox/trust-tokens/index.md +++ b/site/en/docs/privacy-sandbox/trust-tokens/index.md @@ -15,7 +15,7 @@ authors: ## Implementation status * [In origin trial](https://web.dev/origin-trials/) Chrome 84 to 94. -* [Register for the trial](https://developer.chrome.com/origintrials/#/view_trial/2479231594867458049). +* [Register for the trial](/origintrials/#/view_trial/2479231594867458049). * [Demo](https://trust-token-demo.glitch.me/). * [Chrome DevTools integration](https://developers.google.com/web/updates/2021/01/devtools?utm_source=devtools#trust-token). * [Chrome Platform Status](https://www.chromestatus.com/feature/5078049450098688). @@ -68,7 +68,7 @@ publisher or online store) without identifying the user or linking identities ac {% Aside 'key-term' %} [Fingerprinting](https://w3c.github.io/fingerprinting-guidance/#passive) enables sites to identify and track individual users by getting data about their device, operating system, and browser setup -(such as language preferences, [user agent](https://developer.mozilla.org/en-US/docs/Web/API/NavigatorID/userAgent), and available fonts) or changes in device state. This may be done on the server by +(such as language preferences, [user agent](https://developer.mozilla.org/docs/Web/API/NavigatorID/userAgent), and available fonts) or changes in device state. This may be done on the server by checking request headers or on the client with JavaScript. Fingerprinting uses mechanisms that users aren't aware of and can't control. Sites such as @@ -110,7 +110,7 @@ For more detail about the JavaScript calls in this example, see [Sample API usag ## Engage and share feedback -* **Origin trial**: Register and take part in the [Chrome origin trial](https://developer.chrome.com/origintrials/#/view_trial/2479231594867458049). +* **Origin trial**: Register and take part in the [Chrome origin trial](/origintrials/#/view_trial/2479231594867458049). * **Demo**: Try out trust token [issuance and redemption](https://trust-token-demo.glitch.me/). * **GitHub**: Read the [proposal](https://github.com/WICG/trust-token-api), [raise questions and follow discussion](https://github.com/WICG/trust-token-api/issues). diff --git a/site/en/docs/privacy-sandbox/user-agent/index.md b/site/en/docs/privacy-sandbox/user-agent/index.md index 97819c366dfa..76bfc91834d3 100644 --- a/site/en/docs/privacy-sandbox/user-agent/index.md +++ b/site/en/docs/privacy-sandbox/user-agent/index.md @@ -37,7 +37,7 @@ full browser version, you'll need to [implement the User-Agent Client Hints API](https://web.dev/migrate-to-ua-ch/). {% Aside 'key-term' %} -The [`User-Agent` string](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/User-Agent) +The [`User-Agent` string](https://developer.mozilla.org/docs/Web/HTTP/Headers/User-Agent) is an HTTP request header which allows servers and networks to identify the application, operating system (OS), vendor, and / or version of a user agent. Currently, the `User-Agent` is shared on every HTTP request and exposed in @@ -116,7 +116,7 @@ to ensure Client Hints are available on site load and optimized. ## Engage and share feedback * **Origin trial**: - [Register for the Chrome origin trial](https://developer.chrome.com/origintrials/#/view_trial/-7123568710593282047) + [Register for the Chrome origin trial](/origintrials/#/view_trial/-7123568710593282047) to opt-in for the reduced user-agent, and [share your feedback](https://github.com/abeyad/user-agent-reduction/issues). * **Demo**: Try our [demo of User-Agent reduction](https://uar-ot.glitch.me/). diff --git a/site/en/docs/privacy-sandbox/user-agent/snippets/index.md b/site/en/docs/privacy-sandbox/user-agent/snippets/index.md index 592b8d388baf..cecdd076e999 100644 --- a/site/en/docs/privacy-sandbox/user-agent/snippets/index.md +++ b/site/en/docs/privacy-sandbox/user-agent/snippets/index.md @@ -53,7 +53,7 @@ AppleWebKit/537.36 (KHTML, like Gecko) Chrome/95. + -Intenta registrar `link` en la **Consola**. Las propiedades propias están en negrita y ordenadas primero. Estos cambios hacen más fácil identificar propiedades personalizadas, especialmente para [API Web](https://developer.mozilla.org/en-US/docs/Web/API) (e.g. `URL`) con muchas propiedades heredadas. +Intenta registrar `link` en la **Consola**. Las propiedades propias están en negrita y ordenadas primero. Estos cambios hacen más fácil identificar propiedades personalizadas, especialmente para [API Web](https://developer.mozilla.org/docs/Web/API) (e.g. `URL`) con muchas propiedades heredadas. {% Img src="image/dPDCek3EhZgLQPGtEG3y0fTn4v82/Ngjx6YRQsH3Fhl6DUZYl.png", alt="Las propiedades propias están en negritas y ordenadas primero.", width="800", height="561" %} diff --git a/site/es/blog/new-in-devtools-96/index.md b/site/es/blog/new-in-devtools-96/index.md index 99d112041895..b71992ed84a8 100644 --- a/site/es/blog/new-in-devtools-96/index.md +++ b/site/es/blog/new-in-devtools-96/index.md @@ -178,7 +178,7 @@ Chromium issues: [1232937](https://crbug.com/1232937), [1255586](https://crbug.c ## Panel de caché de la aplicación en desuso (deprecated) en el panel de la aplicación {: #app-cache } --> -El panel [Caché de la aplicación](https://developer.chrome.com/docs/devtools/storage/applicationcache/) en el panel de Aplicación se eliminó pues el soporte para [AppCache](https://web.dev/appcache-removal/) se ha eliminado de Chrome y otros navegadores basados ​​en Chromium. +El panel [Caché de la aplicación](/docs/devtools/storage/applicationcache/) en el panel de Aplicación se eliminó pues el soporte para [AppCache](https://web.dev/appcache-removal/) se ha eliminado de Chrome y otros navegadores basados ​​en Chromium. {# https://chromium.googlesource.com/devtools/devtools-frontend/+/de4d15e955d6145674e3885cde8a5a70f1269b79 #} diff --git a/site/es/docs/privacy-sandbox/attribution-reporting-introduction/index.md b/site/es/docs/privacy-sandbox/attribution-reporting-introduction/index.md index 2b99052a6ee2..891acb145edf 100644 --- a/site/es/docs/privacy-sandbox/attribution-reporting-introduction/index.md +++ b/site/es/docs/privacy-sandbox/attribution-reporting-introduction/index.md @@ -34,7 +34,7 @@ Esta API forma parte de Privacy Sandbox, que es una serie de propuestas para sat ## ¿Por qué se necesita esta API? -Hoy en día, la evaluación de conversiones publicitarias depende a menudo de las [cookies de terceros](https://developer.mozilla.org/en-US/docs/Web/HTTP/Cookies#Third-party_cookies). Los navegadores restringen el acceso a las cookies de terceros porque pueden utilizarse para rastrear a los usuarios en distintos sitios y obstaculizar su privacidad. Esta API permite realizar esas evaluaciones preservando la privacidad, sin cookies de terceros. +Hoy en día, la evaluación de conversiones publicitarias depende a menudo de las [cookies de terceros](https://developer.mozilla.org/docs/Web/HTTP/Cookies#Third-party_cookies). Los navegadores restringen el acceso a las cookies de terceros porque pueden utilizarse para rastrear a los usuarios en distintos sitios y obstaculizar su privacidad. Esta API permite realizar esas evaluaciones preservando la privacidad, sin cookies de terceros. ## ¿Quién debe conocer esta API? @@ -77,7 +77,7 @@ Si está experimentando con la API en Chrome, tendrá acceso a todas las funcion #### Experimente con usuarios finales en un sitio implementado -1. Habilite la API para los usuarios finales registrándose en una [prueba de origen](https://developer.chrome.com/blog/origin-trials/) si está disponible. Una prueba de origen le da acceso a una función experimental, para crear funciones que puede probar durante un tiempo limitado. Tenga en cuenta que las [pruebas de origen de terceros](https://developer.chrome.com/blog/third-party-origin-trials/) hacen posible que los terceros, como proveedores de servicios de publicidad y de medición, probar una API en varios sitios. **Para ver las pruebas de origen disponibles actualmente para esta API, diríjase a [Estado](#status)**. Para estar informado de futuras pruebas de origen, únase a la [lista de distribución de informes de atribuciones para desarrolladores](https://groups.google.com/u/1/a/chromium.org/g/attribution-reporting-api-dev). +1. Habilite la API para los usuarios finales registrándose en una [prueba de origen](/blog/origin-trials/) si está disponible. Una prueba de origen le da acceso a una función experimental, para crear funciones que puede probar durante un tiempo limitado. Tenga en cuenta que las [pruebas de origen de terceros](/blog/third-party-origin-trials/) hacen posible que los terceros, como proveedores de servicios de publicidad y de medición, probar una API en varios sitios. **Para ver las pruebas de origen disponibles actualmente para esta API, diríjase a [Estado](#status)**. Para estar informado de futuras pruebas de origen, únase a la [lista de distribución de informes de atribuciones para desarrolladores](https://groups.google.com/u/1/a/chromium.org/g/attribution-reporting-api-dev). 2. Integre la API en sus sitios y sistemas. @@ -148,8 +148,8 @@ Otras funciones propuestas en esta API son la [atribución de la aplicación en {% Aside %} En un futuro sin cookies de terceros, esta API se combinaría con otras API de anuncios que preservan la privacidad para cubrir casos de uso de un extremo a otro: -- Remarketing: consulte [FLEDGE](https://developer.chrome.com/docs/privacy-sandbox/fledge/) -- Selección de anuncios basada en intereses: consulte [FLoC](https://developer.chrome.com/docs/privacy-sandbox/floc/) +- Remarketing: consulte [FLEDGE](/docs/privacy-sandbox/fledge/) +- Selección de anuncios basada en intereses: consulte [FLoC](/docs/privacy-sandbox/floc/) {% endAside %} @@ -165,7 +165,7 @@ Estados: - `🧪 Experiment (BROWSER_NAME)`: hay un experimento disponible en BROWSER_NAME. En Chrome, un experimento se denomina prueba de origen. - `🚀 Stable (BROWSER_NAME)`: la función se envía de forma predeterminada en BROWSER_NAME. -{% Aside %} [Prueba de origen actual](https://developer.chrome.com/origintrials/#/view_trial/3411476717733150721) (experimento de Chrome 🧪) {% endAside %} +{% Aside %} [Prueba de origen actual](/origintrials/#/view_trial/3411476717733150721) (experimento de Chrome 🧪) {% endAside %} {% Aside 'caution' %} Se realizarán varias pruebas de origen (experimentos). Cada ronda se utiliza para mejorar y ajustar la API con base en los comentarios del ecosistema. {% endAside %} @@ -352,7 +352,7 @@ Los informes agrupados asocian un evento de clic o visualización detallada con ## Sitios y control de usuarios - Los usuarios pueden optar por no participar a través de la configuración del usuario en `chrome://settings/privacySandbox`. -- De forma predeterminada, la función está habilitada en contextos de nivel superior. Los terceros arbitrarios no pueden utilizar la API sin el conocimiento de un editor, porque la API para informes de atribuciones debe estar habilitada en los iframes secundarios a través de una [Política de permisos](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Feature-Policy). +- De forma predeterminada, la función está habilitada en contextos de nivel superior. Los terceros arbitrarios no pueden utilizar la API sin el conocimiento de un editor, porque la API para informes de atribuciones debe estar habilitada en los iframes secundarios a través de una [Política de permisos](https://developer.mozilla.org/docs/Web/HTTP/Headers/Feature-Policy). ## Preguntas abiertas diff --git a/site/es/docs/privacy-sandbox/attribution-reporting/index.md b/site/es/docs/privacy-sandbox/attribution-reporting/index.md index 342cb8e702cc..b0bc5f32bd28 100644 --- a/site/es/docs/privacy-sandbox/attribution-reporting/index.md +++ b/site/es/docs/privacy-sandbox/attribution-reporting/index.md @@ -40,7 +40,7 @@ También puede consultar el [Glosario de Privacy Sandbox](/docs/privacy-sandbox/ ## ¿Por qué se necesita esta API? {: #why-is-this-api-need } -Hoy en día, la evaluación de conversiones publicitarias depende a menudo de las [cookies de terceros](https://developer.mozilla.org/en-US/docs/Web/HTTP/Cookies#Third-party_cookies). Los navegadores restringen el acceso a las cookies de terceros porque pueden utilizarse para rastrear a los usuarios en distintos sitios y obstaculizar su privacidad. Esta API permite realizar esas evaluaciones preservando la privacidad, sin cookies de terceros. +Hoy en día, la evaluación de conversiones publicitarias depende a menudo de las [cookies de terceros](https://developer.mozilla.org/docs/Web/HTTP/Cookies#Third-party_cookies). Los navegadores restringen el acceso a las cookies de terceros porque pueden utilizarse para rastrear a los usuarios en distintos sitios y obstaculizar su privacidad. Esta API permite realizar esas evaluaciones preservando la privacidad, sin cookies de terceros. ## ¿Cómo funciona la API de informes de atribuciones y cuáles son sus características? @@ -57,7 +57,7 @@ La API ofrece dos tipos de informes de atribuciones que se pueden utilizar para ## Participe y comparta sus comentarios {: #engage } -- **Prueba de origen**: [regístrese en la primera prueba de origen (solo haga clic)](https://developer.chrome.com/origintrials/#/view_trial/3411476717733150721) o [consulte la primera demostración (solo haga clic)](https://goo.gle/demo-event-level-conversion-measurement-api). +- **Prueba de origen**: [regístrese en la primera prueba de origen (solo haga clic)](/origintrials/#/view_trial/3411476717733150721) o [consulte la primera demostración (solo haga clic)](https://goo.gle/demo-event-level-conversion-measurement-api). - Para estar atento a la próxima implementación de esta API que ofrecerá más funciones y estará disponible para experimentar en Chrome (prueba de origen), únase a la [lista de correos para desarrolladores](https://groups.google.com/u/1/a/chromium.org/g/attribution-reporting-api-dev). - **GitHub**: lea la [propuesta](https://github.com/WICG/conversion-measurement-api/), [realice preguntas y siga la discusión](https://github.com/WICG/conversion-measurement-api/issues). - **W3C**: discuta los casos de uso de la industria en el [Grupo de mejoras empresariales de la publicidad web](https://www.w3.org/community/web-adv/participants) y únase al [Grupo de la Privacidad comunitaria](https://www.w3.org/community/privacycg/) para participar en las discusiones en torno a la API de WebKit/Safari. diff --git a/site/es/docs/privacy-sandbox/first-party-sets/index.md b/site/es/docs/privacy-sandbox/first-party-sets/index.md index ee680dec47a6..404d422bfeb9 100644 --- a/site/es/docs/privacy-sandbox/first-party-sets/index.md +++ b/site/es/docs/privacy-sandbox/first-party-sets/index.md @@ -14,7 +14,7 @@ authors: ## Estado de la implementación - [En la prueba de origen](https://web.dev/origin-trials/) Chrome 89 a 93. -- [Regístrese para la prueba de origen](https://developer.chrome.com/origintrials/#/view_trial/988540118207823873). +- [Regístrese para la prueba de origen](/origintrials/#/view_trial/988540118207823873). - [Estado de la plataforma Chrome](https://chromestatus.com/feature/5640066519007232). - [Proyectos de Chromium](https://www.chromium.org/updates/first-party-sets). @@ -69,7 +69,7 @@ Esto significa que cuando un visitante de b.example o c.example realiza una soli ## Participe y comparta sus comentarios -- **Prueba de origen**: regístrese y participe en la [prueba de origen de Chrome](https://developer.chrome.com/origintrials/#/view_trial/988540118207823873). +- **Prueba de origen**: regístrese y participe en la [prueba de origen de Chrome](/origintrials/#/view_trial/988540118207823873). - **GitHub**: lea la [propuesta](https://github.com/privacycg/first-party-sets), [realice preguntas y siga la discusión](https://github.com/privacycg/first-party-sets/issues). - **Soporte para desarrolladores**: haga preguntas y únase a las discusiones en el [repositorio de soporte para desarrolladores de Privacy Sandbox](https://github.com/GoogleChromeLabs/privacy-sandbox-dev-support). diff --git a/site/es/docs/privacy-sandbox/overview/index.md b/site/es/docs/privacy-sandbox/overview/index.md index 380adf9ba57c..e2e65a4855bd 100644 --- a/site/es/docs/privacy-sandbox/overview/index.md +++ b/site/es/docs/privacy-sandbox/overview/index.md @@ -45,7 +45,7 @@ A continuación se enumeran las principales propuestas desarrolladas por el equi ### Limitar la recopilación de datos - [**Presupuesto de privacidad**](https://www.youtube.com/watch?v=0STgfjSA6T8): permite que los sitios web obtengan información sobre el navegador o el dispositivo de un usuario, pero permite que el navegador establezca una cuota sobre la cantidad total de información a la que puede acceder un sitio, de modo que no se pueda identificar al usuario. -- [**Consejos para el cliente Usuario-agente**](https://web.dev/user-agent-client-hints/): La cadena [Usuario-agente](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/User-Agent) (UA) es una importante superficie pasiva de [huellas digitales](https://w3c.github.io/fingerprinting-guidance/#passive), además de ser difícil de procesar. Las sugerencias del cliente permiten que los desarrolladores soliciten activamente solo la información que necesitan sobre el dispositivo o las condiciones del usuario, en vez de que necesiten analizar estos datos a partir de la cadena Usuario-agente. +- [**Consejos para el cliente Usuario-agente**](https://web.dev/user-agent-client-hints/): La cadena [Usuario-agente](https://developer.mozilla.org/docs/Web/HTTP/Headers/User-Agent) (UA) es una importante superficie pasiva de [huellas digitales](https://w3c.github.io/fingerprinting-guidance/#passive), además de ser difícil de procesar. Las sugerencias del cliente permiten que los desarrolladores soliciten activamente solo la información que necesitan sobre el dispositivo o las condiciones del usuario, en vez de que necesiten analizar estos datos a partir de la cadena Usuario-agente. - [**Gnatcatcher**](https://github.com/bslassey/ip-blindness): Limita la capacidad de identificar usuarios individuales accediendo a su dirección IP. La propuesta tiene dos partes: [Willful IP Blindness](https://github.com/bslassey/ip-blindness/blob/master/willful_ip_blindness.md) proporciona una forma para que los sitios web informen a los navegadores que no están conectando las direcciones IP con los usuarios, y Near-path NAT permite que grupos de usuarios envíen su tráfico a través del mismo servidor privatizador, ocultando de forma efectiva sus direcciones IP del host de un sitio. Gnatcatcher también garantiza que los sitios que necesiten acceder a las direcciones IP con fines legítimos, como la prevención de abusos, puedan hacerlo, sujetos a certificación y auditoría. ### Identidad diff --git a/site/es/docs/privacy-sandbox/status/index.md b/site/es/docs/privacy-sandbox/status/index.md index f152de1e93ec..779dfe90a5e7 100644 --- a/site/es/docs/privacy-sandbox/status/index.md +++ b/site/es/docs/privacy-sandbox/status/index.md @@ -16,7 +16,7 @@ authors: *Anteriormente conocido como Evaluación de las conversiones.* - [Prueba de origen actual](https://web.dev/origin-trials/): desde Chrome 86, [ahora ampliado](https://groups.google.com/u/1/a/chromium.org/g/attribution-reporting-api-dev/c/ZKf9T8sRqAM) a Chrome 93. -- [Regístrese para la prueba de origen](https://developer.chrome.com/origintrials/#/view_trial/3411476717733150721). +- [Regístrese para la prueba de origen](/origintrials/#/view_trial/3411476717733150721). - [Demostración](https://goo.gle/demo-event-level-conversion-measurement-api). - [Estado de la plataforma Chrome](https://www.chromestatus.com/features/6412002824028160). - [El estado de Blink](https://groups.google.com/a/chromium.org/g/blink-dev/search?q=conversion%20measurement). @@ -39,7 +39,7 @@ Ver [Estado](/docs/privacy-sandbox/attribution-reporting-introduction/#status). ## Los Trust Tokens - [Prueba de origen actual](https://web.dev/origin-trials/): desde Chrome 84, [ahora ampliada](https://groups.google.com/a/chromium.org/g/blink-dev/c/-W90wVkS0Ks/m/Jfh5-ZWpAQAJ) a Chrome 94. -- [Regístrese para la prueba de origen](https://developer.chrome.com/origintrials/#/view_trial/2479231594867458049). +- [Regístrese para la prueba de origen](/origintrials/#/view_trial/2479231594867458049). - [Demostración](https://trust-token-demo.glitch.me/). - [Estado de la plataforma Chrome](https://www.chromestatus.com/feature/5078049450098688). - [El estado de Blink](https://groups.google.com/a/chromium.org/g/blink-dev/search?q=trust%tokens). @@ -50,7 +50,7 @@ Ver [Estado](/docs/privacy-sandbox/attribution-reporting-introduction/#status). ## Conjuntos propios - [Prueba de origen actual](https://web.dev/origin-trials/): Chrome 84 a 91. -- [Regístrese para la prueba de origen](https://developer.chrome.com/origintrials/#/view_trial/988540118207823873). +- [Regístrese para la prueba de origen](/origintrials/#/view_trial/988540118207823873). - [Estado de la plataforma Chrome](https://chromestatus.com/feature/5640066519007232). - [El estado de Blink](https://groups.google.com/a/chromium.org/g/blink-dev/search?q=first-party%20sets). - [Propuesta de la API](https://github.com/privacycg/first-party-sets): consulte los [problemas](hhttps://github.com/privacycg/first-party-sets/issues) para conocer las preguntas y la discusión sobre la API. @@ -93,7 +93,7 @@ Es un descendiente de [TURTLEDOVE](https://github.com/WICG/turtledove). - [Introducción a las pruebas de origen de Chrome](https://web.dev/origin-trials/) - [¿Qué son las pruebas de origen de terceros?](https://web.dev/third-party-origin-trials) -- [Diagnóstico de los problemas en las pruebas de origen de Chrome](https://developer.chrome.com/blog/origin-trial-troubleshooting/) +- [Diagnóstico de los problemas en las pruebas de origen de Chrome](/blog/origin-trial-troubleshooting/) - [Guía de las pruebas de origen para desarrolladores web](https://github.com/GoogleChrome/OriginTrials/blob/gh-pages/developer-guide.md) - [Explicación de la pruebas de origen](https://github.com/GoogleChrome/OriginTrials/blob/gh-pages/explainer.md) - [Ejecución de una prueba de origen](https://www.chromium.org/blink/origin-trials/running-an-origin-trial) diff --git a/site/es/docs/privacy-sandbox/trust-tokens/index.md b/site/es/docs/privacy-sandbox/trust-tokens/index.md index 841c755fc55c..d00e8cdadae7 100644 --- a/site/es/docs/privacy-sandbox/trust-tokens/index.md +++ b/site/es/docs/privacy-sandbox/trust-tokens/index.md @@ -12,7 +12,7 @@ authors: ## Estado de la implementación - [En la prueba de origen](https://web.dev/origin-trials/) Chrome 84 a 94. -- [Regístrese para la prueba](https://developer.chrome.com/origintrials/#/view_trial/2479231594867458049). +- [Regístrese para la prueba](/origintrials/#/view_trial/2479231594867458049). - [Demostración](https://trust-token-demo.glitch.me/). - [Integración con las Chrome DevTools](https://developers.google.com/web/updates/2021/01/devtools?utm_source=devtools#trust-token). - [Estado de la plataforma Chrome](https://www.chromestatus.com/feature/5078049450098688). @@ -40,7 +40,7 @@ Desafortunadamente, muchos de los mecanismos que existen actualmente para evalua Con la API de Trust Tokens, un sitio web puede emitir tokens criptográficos a un usuario en el que confía, los cuales posteriormente pueden utilizarse en otro lugar. Los tokens se almacenan de forma segura en el navegador del usuario y luego se pueden canjear en otros contextos para confirmar la autenticidad del usuario. Esto permite que la confianza de un usuario en un sitio web (como un sitio de redes sociales o un servicio de correo electrónico) se transmita a otro sitio web (como un editor o una tienda en línea) sin que sea necesario identificar al usuario o relacionar ambas identidades entre los sitios. -{% Aside 'key-term' %} La [toma de huellas dactilares](https://w3c.github.io/fingerprinting-guidance/#passive) permite a los sitios identificar y hacer un seguimiento de los usuarios de forma individual al obtener información sobre su dispositivo, sistema operativo y configuración del navegador (como las preferencias del idioma, el [agente de usuario](https://developer.mozilla.org/en-US/docs/Web/API/NavigatorID/userAgent) y las fuentes que están disponibles) o los cambios efectuados en el estado del dispositivo. Esto se puede hacer en el servidor comprobando los encabezados de las solicitudes o en el cliente a través de JavaScript. +{% Aside 'key-term' %} La [toma de huellas dactilares](https://w3c.github.io/fingerprinting-guidance/#passive) permite a los sitios identificar y hacer un seguimiento de los usuarios de forma individual al obtener información sobre su dispositivo, sistema operativo y configuración del navegador (como las preferencias del idioma, el [agente de usuario](https://developer.mozilla.org/docs/Web/API/NavigatorID/userAgent) y las fuentes que están disponibles) o los cambios efectuados en el estado del dispositivo. Esto se puede hacer en el servidor comprobando los encabezados de las solicitudes o en el cliente a través de JavaScript. La toma de huellas dactilares utiliza mecanismos que los usuarios no conocen y que tampoco pueden controlar. Sitios como [Panopticlick](https://panopticlick.eff.org/) y [amiunique.org](https://amiunique.org/) muestran cómo se puede combinar la información proveniente de las huellas digitales para identificarlo como individuo. {% endAside %} @@ -68,7 +68,7 @@ En este ejemplo, el sitio web de un editor quiere verificar si un usuario es un ## Participe y comparta sus comentarios -- **Prueba de origen**: regístrese y participe en la [prueba de origen de Chrome](https://developer.chrome.com/origintrials/#/view_trial/2479231594867458049). +- **Prueba de origen**: regístrese y participe en la [prueba de origen de Chrome](/origintrials/#/view_trial/2479231594867458049). - **Demostración**: pruebe la [distribución y el desempeño](https://trust-token-demo.glitch.me/) de Trust token. - **GitHub**: lea la [propuesta](https://github.com/WICG/trust-token-api), [realice preguntas y siga la discusión](https://github.com/WICG/trust-token-api/issues). - **W3C**: discuta los casos de uso en la industria con el [grupo Improving Web Advertising Business](https://www.w3.org/community/web-adv/participants). diff --git a/site/ja/blog/new-in-devtools-93/index.md b/site/ja/blog/new-in-devtools-93/index.md index 998cc5de6c1b..e7a45c6d1f29 100644 --- a/site/ja/blog/new-in-devtools-93/index.md +++ b/site/ja/blog/new-in-devtools-93/index.md @@ -86,9 +86,9 @@ Attribution Reporting API errors are now reported in the **Issues** tab. Attribution Reporting API のエラーが **Issues** タブでレポートされるようになりました。 -[Attribution Reporting](https://developer.chrome.com/docs/privacy-sandbox/attribution-reporting/) は（広告のクリックや視聴のような）ユーザーアクションがコンバージョンを引き起こすタイミングについて、クロスサイトの識別を伴わずに測定するための新しい API です。 +[Attribution Reporting](/docs/privacy-sandbox/attribution-reporting/) は（広告のクリックや視聴のような）ユーザーアクションがコンバージョンを引き起こすタイミングについて、クロスサイトの識別を伴わずに測定するための新しい API です。 {% Img src="image/dPDCek3EhZgLQPGtEG3y0fTn4v82/bkEGVEv5kKc9M6qBUmLz.png", alt="Attribution Reporting API errors in the Issues tab", width="800", height="501" %} diff --git a/site/ja/blog/new-in-devtools-95/index.md b/site/ja/blog/new-in-devtools-95/index.md index 2df74355e5be..03b7513bd751 100644 --- a/site/ja/blog/new-in-devtools-95/index.md +++ b/site/ja/blog/new-in-devtools-95/index.md @@ -103,8 +103,8 @@ link.access = 'admin'; link.search = `?access=${link.access}`; ``` - -**Console** で `link` をログに出力してみてください。独自のプロパティが太字になり、最初にソートされるようになりました。この変更により、特に多くの継承されたプロパティを持つ [Web API](https://developer.mozilla.org/en-US/docs/Web/API) (例: `URL`) のカスタムプロパティを見つけやすくなりました。 + +**Console** で `link` をログに出力してみてください。独自のプロパティが太字になり、最初にソートされるようになりました。この変更により、特に多くの継承されたプロパティを持つ [Web API](https://developer.mozilla.org/docs/Web/API) (例: `URL`) のカスタムプロパティを見つけやすくなりました。 {% Img src="image/dPDCek3EhZgLQPGtEG3y0fTn4v82/Ngjx6YRQsH3Fhl6DUZYl.png", alt="独自のプロパティは太字で先頭に並びます", width="800", height="561" %} diff --git a/site/ja/blog/new-in-devtools-96/index.md b/site/ja/blog/new-in-devtools-96/index.md index 0702e3883369..bd969d8cd354 100644 --- a/site/ja/blog/new-in-devtools-96/index.md +++ b/site/ja/blog/new-in-devtools-96/index.md @@ -307,9 +307,9 @@ Chromium issues: [1232937](https://crbug.com/1232937), [1255586](https://crbug.c ## Application パネルの Application cache ペインの廃止 {: #app-cache } - + -Chrome やその他の Chromium ベースのブラウザから [AppCache](https://web.dev/appcache-removal/) のサポートが外れることに伴い、Application パネルの [Application cache](https://developer.chrome.com/docs/devtools/storage/applicationcache/) は削除されます。 +Chrome やその他の Chromium ベースのブラウザから [AppCache](https://web.dev/appcache-removal/) のサポートが外れることに伴い、Application パネルの [Application cache](/docs/devtools/storage/applicationcache/) は削除されます。 {# https://chromium.googlesource.com/devtools/devtools-frontend/+/de4d15e955d6145674e3885cde8a5a70f1269b79 #} diff --git a/site/ja/blog/origin-trials/index.md b/site/ja/blog/origin-trials/index.md index e9ff63d8e4f9..ef66c46bb6ea 100644 --- a/site/ja/blog/origin-trials/index.md +++ b/site/ja/blog/origin-trials/index.md @@ -63,8 +63,8 @@ referred to as "reverse" origin trials. --> -例えば、 [Chrome 85 から](https://web.dev/appcache-removal/#origin-trial) AppCache は初期状態で Chrome で使用できなくなりました。 AppCache から移行するために追加の時間が必要なサイトは、Chrome 93 まで [deprecation trial to continue using AppCache](https://developer.chrome.com/origintrials/#/view_trial/1776670052997660673) に登録することができました。 +the [deprecation trial to continue using AppCache](/origintrials/#/view_trial/1776670052997660673) until Chrome 93. --> +例えば、 [Chrome 85 から](https://web.dev/appcache-removal/#origin-trial) AppCache は初期状態で Chrome で使用できなくなりました。 AppCache から移行するために追加の時間が必要なサイトは、Chrome 93 まで [deprecation trial to continue using AppCache](/origintrials/#/view_trial/1776670052997660673) に登録することができました。 diff --git a/site/ja/docs/privacy-sandbox/attribution-reporting-introduction/index.md b/site/ja/docs/privacy-sandbox/attribution-reporting-introduction/index.md index 3f6eb10457a0..ca78df5ecc80 100644 --- a/site/ja/docs/privacy-sandbox/attribution-reporting-introduction/index.md +++ b/site/ja/docs/privacy-sandbox/attribution-reporting-introduction/index.md @@ -30,7 +30,7 @@ Attribution Reporting API を使用すると、**広告のクリックまたは ## この API が必要なのはなぜか？ -今日、広告コンバージョンの測定は、[サードパーティ Cookie](https://developer.mozilla.org/en-US/docs/Web/HTTP/Cookies#Third-party_cookies) に依存することがよくあります。ブラウザはサードパーティ Cookie へのアクセスを制限しています。これらは、サイト間でユーザーを追跡するために使用され、ユーザーのプライバシーに支障を与える可能性があるためです。この API は、サードパーティ Cookie を使用せずに、プライバシーを保護する形でこうした測定を可能にします。 +今日、広告コンバージョンの測定は、[サードパーティ Cookie](https://developer.mozilla.org/docs/Web/HTTP/Cookies#Third-party_cookies) に依存することがよくあります。ブラウザはサードパーティ Cookie へのアクセスを制限しています。これらは、サイト間でユーザーを追跡するために使用され、ユーザーのプライバシーに支障を与える可能性があるためです。この API は、サードパーティ Cookie を使用せずに、プライバシーを保護する形でこうした測定を可能にします。 ## この API について知っておく必要があるのは誰ですか？ @@ -71,7 +71,7 @@ Chrome で API を試している方は、**現在**実装されているすべ #### デプロイされたサイトでエンド ユーザーに対して試す -1. 使用できる場合は、[オリジン トライアル](https://developer.chrome.com/blog/origin-trials/)に登録して、エンド ユーザーの API を有効にします。オリジン トライアルでは、実験的な機能にアクセスして、限られた時間で試すことができる機能を構築できます。[サードパーティのオリジン トライアル](https://developer.chrome.com/blog/third-party-origin-trials/)では、広告配信や測定プロバイダーなどのサードパーティのアクターが複数のサイトで API をテストできてしまうことに注意してください。**この API で現在利用可能なオリジン トライアルを確認するには、[ステータス](#status)にアクセスしてください**。今後のオリジン トライアルについては、 [開発者向け Attribution Reporting メーリング リスト](https://groups.google.com/u/1/a/chromium.org/g/attribution-reporting-api-dev)にご登録ください。 +1. 使用できる場合は、[オリジン トライアル](/blog/origin-trials/)に登録して、エンド ユーザーの API を有効にします。オリジン トライアルでは、実験的な機能にアクセスして、限られた時間で試すことができる機能を構築できます。[サードパーティのオリジン トライアル](/blog/third-party-origin-trials/)では、広告配信や測定プロバイダーなどのサードパーティのアクターが複数のサイトで API をテストできてしまうことに注意してください。**この API で現在利用可能なオリジン トライアルを確認するには、[ステータス](#status)にアクセスしてください**。今後のオリジン トライアルについては、 [開発者向け Attribution Reporting メーリング リスト](https://groups.google.com/u/1/a/chromium.org/g/attribution-reporting-api-dev)にご登録ください。 2. API をサイトやシステムに統合します。 @@ -146,8 +146,8 @@ Chrome で API を試している方は、**現在**実装されているすべ {% Aside %}将来的に、サードパーティ Cookie がない場合、この API はエンドツーエンドのユース ケースをカバーするために、他のプライバシーが保護される広告の API と組み合わされます。 -- リマーケティング: [FLEDGE](https://developer.chrome.com/docs/privacy-sandbox/fledge/) を参照 -- インタレストベースの広告選択: [FLoC を参照](https://developer.chrome.com/docs/privacy-sandbox/floc/) +- リマーケティング: [FLEDGE](/docs/privacy-sandbox/fledge/) を参照 +- インタレストベースの広告選択: [FLoC を参照](/docs/privacy-sandbox/floc/) {% endAside %} @@ -163,7 +163,7 @@ Chrome で API を試している方は、**現在**実装されているすべ - `🧪 実験 (BROWSER_NAME)`: 実験は BROWSER_NAME で利用できます。 Chromeでは、実験はオリジン トライアルと呼ばれます。 - `🚀 Stable (BROWSER_NAME)`: この機能はデフォルトで BROWSER_NAME に搭載されています。 -{% Aside %} [現在のオリジン トライアル](https://developer.chrome.com/origintrials/#/view_trial/3411476717733150721) (Chrome 実験🧪){% endAside %} +{% Aside %} [現在のオリジン トライアル](/origintrials/#/view_trial/3411476717733150721) (Chrome 実験🧪){% endAside %} {% Aside 'caution' %}複数のオリジン トライアル (実験) が実行されます。各ラウンドは、エコシステムのフィードバックに基づいて API を改善および調整するために使用されます。 {% endAside %} @@ -363,7 +363,7 @@ alt="ALT_TEXT_HERE", width="800", height="1140" %} ## サイトとユーザーの管理 - `chrome://settings/privacySandbox`のユーザー設定よりオプトアウトできます。 -- デフォルトとして、この機能はトップレベルのコンテキストで有効になっています。 Attribution Reporting API は、[アクセス許可ポリシー](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Feature-Policy)によって子 iframe で有効にされている必要があるため、どのサードパーティでもパブリッシャーに内緒で API を使用できるということはありません。 +- デフォルトとして、この機能はトップレベルのコンテキストで有効になっています。 Attribution Reporting API は、[アクセス許可ポリシー](https://developer.mozilla.org/docs/Web/HTTP/Headers/Feature-Policy)によって子 iframe で有効にされている必要があるため、どのサードパーティでもパブリッシャーに内緒で API を使用できるということはありません。 ## 未解決の質問 diff --git a/site/ja/docs/privacy-sandbox/attribution-reporting/index.md b/site/ja/docs/privacy-sandbox/attribution-reporting/index.md index ef3a8988548d..64c9d2ba06e7 100644 --- a/site/ja/docs/privacy-sandbox/attribution-reporting/index.md +++ b/site/ja/docs/privacy-sandbox/attribution-reporting/index.md @@ -40,7 +40,7 @@ authors: ## この API が必要なのはなぜですか？ {: #why-is-this-api-needed } -今日、広告のコンバージョン測定は、[サードパーティの Cookie](https://developer.mozilla.org/en-US/docs/Web/HTTP/Cookies#Third-party_cookies) を使って行われることが多くなっています。サードパーティの Cookie はサイト間でユーザーを追跡することに使用でき、それが原因でユーザーのプライバシーに影響が出る可能性があるため、ブラウザではサードパーティの Cookie へのアクセスが制限されています。この API を使用すると、サードパーティの Cookie を使用しいなくてもプライバシーを保護しながら測定することができます。 +今日、広告のコンバージョン測定は、[サードパーティの Cookie](https://developer.mozilla.org/docs/Web/HTTP/Cookies#Third-party_cookies) を使って行われることが多くなっています。サードパーティの Cookie はサイト間でユーザーを追跡することに使用でき、それが原因でユーザーのプライバシーに影響が出る可能性があるため、ブラウザではサードパーティの Cookie へのアクセスが制限されています。この API を使用すると、サードパーティの Cookie を使用しいなくてもプライバシーを保護しながら測定することができます。 ## Attribution Reporting API はどのような機能を持っていますか？ @@ -57,7 +57,7 @@ Attribution Reporting API を使用すると、リンクされた 2 つのイベ ## 参加してフィードバックを共有する {: #engage } -- **オリジントライアル**： [最初のオリジントライアルに登録する (クリックのみ)](https://developer.chrome.com/origintrials/#/view_trial/3411476717733150721) か、[最初のデモ (クリックのみ) をご覧ください](https://goo.gle/demo-event-level-conversion-measurement-api) 。 +- **オリジントライアル**： [最初のオリジントライアルに登録する (クリックのみ)](/origintrials/#/view_trial/3411476717733150721) か、[最初のデモ (クリックのみ) をご覧ください](https://goo.gle/demo-event-level-conversion-measurement-api) 。 - さらなる機能を提供し、Chrome での実験 (オリジントライアル) に利用できるこの API の次の実装に関する最新情報を把握しておきたい方は、[開発者向けメーリングリスト](https://groups.google.com/u/1/a/chromium.org/g/attribution-reporting-api-dev)にご登録ください。 - **GitHub**: [提案](https://github.com/WICG/conversion-measurement-api/)を読み、[質問をしてディスカッションをフォロー](https://github.com/WICG/conversion-measurement-api/issues)しましょう。 - **W3C**: [Improving Web Advertising Business Group](https://www.w3.org/community/web-adv/participants) で業界のユースケースについて話し合い、[Privacy CommunityGroup](https://www.w3.org/community/privacycg/) の WebKit / Safari API に関するディスカッションに参加しましょう。 diff --git a/site/ja/docs/privacy-sandbox/first-party-sets/index.md b/site/ja/docs/privacy-sandbox/first-party-sets/index.md index ba55dcfcaa7e..3b14211f6bbf 100644 --- a/site/ja/docs/privacy-sandbox/first-party-sets/index.md +++ b/site/ja/docs/privacy-sandbox/first-party-sets/index.md @@ -14,7 +14,7 @@ authors: ## 実装状況 - Chrome 89 から 93 の[オリジン トライアル](https://web.dev/origin-trials/)。 -- [オリジン トライアルに登録](https://developer.chrome.com/origintrials/#/view_trial/988540118207823873)。 +- [オリジン トライアルに登録](/origintrials/#/view_trial/988540118207823873)。 - [Chrome プラットフォームの状態](https://chromestatus.com/feature/5640066519007232)。 - [Chromium プロジェクト](https://www.chromium.org/updates/first-party-sets)。 @@ -71,7 +71,7 @@ First-Party Sets を補うために、`SameParty` という Cookie 属性が提 ## 本 API に貢献し、フィードバックを共有しましょう -- **オリジン トライアル**: 登録して [Chrome オリジン トライアル](https://developer.chrome.com/origintrials/#/view_trial/988540118207823873)に参加しましょう。 +- **オリジン トライアル**: 登録して [Chrome オリジン トライアル](/origintrials/#/view_trial/988540118207823873)に参加しましょう。 - **GitHub**: [提案](https://github.com/privacycg/first-party-sets)を読み、[質問をして、議論に参加しましょう](https://github.com/privacycg/first-party-sets/issues)。 - **開発者サポート**: [プライバシー サンドボックス開発者サポート リポジトリ](https://github.com/GoogleChromeLabs/privacy-sandbox-dev-support)で質問をしたり、議論に参加したりしましょう。 diff --git a/site/ja/docs/privacy-sandbox/overview/index.md b/site/ja/docs/privacy-sandbox/overview/index.md index 732030c134da..608c60d739b2 100644 --- a/site/ja/docs/privacy-sandbox/overview/index.md +++ b/site/ja/docs/privacy-sandbox/overview/index.md @@ -46,7 +46,7 @@ Chromeチームによって立案された主な提案を以下の通りです ### データ収集の制限 - [**Privacy Budget**](https://www.youtube.com/watch?v=0STgfjSA6T8)：Webサイトがユーザーのブラウザーまたはデバイスに関する情報を取得できるようにしますが、ブラウザーがサイトがアクセスできる情報の合計量を制限できるようにし、ユーザーを識別できないようにします。 -- [**User-Agent Client Hints**](https://web.dev/user-agent-client-hints/)：[User-Agent](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/User-Agent)（UA）という文字列は、消極的にユーザーを識別できる重要でかつ処理しにくい[情報源](https://w3c.github.io/fingerprinting-guidance/#passive)です。Client Hintsを使用すると、開発者は、User-Agent文字列からこのデータを解析する必要がなくなり、ユーザーのデバイスまたは条件について必要な情報のみを積極的に要求できます。 +- [**User-Agent Client Hints**](https://web.dev/user-agent-client-hints/)：[User-Agent](https://developer.mozilla.org/docs/Web/HTTP/Headers/User-Agent)（UA）という文字列は、消極的にユーザーを識別できる重要でかつ処理しにくい[情報源](https://w3c.github.io/fingerprinting-guidance/#passive)です。Client Hintsを使用すると、開発者は、User-Agent文字列からこのデータを解析する必要がなくなり、ユーザーのデバイスまたは条件について必要な情報のみを積極的に要求できます。 - [**Gnatcatcher**](https://github.com/bslassey/ip-blindness)：IPアドレスを利用して個々のユーザーを識別する機能を制限します。提案には2つの部分があります。[Willful IP Blindness](https://github.com/bslassey/ip-blindness/blob/master/willful_ip_blindness.md)では、WebサイトがIPアドレスをユーザーに関連付けしていないことをブラウザに通知できるようになります。[Near-path NAT](https://github.com/bslassey/ip-blindness/blob/master/near_path_nat.md)では、ユーザーのグループが同じプライベートサーバーを介してトラフィックを送信し、実質、サイトホストからIPアドレスを隠せます。Gnatcatcherはまた、不正使用防止などの正当な目的でIPアドレスの情報を必要とするサイトが、認証と監査を条件としてIPアドレス情報を取得できるようにします。 ### アイデンティティ diff --git a/site/ja/docs/privacy-sandbox/status/index.md b/site/ja/docs/privacy-sandbox/status/index.md index 1356a1db7884..b297c9f2fc15 100644 --- a/site/ja/docs/privacy-sandbox/status/index.md +++ b/site/ja/docs/privacy-sandbox/status/index.md @@ -16,7 +16,7 @@ authors: *以前はコンバージョン測定と呼ばれていました。* - [現在のオリジントライアル](https://web.dev/origin-trials/)：Chrome 86から、Chrome93に[拡張されました](https://groups.google.com/u/1/a/chromium.org/g/attribution-reporting-api-dev/c/ZKf9T8sRqAM)。 -- [オリジントライアルに登録](https://developer.chrome.com/origintrials/#/view_trial/3411476717733150721)。 +- [オリジントライアルに登録](/origintrials/#/view_trial/3411476717733150721)。 - [デモ](https://goo.gle/demo-event-level-conversion-measurement-api)。 - [Chromeプラットフォームでの状況](https://www.chromestatus.com/features/6412002824028160)。 - [Blinkでの状況](https://groups.google.com/a/chromium.org/g/blink-dev/search?q=conversion%20measurement)。 @@ -39,7 +39,7 @@ authors: ## Trust Tokens - [現在のオリジントライアル](https://web.dev/origin-trials/)：Chrome 84から、Chrome94に[拡張され](https://groups.google.com/a/chromium.org/g/blink-dev/c/-W90wVkS0Ks/m/Jfh5-ZWpAQAJ)ました。 -- [オリジントライアルに登録](https://developer.chrome.com/origintrials/#/view_trial/2479231594867458049)。 +- [オリジントライアルに登録](/origintrials/#/view_trial/2479231594867458049)。 - [デモ](https://trust-token-demo.glitch.me/)。 - [Chromeプラットフォームでの状況](https://www.chromestatus.com/feature/5078049450098688)。 - [Blinkで状況](https://groups.google.com/a/chromium.org/g/blink-dev/search?q=trust%tokens)。 @@ -50,7 +50,7 @@ authors: ## First-Party Sets - [現在のオリジントライアル](https://web.dev/origin-trials/)：Chrome89から93。 -- [オリジントライアルに登録](https://developer.chrome.com/origintrials/#/view_trial/988540118207823873)。 +- [オリジントライアルに登録](/origintrials/#/view_trial/988540118207823873)。 - [Chromeプラットフォームでの状態](https://chromestatus.com/feature/5640066519007232)。 - [Blinkでの状況](https://groups.google.com/a/chromium.org/g/blink-dev/search?q=first-party%20sets)。 - [APIの提案](https://github.com/privacycg/first-party-sets)：APIの質問とディスカッションについては[問題](hhttps://github.com/privacycg/first-party-sets/issues)を参照してください。 @@ -93,7 +93,7 @@ authors: - [Chromeのオリジントライアルの紹介](https://web.dev/origin-trials/) - [サードパーティのオリジントライアルとは？](https://web.dev/third-party-origin-trials) -- [Chromeのオリジントライアルのトラブルシューティング](https://developer.chrome.com/blog/origin-trial-troubleshooting/) +- [Chromeのオリジントライアルのトラブルシューティング](/blog/origin-trial-troubleshooting/) - [Web開発者向けのオリジントライアルガイド](https://github.com/GoogleChrome/OriginTrials/blob/gh-pages/developer-guide.md) - [オリジントライアルの説明](https://github.com/GoogleChrome/OriginTrials/blob/gh-pages/explainer.md) - [オリジントライアルの実行](https://www.chromium.org/blink/origin-trials/running-an-origin-trial) diff --git a/site/ja/docs/privacy-sandbox/trust-tokens/index.md b/site/ja/docs/privacy-sandbox/trust-tokens/index.md index 32787cb1dc54..e28e98e534a2 100644 --- a/site/ja/docs/privacy-sandbox/trust-tokens/index.md +++ b/site/ja/docs/privacy-sandbox/trust-tokens/index.md @@ -12,7 +12,7 @@ authors: ## 実装状況 - [オリジントライアル中](https://web.dev/origin-trials/) Chrome 84～94。 -- [トライアルに登録する](https://developer.chrome.com/origintrials/#/view_trial/2479231594867458049)。 +- [トライアルに登録する](/origintrials/#/view_trial/2479231594867458049)。 - [デモ](https://trust-token-demo.glitch.me/)。 - [ChromeDevTools の統合](https://developers.google.com/web/updates/2021/01/devtools?utm_source=devtools#trust-token)。 - [Chrome プラットフォームステータス](https://www.chromestatus.com/feature/5078049450098688)。 @@ -40,7 +40,7 @@ authors: Trust Tokens API を使用すると、ウェブサイトは信頼できるユーザーに暗号化トークンを発行できます。このトークンは、その後に他の場所で使用することもできます。トークンはユーザーのブラウザによって安全に保存されるため、他のコンテキストでも利用することによりユーザーの信頼性を確認することができます。そうすることで、ユーザーを識別したりサイト間でアイデンティティを紐づけたりせずに、1 つのウェブサイト (ソーシャルメディアサイトや電子メールサービスなど) におけるユーザーの信頼性を別のウェブサイト (パブリッシャーやオンラインストアなど) に伝えることができます。 -{% Aside 'key-term' %} [フィンガープリンティング](https://w3c.github.io/fingerprinting-guidance/#passive)を使用すると、サイトはデバイス、オペレーティングシステム、ブラウザーの設定 (言語設定、[ユーザーエージェント](https://developer.mozilla.org/en-US/docs/Web/API/NavigatorID/userAgent)、使用可能なフォントなど) またはデバイスの状態の変化に関するデータを取得することにより、個々のユーザーを識別および追跡できます。これは、リクエストヘッダーを確認してサーバー側で行うことも、JavaScript を使用してクライアント側で行うことも可能です。 +{% Aside 'key-term' %} [フィンガープリンティング](https://w3c.github.io/fingerprinting-guidance/#passive)を使用すると、サイトはデバイス、オペレーティングシステム、ブラウザーの設定 (言語設定、[ユーザーエージェント](https://developer.mozilla.org/docs/Web/API/NavigatorID/userAgent)、使用可能なフォントなど) またはデバイスの状態の変化に関するデータを取得することにより、個々のユーザーを識別および追跡できます。これは、リクエストヘッダーを確認してサーバー側で行うことも、JavaScript を使用してクライアント側で行うことも可能です。 フィンガープリンティングは、ユーザーが認識していない、または制御できないメカニズムを使用しています。[Panopticlick](https://panopticlick.eff.org/) や [amiunique.org](https://amiunique.org/) などのサイトでは、フィンガープリントのデータを組み合わせて個人を識別する方法が説明されています。 {% endAside %} @@ -68,7 +68,7 @@ Trust Tokens API を使用すると、ウェブサイトは信頼できるユー ## 参加してフィードバックを共有する -- **オリジントライアル**[：Chrome オリジントライアル](https://developer.chrome.com/origintrials/#/view_trial/2479231594867458049)に登録して参加してください。 +- **オリジントライアル**[：Chrome オリジントライアル](/origintrials/#/view_trial/2479231594867458049)に登録して参加してください。 - **デモ**[：トラストトークンの発行と引き換え](https://trust-token-demo.glitch.me/)をお試しください。 - **GitHub**: [提案](https://github.com/WICG/trust-token-api)を読み、[質問をしてディスカッションをフォロー](https://github.com/WICG/trust-token-api/issues)しましょう。 - **W3C** [：Improving Web Advertising BusinessGroup](https://www.w3.org/community/web-adv/participants) で業界のユースケースについて話し合いましょう。 diff --git a/site/ko/blog/new-in-devtools-93/index.md b/site/ko/blog/new-in-devtools-93/index.md index 58f48070d913..729ec72aec5a 100644 --- a/site/ko/blog/new-in-devtools-93/index.md +++ b/site/ko/blog/new-in-devtools-93/index.md @@ -59,7 +59,7 @@ Chromium issue: [1182537](https://crbug.com/1182537) ## Attribution Reporting API 디버깅 {: #attribution-reporting } Attribution Reporting API 에러가 **Issues** 탭에 노출됩니다. -[Attribution Reporting](https://developer.chrome.com/docs/privacy-sandbox/attribution-reporting/) 은 크로스 사이트 식별자를 사용하지 않고 광고 클릭이나 노출같은 사용자 액션을 측정하는 데 도움을 주는 새로운 API 입니다. +[Attribution Reporting](/docs/privacy-sandbox/attribution-reporting/) 은 크로스 사이트 식별자를 사용하지 않고 광고 클릭이나 노출같은 사용자 액션을 측정하는 데 도움을 주는 새로운 API 입니다. {% Img src="image/dPDCek3EhZgLQPGtEG3y0fTn4v82/bkEGVEv5kKc9M6qBUmLz.png", alt="Issues 탭에서 Attribution Reporting API 에러를 볼 수 있습니다.", width="800", height="501" %} @@ -71,7 +71,7 @@ Chromium issue: [1190735](https://crbug.com/1190735) {% Img src="image/dPDCek3EhZgLQPGtEG3y0fTn4v82/O5uMSgkHrQ2mQDSjmg3A.png", alt="Console의 새로운 컨텍스트 메뉴", width="800", height="477" %} -Chrome 90에서 DevTools는 **Console** 이 [문자열 출력을 언제나 유효한 JSON 리터럴로 변경](https://developer.chrome.com/en/blog/new-in-devtools-90/#double-quotes) 하도록 업데이트 하였습니다. 이러한 변경사항이 오히려 혼란을 줄 수 있다는 피드백을 개발자로부터 받았고, 일부는 이스케이프 양이 과도하거나, 출력된 값을 읽기 어렵다고 느끼기도 하였습니다. +Chrome 90에서 DevTools는 **Console** 이 [문자열 출력을 언제나 유효한 JSON 리터럴로 변경](/en/blog/new-in-devtools-90/#double-quotes) 하도록 업데이트 하였습니다. 이러한 변경사항이 오히려 혼란을 줄 수 있다는 피드백을 개발자로부터 받았고, 일부는 이스케이프 양이 과도하거나, 출력된 값을 읽기 어렵다고 느끼기도 하였습니다. 이제 **Console** 에서는 문자열 출력을 유효한 JavaScript 리터럴로 변경하고, 문자열 복사 옵션을 3개 추가로 제공합니다. **Copy as JavaScript literal** 옵션은 적절한 특수 문자를 이스케이프하고 문자열 내용에 따라 작은따옴표, 큰따옴표 또는 억음 부호 (backtick)를 사용하여 문자열을 래핑합니다. **Copy string contents** 는 새 줄 및 기타 특수 문자를 포함한 원시 문자열 콘텐츠를 그대로 클립보드에 복사합니다. 마지막으로 **Copy as JSON literal** 은 문자열을 유효한 JSON 리터럴로 변환하고 클립보드에 복사합니다. diff --git a/site/ko/blog/new-in-devtools-95/index.md b/site/ko/blog/new-in-devtools-95/index.md index 5bc16f6b3dca..6df8525b7d99 100644 --- a/site/ko/blog/new-in-devtools-95/index.md +++ b/site/ko/blog/new-in-devtools-95/index.md @@ -83,7 +83,7 @@ link.search = `?access=${link.access}`; **콘솔** 에서 `link` 를 로깅해보세요. 객체의 자체 속성은 굵게 표시되고 첫번째로 노출됩니다. 이러한 변경을 통해 커스텀 속성을 더 쉽게 찾을 수 있습니다. -특히 상속되는 속성이 많은 [Web APIs](https://developer.mozilla.org/en-US/docs/Web/API) (예: `URL`)에서 유용합니다. +특히 상속되는 속성이 많은 [Web APIs](https://developer.mozilla.org/docs/Web/API) (예: `URL`)에서 유용합니다. {% Img src="image/dPDCek3EhZgLQPGtEG3y0fTn4v82/Ngjx6YRQsH3Fhl6DUZYl.png", alt="자체 속성은 굵게 표시되고, 첫번째로 노출됩니다.", width="800", height="561" %} diff --git a/site/ko/blog/new-in-devtools-96/index.md b/site/ko/blog/new-in-devtools-96/index.md index ab31092dd9d7..830633a8e3fd 100644 --- a/site/ko/blog/new-in-devtools-96/index.md +++ b/site/ko/blog/new-in-devtools-96/index.md @@ -189,7 +189,7 @@ Chromium issues: [1232937](https://crbug.com/1232937), [1255586](https://crbug.c ## 애플리케이션 패널 내 애플리케이션 캐시 영역 제거 예정 {: #app-cache } -[AppCache](https://web.dev/appcache-removal/)에 대한 지원이 크롬 및 다른 크로미움 기반 브라우저에서 중단됨에 따라, 애플리케이션 패널 내부 [애플리케이션 캐시](https://developer.chrome.com/docs/devtools/storage/applicationcache/) 영역이 제거되었습니다. +[AppCache](https://web.dev/appcache-removal/)에 대한 지원이 크롬 및 다른 크로미움 기반 브라우저에서 중단됨에 따라, 애플리케이션 패널 내부 [애플리케이션 캐시](/docs/devtools/storage/applicationcache/) 영역이 제거되었습니다. {# https://chromium.googlesource.com/devtools/devtools-frontend/+/de4d15e955d6145674e3885cde8a5a70f1269b79 #} diff --git a/site/ko/docs/privacy-sandbox/attribution-reporting-introduction/index.md b/site/ko/docs/privacy-sandbox/attribution-reporting-introduction/index.md index f78b96993bd2..a65602797a61 100644 --- a/site/ko/docs/privacy-sandbox/attribution-reporting-introduction/index.md +++ b/site/ko/docs/privacy-sandbox/attribution-reporting-introduction/index.md @@ -30,7 +30,7 @@ Attribution Reporting API를 사용하면 **광고 클릭 또는 조회**가 판 ## 이 API가 필요한 이유는 무엇입니까? -오늘날 광고 전환 측정은 종종 [타사 쿠키](https://developer.mozilla.org/en-US/docs/Web/HTTP/Cookies#Third-party_cookies)에 의존합니다. 브라우저는 타사 쿠키에 대한 액세스를 제한하고 있는데, 타사 쿠키는 사이트 전체에서 사용자를 추적하고 사용자 개인정보를 유출하는 데 사용될 수 있기 때문입니다. 이 API는 타사 쿠키 없이 개인정보를 보호하는 방식으로 이러한 측정을 가능하게 합니다. +오늘날 광고 전환 측정은 종종 [타사 쿠키](https://developer.mozilla.org/docs/Web/HTTP/Cookies#Third-party_cookies)에 의존합니다. 브라우저는 타사 쿠키에 대한 액세스를 제한하고 있는데, 타사 쿠키는 사이트 전체에서 사용자를 추적하고 사용자 개인정보를 유출하는 데 사용될 수 있기 때문입니다. 이 API는 타사 쿠키 없이 개인정보를 보호하는 방식으로 이러한 측정을 가능하게 합니다. ## 누가 이 API에 대해 알아야 합니까? @@ -71,7 +71,7 @@ Chrome에서 API를 실험하는 경우 **현재** 구현된 모든 기능에 #### 배포된 사이트에서 최종 사용자를 대상으로 실험 -1. 사용 가능한 경우 [최초 평가판](https://developer.chrome.com/blog/origin-trials/)에 등록하여 최종 사용자용 API를 사용합니다. 최초 평가판을 사용하면 제한된 시간 동안 사용해 볼 수 있는 기능을 구축하기 위해 실험적 기능에 액세스할 수 있습니다. [제3자 최초 평가판](https://developer.chrome.com/blog/third-party-origin-trials/)을 통해 광고 제공 및 측정 제공자와 같은 제3의 행위자가 여러 사이트에서 API를 테스트할 수 있습니다. **이 API에 대해 현재 사용 가능한 최초 평가판을 보려면 [현황](#status)으로 이동하세요**. 향후 최초 평가판에 대한 정보를 얻으려면 [개발자를 위한 Attribution Reporting 메일링 리스트에](https://groups.google.com/u/1/a/chromium.org/g/attribution-reporting-api-dev)에 가입하세요. +1. 사용 가능한 경우 [최초 평가판](/blog/origin-trials/)에 등록하여 최종 사용자용 API를 사용합니다. 최초 평가판을 사용하면 제한된 시간 동안 사용해 볼 수 있는 기능을 구축하기 위해 실험적 기능에 액세스할 수 있습니다. [제3자 최초 평가판](/blog/third-party-origin-trials/)을 통해 광고 제공 및 측정 제공자와 같은 제3의 행위자가 여러 사이트에서 API를 테스트할 수 있습니다. **이 API에 대해 현재 사용 가능한 최초 평가판을 보려면 [현황](#status)으로 이동하세요**. 향후 최초 평가판에 대한 정보를 얻으려면 [개발자를 위한 Attribution Reporting 메일링 리스트에](https://groups.google.com/u/1/a/chromium.org/g/attribution-reporting-api-dev)에 가입하세요. 2. API를 사이트 및 시스템에 통합합니다. @@ -138,8 +138,8 @@ Chrome에서 API를 실험하는 경우 **현재** 구현된 모든 기능에 {% Aside %} 타사 쿠키가 없는 향후 환경에서 이 API는 엔드 투 엔드 사용 사례를 포괄하기 위해 다른 개인정보 보호 광고 API와 결합될 것입니다. -- 리마케팅: [FLEDGE 참조](https://developer.chrome.com/docs/privacy-sandbox/fledge/) -- 관심 기반 광고 선택: [FLoC 참조](https://developer.chrome.com/docs/privacy-sandbox/floc/) +- 리마케팅: [FLEDGE 참조](/docs/privacy-sandbox/fledge/) +- 관심 기반 광고 선택: [FLoC 참조](/docs/privacy-sandbox/floc/) {% endAside %} @@ -155,7 +155,7 @@ Chrome에서 API를 실험하는 경우 **현재** 구현된 모든 기능에 - `🧪 Experiment (BROWSER_NAME)`: BROWSER_NAME에서 실험이 가능합니다. Chrome에서는 실험을 최초 평가판이라고 합니다. - `🚀 Stable (BROWSER_NAME)`: 이 기능은 BROWSER_NAME에서 기본적으로 제공됩니다. -{% Aside %} [현재 최초 평가판](https://developer.chrome.com/origintrials/#/view_trial/3411476717733150721) (Chrome 실험 🧪) {% endAside %} +{% Aside %} [현재 최초 평가판](/origintrials/#/view_trial/3411476717733150721) (Chrome 실험 🧪) {% endAside %} {% Aside 'caution' %} 다수의 최초 평가판(실험)이 실행됩니다. 각 라운드는 생태계 피드백을 기반으로 API를 개선하고 조정하는 데 이용됩니다. {% endAside %} @@ -342,7 +342,7 @@ Bob이라는 사람을 예로 들어 보겠습니다. Bob은 `news.com`에서 ## 사이트 및 사용자 제어 - 사용자는 `chrome://settings/privacySandbox`의 사용자 설정을 통해 선택 해제할 수 있습니다. -- 기본적으로 이 기능은 최상위 컨텍스트에서 활성화됩니다. [권한 정책](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Feature-Policy)을 통해 하위 iframe에서 Attribution Reporting API를 활성화해야 하기 때문에 임의의 제3자가 게시자 모르게 API를 사용할 수 없습니다. +- 기본적으로 이 기능은 최상위 컨텍스트에서 활성화됩니다. [권한 정책](https://developer.mozilla.org/docs/Web/HTTP/Headers/Feature-Policy)을 통해 하위 iframe에서 Attribution Reporting API를 활성화해야 하기 때문에 임의의 제3자가 게시자 모르게 API를 사용할 수 없습니다. ## 열린 질문 diff --git a/site/ko/docs/privacy-sandbox/attribution-reporting/index.md b/site/ko/docs/privacy-sandbox/attribution-reporting/index.md index d0f624fbbe54..cb03460427aa 100644 --- a/site/ko/docs/privacy-sandbox/attribution-reporting/index.md +++ b/site/ko/docs/privacy-sandbox/attribution-reporting/index.md @@ -40,7 +40,7 @@ authors: ## 이 API가 필요한 이유는 무엇입니까? {: #why-is-this-api-needed } -오늘날 광고 전환 측정은 종종 [타사 쿠키](https://developer.mozilla.org/en-US/docs/Web/HTTP/Cookies#Third-party_cookies)에 의존합니다. 브라우저는 타사 쿠키에 대한 액세스를 제한하고 있는데, 타사 쿠키는 사이트 전체에서 사용자를 추적하고 사용자 개인정보를 유출하는 데 사용될 수 있기 때문입니다. 이 API는 타사 쿠키 없이 개인정보를 보호하는 방식으로 이러한 측정을 가능하게 합니다. +오늘날 광고 전환 측정은 종종 [타사 쿠키](https://developer.mozilla.org/docs/Web/HTTP/Cookies#Third-party_cookies)에 의존합니다. 브라우저는 타사 쿠키에 대한 액세스를 제한하고 있는데, 타사 쿠키는 사이트 전체에서 사용자를 추적하고 사용자 개인정보를 유출하는 데 사용될 수 있기 때문입니다. 이 API는 타사 쿠키 없이 개인정보를 보호하는 방식으로 이러한 측정을 가능하게 합니다. ## Attribution Reporting API는 어떤 방식으로 작동하며 어떤 기능을 합니까? @@ -57,7 +57,7 @@ API는 다양한 사용 사례에 사용할 수 있는 두 가지 유형의 기 ## 참여 및 피드백 공유 {: #engage } -- **최초 평가판**: [첫 최초 평가판(클릭만)에 등록하거나](https://developer.chrome.com/origintrials/#/view_trial/3411476717733150721), 또는 [첫 데모(클릭만)를 참조하세요](https://goo.gle/demo-event-level-conversion-measurement-api). +- **최초 평가판**: [첫 최초 평가판(클릭만)에 등록하거나](/origintrials/#/view_trial/3411476717733150721), 또는 [첫 데모(클릭만)를 참조하세요](https://goo.gle/demo-event-level-conversion-measurement-api). - 더 많은 기능을 제공하고 Chrome에서 실험해 볼 수 있는(최초 평가판) 이 API의 다음 구현 내용을 계속해서 확인하려면 [개발자 메일링 리스트](https://groups.google.com/u/1/a/chromium.org/g/attribution-reporting-api-dev)에 등록하세요. - **GitHub**: [제안](https://github.com/WICG/conversion-measurement-api/)을 읽고 [질문을 제기하고 토론에 참여하세요](https://github.com/WICG/conversion-measurement-api/issues). - **W3C**: [웹 광고 개선 비즈니스 그룹](https://www.w3.org/community/web-adv/participants)에서 업계 사용 사례에 대해 논의하고 [개인정보 보호 커뮤니티 그룹](https://www.w3.org/community/privacycg/)에 참여하여 WebKit/Safari API에 대한 토론을 벌이세요. diff --git a/site/ko/docs/privacy-sandbox/first-party-sets/index.md b/site/ko/docs/privacy-sandbox/first-party-sets/index.md index 14aeede9d488..e1849df7933e 100644 --- a/site/ko/docs/privacy-sandbox/first-party-sets/index.md +++ b/site/ko/docs/privacy-sandbox/first-party-sets/index.md @@ -14,7 +14,7 @@ authors: ## 구현 현황 - [최초 평가판](https://web.dev/origin-trials/) Chrome 89 ~ 93 -- [최초 평가판에 등록](https://developer.chrome.com/origintrials/#/view_trial/988540118207823873) +- [최초 평가판에 등록](/origintrials/#/view_trial/988540118207823873) - [Chrome 플랫폼 현황](https://chromestatus.com/feature/5640066519007232) - [Chromium 프로젝트](https://www.chromium.org/updates/first-party-sets) @@ -69,7 +69,7 @@ authors: ## 참여 및 피드백 공유 -- **최초 평가판**: 등록 후, [Chrome 최초 평가판](https://developer.chrome.com/origintrials/#/view_trial/988540118207823873)에 참여하세요. +- **최초 평가판**: 등록 후, [Chrome 최초 평가판](/origintrials/#/view_trial/988540118207823873)에 참여하세요. - **GitHub**: [제안](https://github.com/privacycg/first-party-sets)을 읽고 [질문을 제기하고 토론에 참여하세요](https://github.com/privacycg/first-party-sets/issues). - **개발자 지원**: [개인정보 보호 샌드박스 개발자 지원 저장소](https://github.com/GoogleChromeLabs/privacy-sandbox-dev-support)에서 질문을 하고 토론에 참여하세요. diff --git a/site/ko/docs/privacy-sandbox/overview/index.md b/site/ko/docs/privacy-sandbox/overview/index.md index 3173b70ec6ac..22e2a927dbb7 100644 --- a/site/ko/docs/privacy-sandbox/overview/index.md +++ b/site/ko/docs/privacy-sandbox/overview/index.md @@ -45,7 +45,7 @@ Chrome 팀에서 개발한 주요 제안은 다음과 같습니다. ### 데이터 수집 제한 - [**개인정보 보호 예산**](https://www.youtube.com/watch?v=0STgfjSA6T8): 웹사이트가 사용자의 브라우저 또는 장치에 대한 정보를 얻을 수 있도록 허용하지만 사이트가 액세스할 수 있는 총 정보량에 대한 할당량을 브라우저에서 설정할 수 있도록 하여 사용자를 식별하지 못하게 합니다. -- [**사용자-에이전트 클라이언트 힌트**](https://web.dev/user-agent-client-hints/): [사용자-에이전트](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/User-Agent)(UA) 문자열은 중요한 패시브 [핑거프린팅](https://w3c.github.io/fingerprinting-guidance/#passive) 표면이며 처리가 까다롭습니다. 클라이언트 힌트를 사용하면 개발자가 사용자-에이전트 문자열에서 데이터 구문을 분석할 필요 없이 사용자의 장치 또는 조건에 대해 필요한 정보만 능동적으로 요청할 수 있습니다. +- [**사용자-에이전트 클라이언트 힌트**](https://web.dev/user-agent-client-hints/): [사용자-에이전트](https://developer.mozilla.org/docs/Web/HTTP/Headers/User-Agent)(UA) 문자열은 중요한 패시브 [핑거프린팅](https://w3c.github.io/fingerprinting-guidance/#passive) 표면이며 처리가 까다롭습니다. 클라이언트 힌트를 사용하면 개발자가 사용자-에이전트 문자열에서 데이터 구문을 분석할 필요 없이 사용자의 장치 또는 조건에 대해 필요한 정보만 능동적으로 요청할 수 있습니다. - [**Gnatcatcher**](https://github.com/bslassey/ip-blindness): 사용자의 IP 주소에 액세스하여 개별 사용자를 식별할 가능성을 제한합니다. 제안에는 두 부분이 있습니다: [의도적 IP 가림](https://github.com/bslassey/ip-blindness/blob/master/willful_ip_blindness.md)은 웹사이트가 브라우저에 사용자와 IP 주소를 연결하지 않음을 알릴 수 있는 방법을 제공하고, [**근접 경로 NAT**](https://github.com/bslassey/ip-blindness/blob/master/near_path_nat.md)는 사용자 그룹이 동일한 비공개 처리 서버를 통해 트래픽을 보낼 수 있게 하여 사이트 호스트로부터 해당 IP 주소를 효과적으로 숨길 수 있는 방법입니다. Gnatcatcher는 또한 남용 방지와 같은 합법적인 목적으로 IP 주소에 액세스해야 하는 사이트가 인증 및 감사를 통해 그렇게 할 수 있도록 합니다. ### 신원 diff --git a/site/ko/docs/privacy-sandbox/status/index.md b/site/ko/docs/privacy-sandbox/status/index.md index 0cf45c6b5e9c..e60be0be2ee8 100644 --- a/site/ko/docs/privacy-sandbox/status/index.md +++ b/site/ko/docs/privacy-sandbox/status/index.md @@ -16,7 +16,7 @@ authors: *이전에는 전환 측정이라고 했습니다.* - [현재 최초 평가판](https://web.dev/origin-trials/): Chrome 86에서 [이제 Chrome 93으로 확장](https://groups.google.com/u/1/a/chromium.org/g/attribution-reporting-api-dev/c/ZKf9T8sRqAM)되었습니다. -- [최초 평가판에 등록](https://developer.chrome.com/origintrials/#/view_trial/3411476717733150721) +- [최초 평가판에 등록](/origintrials/#/view_trial/3411476717733150721) - [데모](https://goo.gle/demo-event-level-conversion-measurement-api) - [Chrome 플랫폼 현황](https://www.chromestatus.com/features/6412002824028160) - [Blink 상태](https://groups.google.com/a/chromium.org/g/blink-dev/search?q=conversion%20measurement) @@ -39,7 +39,7 @@ authors: ## 신뢰 토큰 - [현재 최초 평가판](https://web.dev/origin-trials/): Chrome 84에서 [이제 Chrome 94로 확장](https://groups.google.com/a/chromium.org/g/blink-dev/c/-W90wVkS0Ks/m/Jfh5-ZWpAQAJ)되었습니다. -- [최초 평가판에 등록](https://developer.chrome.com/origintrials/#/view_trial/2479231594867458049) +- [최초 평가판에 등록](/origintrials/#/view_trial/2479231594867458049) - [데모](https://trust-token-demo.glitch.me/) - [Chrome 플랫폼 현황](https://www.chromestatus.com/feature/5078049450098688) - [Blink 상태](https://groups.google.com/a/chromium.org/g/blink-dev/search?q=trust%tokens) @@ -50,7 +50,7 @@ authors: ## 자사 세트 - [현재 최초 평가판](https://web.dev/origin-trials/) Chrome 89 ~ 93 -- [최초 평가판에 등록](https://developer.chrome.com/origintrials/#/view_trial/988540118207823873) +- [최초 평가판에 등록](/origintrials/#/view_trial/988540118207823873) - [Chrome 플랫폼 현황](https://chromestatus.com/feature/5640066519007232) - [Blink 상태](https://groups.google.com/a/chromium.org/g/blink-dev/search?q=first-party%20sets) - [API 제안](https://github.com/privacycg/first-party-sets): API 질문 및 토론에 대한 [이슈](hhttps://github.com/privacycg/first-party-sets/issues)를 참조하세요. diff --git a/site/ko/docs/privacy-sandbox/trust-tokens/index.md b/site/ko/docs/privacy-sandbox/trust-tokens/index.md index 95099dd73a2d..22f2526f715c 100644 --- a/site/ko/docs/privacy-sandbox/trust-tokens/index.md +++ b/site/ko/docs/privacy-sandbox/trust-tokens/index.md @@ -12,7 +12,7 @@ authors: ## 구현 현황 - [최초 평가판](https://web.dev/origin-trials/) Chrome 84 ~ 94 -- [평가판에 등록](https://developer.chrome.com/origintrials/#/view_trial/2479231594867458049) +- [평가판에 등록](/origintrials/#/view_trial/2479231594867458049) - [데모](https://trust-token-demo.glitch.me/) - [Chrome DevTools 통합](https://developers.google.com/web/updates/2021/01/devtools?utm_source=devtools#trust-token) - [Chrome 플랫폼 현황](https://www.chromestatus.com/feature/5078049450098688) @@ -40,7 +40,7 @@ authors: Trust Tokens API를 사용하면 웹사이트에서 신뢰하는 사용자에게 암호화 토큰을 발행할 수 있으며 나중에 다른 곳에서 이 토큰을 사용할 수 있습니다. 토큰은 사용자의 브라우저에 안전하게 저장되며 사용자의 진위를 확인하기 위해 다른 컨텍스트에서 사용할 수 있습니다. 이를 통해 사용자를 식별하거나 사이트 간에 ID를 연결하지 않고 한 웹사이트(예: 소셜 미디어 사이트 또는 이메일 서비스)에서 사용자의 신뢰를 다른 웹사이트(예: 게시자 또는 온라인 상점)로 전달할 수 있습니다. -{% Aside 'key-term' %} [핑거프린팅](https://w3c.github.io/fingerprinting-guidance/#passive)을 사용하면 사이트에서 장치, 운영 체제 및 브라우저 설정(예: 언어 기본 설정, [사용자 에이전트](https://developer.mozilla.org/en-US/docs/Web/API/NavigatorID/userAgent) 및 사용 가능한 글꼴) 또는 장치 상태 변경에 대한 데이터를 가져와 개별 사용자를 식별하고 추적할 수 있습니다. 이 작업은 요청 헤더를 확인하여 서버에서, 또는 JavaScript를 사용하여 클라이언트에서 수행할 수 있습니다. +{% Aside 'key-term' %} [핑거프린팅](https://w3c.github.io/fingerprinting-guidance/#passive)을 사용하면 사이트에서 장치, 운영 체제 및 브라우저 설정(예: 언어 기본 설정, [사용자 에이전트](https://developer.mozilla.org/docs/Web/API/NavigatorID/userAgent) 및 사용 가능한 글꼴) 또는 장치 상태 변경에 대한 데이터를 가져와 개별 사용자를 식별하고 추적할 수 있습니다. 이 작업은 요청 헤더를 확인하여 서버에서, 또는 JavaScript를 사용하여 클라이언트에서 수행할 수 있습니다. 핑거프린팅은 사용자가 인식하지 못하고 제어할 수 없는 메커니즘을 사용합니다. 지문 데이터를 결합하여 개인을 식별하는 방법을 알아보려면 [Panopticlick](https://panopticlick.eff.org/) 및 [amiunique.org](https://amiunique.org/)와 같은 사이트를 참조하세요. {% endAside %} @@ -68,7 +68,7 @@ Trust Tokens API를 사용하면 웹사이트에서 신뢰하는 사용자에게 ## 참여 및 피드백 공유 -- **최초 평가판**: 등록 후, [Chrome 최초 평가판](https://developer.chrome.com/origintrials/#/view_trial/2479231594867458049)에 참여하세요. +- **최초 평가판**: 등록 후, [Chrome 최초 평가판](/origintrials/#/view_trial/2479231594867458049)에 참여하세요. - **데모**: 신뢰 토큰 [발행 및 회수](https://trust-token-demo.glitch.me/)를 사용해 보세요. - **GitHub**: [제안](https://github.com/WICG/trust-token-api)을 읽고 [질문을 제기하고 토론에 참여하세요](https://github.com/WICG/trust-token-api/issues). - **W3C**: [웹 광고 개선 비즈니스 그룹](https://www.w3.org/community/web-adv/participants)에서 업계 사용 사례에 대해 논의하세요. diff --git a/site/pt/blog/new-in-devtools-93/index.md b/site/pt/blog/new-in-devtools-93/index.md index 6a44b67a0c1b..3694e00994b1 100644 --- a/site/pt/blog/new-in-devtools-93/index.md +++ b/site/pt/blog/new-in-devtools-93/index.md @@ -55,7 +55,7 @@ Issue relacionada: [1182537](https://crbug.com/1182537) Os erros da Attribution Reporting API agora são relatados na guia **Issues**. -[Attribution Reporting](https://developer.chrome.com/docs/privacy-sandbox/attribution-reporting/) é uma nova API para ajudá-lo a medir quando uma ação do usuário (como um clique no anúncio ou visualização) leva a uma conversão, sem usar identificadores entre sites. +[Attribution Reporting](/docs/privacy-sandbox/attribution-reporting/) é uma nova API para ajudá-lo a medir quando uma ação do usuário (como um clique no anúncio ou visualização) leva a uma conversão, sem usar identificadores entre sites. {% Img src="image/dPDCek3EhZgLQPGtEG3y0fTn4v82/bkEGVEv5kKc9M6qBUmLz.png", alt="Attribution Reporting API errors in the Issues tab", width="800", height="501" %} diff --git a/site/pt/blog/new-in-devtools-95/index.md b/site/pt/blog/new-in-devtools-95/index.md index bbe429f4dd93..cfdf8cdc61ae 100644 --- a/site/pt/blog/new-in-devtools-95/index.md +++ b/site/pt/blog/new-in-devtools-95/index.md @@ -95,8 +95,8 @@ link.access = 'admin'; link.search = `?access=${link.access}`; ``` - -Tente registrar `link` no **Console**. Propriedades customizadas agora estão em destaque e ordenadas primeiro. Essas alterações facilitam a localização de propriedades customizadas, especialmente para [Web APIs](https://developer.mozilla.org/en-US/docs/Web/API)(por exemplo, `URL`) com muitas propriedades herdadas. + +Tente registrar `link` no **Console**. Propriedades customizadas agora estão em destaque e ordenadas primeiro. Essas alterações facilitam a localização de propriedades customizadas, especialmente para [Web APIs](https://developer.mozilla.org/docs/Web/API)(por exemplo, `URL`) com muitas propriedades herdadas. {% Img src="image/dPDCek3EhZgLQPGtEG3y0fTn4v82/Ngjx6YRQsH3Fhl6DUZYl.png", alt="As propriedades customizadas estão em negrito e classificadas primeiro", width="800", height="561" %} diff --git a/site/pt/blog/new-in-devtools-96/index.md b/site/pt/blog/new-in-devtools-96/index.md index 86e90e14e307..5eca11a07aca 100644 --- a/site/pt/blog/new-in-devtools-96/index.md +++ b/site/pt/blog/new-in-devtools-96/index.md @@ -211,8 +211,8 @@ Issues relacionadas: [1232937](https://crbug.com/1232937), [1255586](https://crb ## Obsolescência do Painel de cache no painel do Aplicativo {: #app-cache } - -O painel [Cache do aplicativo](https://developer.chrome.com/docs/devtools/storage/applicationcache/) no painel do aplicativo foi removido pois o suporte para [AppCache](https://web.dev/appcache-removal/) foi removido do Chrome e de outros navegadores baseados em Chromium. + +O painel [Cache do aplicativo](/docs/devtools/storage/applicationcache/) no painel do aplicativo foi removido pois o suporte para [AppCache](https://web.dev/appcache-removal/) foi removido do Chrome e de outros navegadores baseados em Chromium. {# https://chromium.googlesource.com/devtools/devtools-frontend/+/de4d15e955d6145674e3885cde8a5a70f1269b79 #} diff --git a/site/pt/docs/privacy-sandbox/attribution-reporting-introduction/index.md b/site/pt/docs/privacy-sandbox/attribution-reporting-introduction/index.md index 0f157a119533..9aba0965aca7 100644 --- a/site/pt/docs/privacy-sandbox/attribution-reporting-introduction/index.md +++ b/site/pt/docs/privacy-sandbox/attribution-reporting-introduction/index.md @@ -30,7 +30,7 @@ Esta proposta está sendo incubada de forma aberta. A proposta e as discussões ## Por que esta API é necessária? -Hoje, a mensuração da conversão de anúncios geralmente depende [de cookies de terceiros](https://developer.mozilla.org/en-US/docs/Web/HTTP/Cookies#Third-party_cookies). Os navegadores estão restringindo o acesso a cookies de terceiros porque eles podem ser usados para rastrear usuários em sites e prejudicar a privacidade do usuário. Esta API viabiliza essas medições de uma forma que preserva a privacidade, sem usar cookies de terceiros. +Hoje, a mensuração da conversão de anúncios geralmente depende [de cookies de terceiros](https://developer.mozilla.org/docs/Web/HTTP/Cookies#Third-party_cookies). Os navegadores estão restringindo o acesso a cookies de terceiros porque eles podem ser usados para rastrear usuários em sites e prejudicar a privacidade do usuário. Esta API viabiliza essas medições de uma forma que preserva a privacidade, sem usar cookies de terceiros. ## Quem precisa saber sobre esta API? @@ -71,7 +71,7 @@ Se estiver experimentando a API no Chrome, você terá acesso a todos os recurso #### Experimente com usuários finais num site implantado -1. Ative a API para usuários finais registrando-se para um [ensaio de origem](https://developer.chrome.com/blog/origin-trials/), se disponível. Um ensaio de origem dá acesso a um recurso experimental, para construir uma funcionalidade que você pode experimentar por um tempo limitado. Observe que [os ensaios de origem](https://developer.chrome.com/blog/third-party-origin-trials/) de terceiros possibilitam que atores terceirizados, tais como como servidores de anúncios e provedores de medição, testem uma API entre múltiplos sites. **Para saber quais são os ensaios de origem que estão atualmente disponíveis para esta API, vá para [Status](#status)**. Para ser informado sobre ensaios de origem futuros, participe da [lista de e-mails sobre Attribution Reporting para desenvolvedores](https://groups.google.com/u/1/a/chromium.org/g/attribution-reporting-api-dev). +1. Ative a API para usuários finais registrando-se para um [ensaio de origem](/blog/origin-trials/), se disponível. Um ensaio de origem dá acesso a um recurso experimental, para construir uma funcionalidade que você pode experimentar por um tempo limitado. Observe que [os ensaios de origem](/blog/third-party-origin-trials/) de terceiros possibilitam que atores terceirizados, tais como como servidores de anúncios e provedores de medição, testem uma API entre múltiplos sites. **Para saber quais são os ensaios de origem que estão atualmente disponíveis para esta API, vá para [Status](#status)**. Para ser informado sobre ensaios de origem futuros, participe da [lista de e-mails sobre Attribution Reporting para desenvolvedores](https://groups.google.com/u/1/a/chromium.org/g/attribution-reporting-api-dev). 2. Integre a API aos seus sites e sistemas. @@ -138,8 +138,8 @@ Outros recursos propostos nesta API são [a atribuição app-to-web](https://git {% Aside %} No futuro, sem cookies de terceiros, esta API seria combinada com outras APIs de anúncios que preservam a privacidade para cobrir casos de uso de ponta a ponta: -- Remarketing: veja [FLEDGE](https://developer.chrome.com/docs/privacy-sandbox/fledge/) -- Seleção de anúncios com base em interesses: veja [FLoC](https://developer.chrome.com/docs/privacy-sandbox/floc/) +- Remarketing: veja [FLEDGE](/docs/privacy-sandbox/fledge/) +- Seleção de anúncios com base em interesses: veja [FLoC](/docs/privacy-sandbox/floc/) {% endAside %} @@ -155,7 +155,7 @@ Status: - `🧪 Experiment (BROWSER_NAME)` : um experimento está disponível em BROWSER_NAME. No Chrome, um experimento é chamado de ensaio de origem. - `🚀 Stable (BROWSER_NAME)` : o recurso é fornecido por default no BROWSER_NAME. -{% Aside %} [Ensaio de origem atual](https://developer.chrome.com/origintrials/#/view_trial/3411476717733150721) (Chrome experiment 🧪) {% endAside %} +{% Aside %} [Ensaio de origem atual](/origintrials/#/view_trial/3411476717733150721) (Chrome experiment 🧪) {% endAside %} {% Aside 'caution' %} Vários testes de origem (experimentos) serão executados. Cada rodada é usada para melhorar e ajustar a API com base no feedback do ecossistema. {% endAside %} @@ -342,7 +342,7 @@ Os relatórios agregados associam um clique detalhado ou evento de visualizaçã ## Sites e controle do usuário - Os usuários podem desativar o recurso através das configurações do usuário em `chrome://settings/privacySandbox` . -- Por default, o recurso é habilitado em contextos de nível superior. Terceiros arbitrários não podem usar a API sem o conhecimento do editor, porque a API de relatórios de atribuição precisa ser ativada em iframes filhos por meio de uma [política de permissões](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Feature-Policy). +- Por default, o recurso é habilitado em contextos de nível superior. Terceiros arbitrários não podem usar a API sem o conhecimento do editor, porque a API de relatórios de atribuição precisa ser ativada em iframes filhos por meio de uma [política de permissões](https://developer.mozilla.org/docs/Web/HTTP/Headers/Feature-Policy). ## Questões abertas diff --git a/site/pt/docs/privacy-sandbox/attribution-reporting/index.md b/site/pt/docs/privacy-sandbox/attribution-reporting/index.md index 4832ac068b37..6a2b2d3c1c25 100644 --- a/site/pt/docs/privacy-sandbox/attribution-reporting/index.md +++ b/site/pt/docs/privacy-sandbox/attribution-reporting/index.md @@ -40,7 +40,7 @@ Você talvez também queira consultar o [Glossário completo do Privacy Sandbox] ## Por que essa API é necessária? {: #why-is-this-api-needed } -Hoje, a medição de conversão de anúncios geralmente depende de [cookies de terceiros](https://developer.mozilla.org/en-US/docs/Web/HTTP/Cookies#Third-party_cookies). Os navegadores estão restringindo o acesso a cookies de terceiros porque eles podem ser usados para rastrear usuários em sites e prejudicar a privacidade do usuário. Esta API permite essas medições de uma forma que preserva a privacidade, sem cookies de terceiros. +Hoje, a medição de conversão de anúncios geralmente depende de [cookies de terceiros](https://developer.mozilla.org/docs/Web/HTTP/Cookies#Third-party_cookies). Os navegadores estão restringindo o acesso a cookies de terceiros porque eles podem ser usados para rastrear usuários em sites e prejudicar a privacidade do usuário. Esta API permite essas medições de uma forma que preserva a privacidade, sem cookies de terceiros. ## Como funciona a API Attribution Reporting e quais são seus recursos? @@ -57,7 +57,7 @@ A API oferece dois tipos de relatórios de atribuição que podem ser usados par ## Envolva-se e compartilhe feedback {: #engage } -- **Ensaio de origem**: [registre-se para o primeiro ensaio de origem (apenas cliques)](https://developer.chrome.com/origintrials/#/view_trial/3411476717733150721) ou [veja a primeira demo (apenas cliques)](https://goo.gle/demo-event-level-conversion-measurement-api) . +- **Ensaio de origem**: [registre-se para o primeiro ensaio de origem (apenas cliques)](/origintrials/#/view_trial/3411476717733150721) ou [veja a primeira demo (apenas cliques)](https://goo.gle/demo-event-level-conversion-measurement-api) . - Para ficar por dentro da próxima implementação dessa API que vai oferecer mais recursos e ficar disponível para experimentação no Chrome (ensaio de origem), participe da [lista de discussão para desenvolvedores](https://groups.google.com/u/1/a/chromium.org/g/attribution-reporting-api-dev). - **GitHub**: Leia a [proposta](https://github.com/WICG/conversion-measurement-api/), [levante questões e acompanhe a discussão](https://github.com/WICG/conversion-measurement-api/issues). - **W3C** : discuta os casos de uso da indústria no [Improving Web Advertising Business Group](https://www.w3.org/community/web-adv/participants) e participe do [Privacy Community Group](https://www.w3.org/community/privacycg/) para discussões sobre a API WebKit/Safari. diff --git a/site/pt/docs/privacy-sandbox/first-party-sets/index.md b/site/pt/docs/privacy-sandbox/first-party-sets/index.md index f7fc006db328..142f297e415e 100644 --- a/site/pt/docs/privacy-sandbox/first-party-sets/index.md +++ b/site/pt/docs/privacy-sandbox/first-party-sets/index.md @@ -14,7 +14,7 @@ authors: ## Status de implementação - [Em ensaio de origem](https://web.dev/origin-trials/) no Chrome 89 a 93. -- [Cadastre-se para o ensaio de origem](https://developer.chrome.com/origintrials/#/view_trial/988540118207823873). +- [Cadastre-se para o ensaio de origem](/origintrials/#/view_trial/988540118207823873). - [Status da plataforma Chrome](https://chromestatus.com/feature/5640066519007232). - [Projetos Chromium](https://www.chromium.org/updates/first-party-sets) . @@ -69,7 +69,7 @@ Isso significa que quando um visitante em b.example ou c.example faz uma solicit ## Envolva-se e compartilhe feedback -- **Ensaio de origem**: cadastre-se e participe do [ensaio de origem](https://developer.chrome.com/origintrials/#/view_trial/988540118207823873) do Chrome. +- **Ensaio de origem**: cadastre-se e participe do [ensaio de origem](/origintrials/#/view_trial/988540118207823873) do Chrome. - **GitHub**: Leia a [proposta](https://github.com/privacycg/first-party-sets), [levante questões e acompanhe a discussão](https://github.com/privacycg/first-party-sets/issues) . - **Suporte ao desenvolvedor**: faça perguntas e participe de discussões no [repositório Privacy Sandbox Developer Support](https://github.com/GoogleChromeLabs/privacy-sandbox-dev-support) . diff --git a/site/pt/docs/privacy-sandbox/overview/index.md b/site/pt/docs/privacy-sandbox/overview/index.md index f6165864a03d..69e354dba534 100644 --- a/site/pt/docs/privacy-sandbox/overview/index.md +++ b/site/pt/docs/privacy-sandbox/overview/index.md @@ -45,7 +45,7 @@ As principais propostas desenvolvidas pela equipe do Chrome estão listadas abai ### Limitação da coleta de dados - [**Privacy Budget**](https://www.youtube.com/watch?v=0STgfjSA6T8): permite que os sites obtenham informações sobre o navegador ou dispositivo de um usuário, mas permite que o navegador defina uma cota na quantidade total de informações que um site pode acessar, de modo que o usuário não possa ser identificado. -- [**User-Agent Client Hints**](https://web.dev/user-agent-client-hints/): A string [User-Agent](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/User-Agent) (UA) é uma [significativa superfície de](https://w3c.github.io/fingerprinting-guidance/#passive)[fingerprinting](https://w3c.github.io/fingerprinting-guidance/#passive) passiva, além de ser difícil de processar. Client Hints (dicas do cliente) permitem que os desenvolvedores solicitem ativamente apenas as informações de que precisam sobre o dispositivo do usuário ou condições, em vez de precisar processar esses dados na string User-Agent. +- [**User-Agent Client Hints**](https://web.dev/user-agent-client-hints/): A string [User-Agent](https://developer.mozilla.org/docs/Web/HTTP/Headers/User-Agent) (UA) é uma [significativa superfície de](https://w3c.github.io/fingerprinting-guidance/#passive)[fingerprinting](https://w3c.github.io/fingerprinting-guidance/#passive) passiva, além de ser difícil de processar. Client Hints (dicas do cliente) permitem que os desenvolvedores solicitem ativamente apenas as informações de que precisam sobre o dispositivo do usuário ou condições, em vez de precisar processar esses dados na string User-Agent. - [**Gnatcatcher**](https://github.com/bslassey/ip-blindness): Limita a capacidade de identificar usuários individuais acessando seus endereços IP. A proposta tem duas partes: [**Willful IP Blindness**](https://github.com/bslassey/ip-blindness/blob/master/willful_ip_blindness.md) fornece uma maneira para os sites informarem aos navegadores que eles não estão conectando endereços IP aos usuários e [**Near-path NAT**](https://github.com/bslassey/ip-blindness/blob/master/near_path_nat.md) permite que grupos de usuários enviem seu tráfego através do mesmo servidor de privatização, efetivamente ocultando seus endereços IP de um host. O Gnatcatcher também garante que os sites que requerem acesso a endereços IP para fins legítimos, como prevenção de abusos, possam fazê-lo, sujeito a certificação e auditoria. ### Identidade diff --git a/site/pt/docs/privacy-sandbox/status/index.md b/site/pt/docs/privacy-sandbox/status/index.md index 26bc31126cd0..8fb3f67948e5 100644 --- a/site/pt/docs/privacy-sandbox/status/index.md +++ b/site/pt/docs/privacy-sandbox/status/index.md @@ -16,7 +16,7 @@ authors: *Anteriormente conhecido como Conversion Measurement (mensuração de conversão).* - [Ensaio de origem atual](https://web.dev/origin-trials/): do Chrome 86, [agora estendido](https://groups.google.com/u/1/a/chromium.org/g/attribution-reporting-api-dev/c/ZKf9T8sRqAM) ao Chrome 93. -- [Cadastre-se para o ensaio de origem](https://developer.chrome.com/origintrials/#/view_trial/3411476717733150721). +- [Cadastre-se para o ensaio de origem](/origintrials/#/view_trial/3411476717733150721). - [Demo](https://goo.gle/demo-event-level-conversion-measurement-api). - [Status da plataforma Chrome](https://www.chromestatus.com/features/6412002824028160). - [Status do Blink](https://groups.google.com/a/chromium.org/g/blink-dev/search?q=conversion%20measurement) . @@ -39,7 +39,7 @@ Veja o [status](/docs/privacy-sandbox/attribution-reporting-introduction/#status ## Trust Tokens - [Ensaio de origem atual](https://web.dev/origin-trials/): do Chrome 84, [agora estendido](https://groups.google.com/a/chromium.org/g/blink-dev/c/-W90wVkS0Ks/m/Jfh5-ZWpAQAJ) ao Chrome 94. -- [Cadastre-se para o ensaio de origem](https://developer.chrome.com/origintrials/#/view_trial/2479231594867458049). +- [Cadastre-se para o ensaio de origem](/origintrials/#/view_trial/2479231594867458049). - [Demo](https://trust-token-demo.glitch.me/). - [Status da plataforma Chrome](https://www.chromestatus.com/feature/5078049450098688). - [Status do Blink](https://groups.google.com/a/chromium.org/g/blink-dev/search?q=trust%tokens) . @@ -50,7 +50,7 @@ Veja o [status](/docs/privacy-sandbox/attribution-reporting-introduction/#status ## Conjuntos primários - [Ensaio de origem atual](https://web.dev/origin-trials/): Chrome 89 a 93. -- [Cadastre-se para o ensaio de origem](https://developer.chrome.com/origintrials/#/view_trial/988540118207823873). +- [Cadastre-se para o ensaio de origem](/origintrials/#/view_trial/988540118207823873). - [Status da plataforma Chrome](https://chromestatus.com/feature/5640066519007232). - [Status do Blink](https://groups.google.com/a/chromium.org/g/blink-dev/search?q=first-party%20sets) . - [Proposta de API](https://github.com/privacycg/first-party-sets): veja os [issues](hhttps://github.com/privacycg/first-party-sets/issues) para perguntas e discussões sobre a API. @@ -93,7 +93,7 @@ Descendente do [TURTLEDOVE](https://github.com/WICG/turtledove) . - [Introdução aos ensaios de origem do Chrome](https://web.dev/origin-trials/) - [O que são ensaios de origem de terceiros?](https://web.dev/third-party-origin-trials) -- [Solução de problemas para ensaios de origem do Chrome](https://developer.chrome.com/blog/origin-trial-troubleshooting/) +- [Solução de problemas para ensaios de origem do Chrome](/blog/origin-trial-troubleshooting/) - [Guia de ensaios de origem para desenvolvedores web](https://github.com/GoogleChrome/OriginTrials/blob/gh-pages/developer-guide.md) - [Explicação sobre ensaios de origem](https://github.com/GoogleChrome/OriginTrials/blob/gh-pages/explainer.md) - [Executando um ensaio de origem](https://www.chromium.org/blink/origin-trials/running-an-origin-trial) diff --git a/site/pt/docs/privacy-sandbox/trust-tokens/index.md b/site/pt/docs/privacy-sandbox/trust-tokens/index.md index 57008c67bcfb..fe75fa14d9d7 100644 --- a/site/pt/docs/privacy-sandbox/trust-tokens/index.md +++ b/site/pt/docs/privacy-sandbox/trust-tokens/index.md @@ -12,7 +12,7 @@ authors: ## Status de implementação - [Em ensaio de origem](https://web.dev/origin-trials/): Chrome 84 a 94. -- [Cadastre-se para o ensaio](https://developer.chrome.com/origintrials/#/view_trial/2479231594867458049). +- [Cadastre-se para o ensaio](/origintrials/#/view_trial/2479231594867458049). - [Demo](https://trust-token-demo.glitch.me/). - [Integração do Chrome DevTools](https://developers.google.com/web/updates/2021/01/devtools?utm_source=devtools#trust-token). - [Status da plataforma Chrome](https://www.chromestatus.com/feature/5078049450098688). @@ -40,7 +40,7 @@ Infelizmente, muitos mecanismos existentes para medir e propagar confiabilidade Com a API Trust Tokens, um site pode emitir tokens criptográficos para um usuário de sua confiança, que podem ser usados posteriormente em outro lugar. Os tokens são armazenados com segurança pelo navegador do usuário e podem ser resgatados em outros contextos para confirmar a autenticidade do usuário. Isto permite que a confiança de um usuário em um site (como um site de mídia social ou serviço de e-mail) seja transmitida a outro site (como um editor ou loja online) sem identificar o usuário ou vincular identidades entre sites. -{% Aside 'key-term' %} [Fingerprinting](https://w3c.github.io/fingerprinting-guidance/#passive) permite que os sites identifiquem e rastreiem usuários individuais, obtendo dados sobre seus dispositivos, sistema operacional e configuração do navegador (como preferências de idioma, [user agent](https://developer.mozilla.org/en-US/docs/Web/API/NavigatorID/userAgent) e fontes disponíveis) ou alterações no estado do dispositivo. Isto pode ser feito no servidor verificando os cabeçalhos das solicitações ou no cliente com JavaScript. +{% Aside 'key-term' %} [Fingerprinting](https://w3c.github.io/fingerprinting-guidance/#passive) permite que os sites identifiquem e rastreiem usuários individuais, obtendo dados sobre seus dispositivos, sistema operacional e configuração do navegador (como preferências de idioma, [user agent](https://developer.mozilla.org/docs/Web/API/NavigatorID/userAgent) e fontes disponíveis) ou alterações no estado do dispositivo. Isto pode ser feito no servidor verificando os cabeçalhos das solicitações ou no cliente com JavaScript. O fingerprinting usa mecanismos que os usuários não conhecem e não podem controlar. Sites como [Panopticlick](https://panopticlick.eff.org/) e [amiunique.org](https://amiunique.org/) mostram como os dados de fingerprint podem ser combinados para identificar uma pessoa como indivíduo. {% endAside %} @@ -68,7 +68,7 @@ Neste exemplo, um site de editor deseja verificar se um usuário é um ser human ## Envolva-se e compartilhe feedback -- **Ensaio de origem**: cadastre-se e participe do [ensaio de origem](https://developer.chrome.com/origintrials/#/view_trial/2479231594867458049) do Chrome. +- **Ensaio de origem**: cadastre-se e participe do [ensaio de origem](/origintrials/#/view_trial/2479231594867458049) do Chrome. - **Demo**: experimente a [emissão e o resgate](https://trust-token-demo.glitch.me/) de trust tokens. - **GitHub**: Leia a [proposta](https://github.com/WICG/trust-token-api), [levante questões e acompanhe a discussão](https://github.com/WICG/trust-token-api/issues). - **W3C**: Discuta os casos de uso da indústria no [Improving Web Advertising Business Group](https://www.w3.org/community/web-adv/participants). diff --git a/site/ru/blog/new-in-devtools-93/index.md b/site/ru/blog/new-in-devtools-93/index.md index a3d80fd0ef48..e9cf81e24a2e 100644 --- a/site/ru/blog/new-in-devtools-93/index.md +++ b/site/ru/blog/new-in-devtools-93/index.md @@ -87,7 +87,7 @@ https://chromium.googlesource.com/devtools/devtools-frontend/+/e7672c40f2febc807 **Issues**. [Attribution -Reporting](https://developer.chrome.com/docs/privacy-sandbox/attribution-reporting/) +Reporting](/docs/privacy-sandbox/attribution-reporting/) это новый API, который поможет вам понять, когда действия пользователя (например, клик или просмотр рекламы) приводят к конверсии, без использования межсайтовых идентификаторов. diff --git a/site/ru/blog/new-in-devtools-95/index.md b/site/ru/blog/new-in-devtools-95/index.md index 2dac9c86ca67..693d8c2411dd 100644 --- a/site/ru/blog/new-in-devtools-95/index.md +++ b/site/ru/blog/new-in-devtools-95/index.md @@ -113,10 +113,10 @@ link.access = 'admin'; link.search = `?access=${link.access}`; ``` - + Попробуйте вывести `link` в **Консоль** (Console). Собственные свойства отображаются вверху списка и выделены жирным. Эти изменения облегчают поиск кастомных свойств, особенно для [Web -APIs](https://developer.mozilla.org/en-US/docs/Web/API) (например, `URL`) с множеством +APIs](https://developer.mozilla.org/docs/Web/API) (например, `URL`) с множеством унаследованных свойств. {% Img src="image/dPDCek3EhZgLQPGtEG3y0fTn4v82/Ngjx6YRQsH3Fhl6DUZYl.png", alt="Собственные свойства diff --git a/site/ru/blog/new-in-devtools-96/index.md b/site/ru/blog/new-in-devtools-96/index.md index 3d79ae2f3170..485bc332df71 100644 --- a/site/ru/blog/new-in-devtools-96/index.md +++ b/site/ru/blog/new-in-devtools-96/index.md @@ -234,8 +234,8 @@ DevTools теперь отображает стек трассировки `asyn ## Устаревшая панель Кэш приложения на вкладке Приложение {: #app-cache } - -Панель [Кеш приложений](https://developer.chrome.com/docs/devtools/storage/applicationcache/) (Application cache) на вкладке Приложение (Application) удалена, поскольку [AppCache](https://web.dev/appcache-removal/) больше не поддерживается в Chrome и других браузерах на основе Chromium. + +Панель [Кеш приложений](/docs/devtools/storage/applicationcache/) (Application cache) на вкладке Приложение (Application) удалена, поскольку [AppCache](https://web.dev/appcache-removal/) больше не поддерживается в Chrome и других браузерах на основе Chromium. {# https://chromium.googlesource.com/devtools/devtools-frontend/+/de4d15e955d6145674e3885cde8a5a70f1269b79 #} diff --git a/site/ru/docs/privacy-sandbox/attribution-reporting-introduction/index.md b/site/ru/docs/privacy-sandbox/attribution-reporting-introduction/index.md index b099b592db2d..a09c8f64ebc4 100644 --- a/site/ru/docs/privacy-sandbox/attribution-reporting-introduction/index.md +++ b/site/ru/docs/privacy-sandbox/attribution-reporting-introduction/index.md @@ -71,7 +71,7 @@ Attribution Reporting API позволяет отслеживать, когда #### Экспериментируйте с конечными пользователями на развернутом сайте -1. Включите API для конечных пользователей, зарегистрировавшись в [пробной версии источника](https://developer.chrome.com/blog/origin-trials/), если она доступна. Пробная версия источника временно открывает доступ к экспериментальной функции, на основе которой можно создать свою функциональность. Обратите внимание, что [сторонние пробные версии источника](https://developer.chrome.com/blog/third-party-origin-trials/) позволяют сторонним участникам, таким как поставщики услуг показа и измерения рекламы, тестировать API на нескольких сайтах. **Чтобы увидеть, какие пробные версии источника для этого API сейчас доступны, перейдите в раздел [«Статус»](#status)**. А чтобы узнавать о будущих пробных версиях источника, присоединяйтесь к [списку рассылки Attribution Reporting для разработчиков](https://groups.google.com/u/1/a/chromium.org/g/attribution-reporting-api-dev). +1. Включите API для конечных пользователей, зарегистрировавшись в [пробной версии источника](/blog/origin-trials/), если она доступна. Пробная версия источника временно открывает доступ к экспериментальной функции, на основе которой можно создать свою функциональность. Обратите внимание, что [сторонние пробные версии источника](/blog/third-party-origin-trials/) позволяют сторонним участникам, таким как поставщики услуг показа и измерения рекламы, тестировать API на нескольких сайтах. **Чтобы увидеть, какие пробные версии источника для этого API сейчас доступны, перейдите в раздел [«Статус»](#status)**. А чтобы узнавать о будущих пробных версиях источника, присоединяйтесь к [списку рассылки Attribution Reporting для разработчиков](https://groups.google.com/u/1/a/chromium.org/g/attribution-reporting-api-dev). 2. Интегрируйте API в свои сайты и системы. @@ -138,8 +138,8 @@ Attribution Reporting API позволяет отслеживать, когда {% Aside %} В будущем, когда сторонние cookie перестанут использоваться, этот API будет объединен с другими сохраняющими конфиденциальность API для рекламы, чтобы обеспечить сквозной процесс отслеживания: -- ремаркетинг: см. [FLEDGE](https://developer.chrome.com/docs/privacy-sandbox/fledge/); -- отбор объявлений на основе интересов: см. [FLoC](https://developer.chrome.com/docs/privacy-sandbox/floc/). +- ремаркетинг: см. [FLEDGE](/docs/privacy-sandbox/fledge/); +- отбор объявлений на основе интересов: см. [FLoC](/docs/privacy-sandbox/floc/). {% endAside %} @@ -155,7 +155,7 @@ Attribution Reporting API позволяет отслеживать, когда - `🧪 Experiment (BROWSER_NAME)`: функция доступна для экспериментов в BROWSER_NAME. В Chrome такая экспериментальная функция называется пробной версией источника; - `🚀 Stable (BROWSER_NAME)`: функция по умолчанию интегрирована в BROWSER_NAME. -{% Aside %} [Текущая пробная версия источника](https://developer.chrome.com/origintrials/#/view_trial/3411476717733150721) (экспериментальная функция Chrome 🧪) {% endAside %} +{% Aside %} [Текущая пробная версия источника](/origintrials/#/view_trial/3411476717733150721) (экспериментальная функция Chrome 🧪) {% endAside %} {% Aside 'caution' %}Испытания (эксперименты) будут проводиться с несколькими пробными версиями источника. В каждом раунде в API будут вноситься улучшения и корректировки на основе отзывов от участников экосистемы. {% endAside %} @@ -342,7 +342,7 @@ Attribution Reporting API позволяет отслеживать, когда ## Сайты и пользовательский контроль - Пользователи могут отключить эту функцию в пользовательских настройках: `chrome://settings/privacySandbox`. -- По умолчанию функция включена в контекстах верхнего уровня. Произвольные третьи стороны не могут использовать API без ведома издателя, потому что Attribution Reporting API необходимо включать в дочерних блоках iframe с помощью [политики разрешений](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Feature-Policy). +- По умолчанию функция включена в контекстах верхнего уровня. Произвольные третьи стороны не могут использовать API без ведома издателя, потому что Attribution Reporting API необходимо включать в дочерних блоках iframe с помощью [политики разрешений](https://developer.mozilla.org/docs/Web/HTTP/Headers/Feature-Policy). ## Открытые вопросы diff --git a/site/ru/docs/privacy-sandbox/attribution-reporting/index.md b/site/ru/docs/privacy-sandbox/attribution-reporting/index.md index dbb7e93c4e9f..21ccd3111bc9 100644 --- a/site/ru/docs/privacy-sandbox/attribution-reporting/index.md +++ b/site/ru/docs/privacy-sandbox/attribution-reporting/index.md @@ -40,7 +40,7 @@ authors: ## Зачем нужен этот API? {: #why-is-this-api-required } -Сегодня для измерения конверсии рекламы часто используются [сторонние cookie](https://developer.mozilla.org/en-US/docs/Web/HTTP/Cookies#Third-party_cookies). Однако для сохранения конфиденциальности пользователей браузеры ограничивают доступ к сторонним cookie, чтобы с их помощью нельзя было отследить перемещение пользователей между сайтами. Данный API позволяет проводить такие измерения с сохранением конфиденциальности без сторонних cookie. +Сегодня для измерения конверсии рекламы часто используются [сторонние cookie](https://developer.mozilla.org/docs/Web/HTTP/Cookies#Third-party_cookies). Однако для сохранения конфиденциальности пользователей браузеры ограничивают доступ к сторонним cookie, чтобы с их помощью нельзя было отследить перемещение пользователей между сайтами. Данный API позволяет проводить такие измерения с сохранением конфиденциальности без сторонних cookie. ## Как работает Attribution Reporting API и каковы его возможности? @@ -57,7 +57,7 @@ API предлагает два типа отчетов об атрибуции ## Присоединяйтесь и делитесь отзывами {: #engage } -- **Пробная версия источника**: [зарегистрируйтесь, чтобы поработать с первой пробной версией источника (только клики)](https://developer.chrome.com/origintrials/#/view_trial/3411476717733150721) или [посмотреть первую демоверсию (только клики)](https://goo.gle/demo-event-level-conversion-measurement-api). +- **Пробная версия источника**: [зарегистрируйтесь, чтобы поработать с первой пробной версией источника (только клики)](/origintrials/#/view_trial/3411476717733150721) или [посмотреть первую демоверсию (только клики)](https://goo.gle/demo-event-level-conversion-measurement-api). - Чтобы следить за последующими реализациями этого API, в которых появится больше возможностей и которые будут доступны для экспериментов в Chrome (в виде пробной версии источника), присоединяйтесь к [списку рассылки для разработчиков](https://groups.google.com/u/1/a/chromium.org/g/attribution-reporting-api-dev). - **GitHub**: ознакомьтесь с [текстом предложения](https://github.com/WICG/conversion-measurement-api/) и [обсуждением, где можно задать свои вопросы](https://github.com/WICG/conversion-measurement-api/issues). - **W3C**: обсуждайте отраслевые варианты использования в [группе Improving Web Advertising Business Group](https://www.w3.org/community/web-adv/participants) и присоединяйтесь к [группе Privacy Community Group](https://www.w3.org/community/privacycg/) для обсуждения WebKit/Safari API. diff --git a/site/ru/docs/privacy-sandbox/first-party-sets/index.md b/site/ru/docs/privacy-sandbox/first-party-sets/index.md index 60858540e676..3bb9d1bfb5de 100644 --- a/site/ru/docs/privacy-sandbox/first-party-sets/index.md +++ b/site/ru/docs/privacy-sandbox/first-party-sets/index.md @@ -14,7 +14,7 @@ authors: ## Статус реализации - [Доступно в рамках испытания Origin Trial](https://web.dev/origin-trials/) в Chrome с 89 по 93. -- [Регистрация для участия в испытании Origin Trial](https://developer.chrome.com/origintrials/#/view_trial/988540118207823873). +- [Регистрация для участия в испытании Origin Trial](/origintrials/#/view_trial/988540118207823873). - [Статус платформы Chrome](https://chromestatus.com/feature/5640066519007232). - [Проекты Chromium](https://www.chromium.org/updates/first-party-sets). @@ -69,7 +69,7 @@ authors: ## Участвуйте и делитесь отзывами -- **Испытание Origin Trial**: зарегистрируйтесь и примите участие в [испытании Chrome Origin Trial](https://developer.chrome.com/origintrials/#/view_trial/988540118207823873). +- **Испытание Origin Trial**: зарегистрируйтесь и примите участие в [испытании Chrome Origin Trial](/origintrials/#/view_trial/988540118207823873). - **GitHub**: ознакомьтесь с [текстом предложения](https://github.com/privacycg/first-party-sets) и [обсуждением, где можно задать свои вопросы](https://github.com/privacycg/first-party-sets/issues). - **Поддержка разработчиков**: задавайте вопросы и участвуйте в обсуждениях в [репозитории поддержки разработчиков Privacy Sandbox](https://github.com/GoogleChromeLabs/privacy-sandbox-dev-support). diff --git a/site/ru/docs/privacy-sandbox/overview/index.md b/site/ru/docs/privacy-sandbox/overview/index.md index d4326128daf6..98caa42f9e83 100644 --- a/site/ru/docs/privacy-sandbox/overview/index.md +++ b/site/ru/docs/privacy-sandbox/overview/index.md @@ -45,7 +45,7 @@ authors: ### Ограничение сбора данных - [**Бюджет конфиденциальности**](https://www.youtube.com/watch?v=0STgfjSA6T8): механизм, дающий сайтам возможность получать информацию об используемом браузере или устройстве, но при этом позволяющий браузеру ограничивать общий объем доступной сайту информации, чтобы не дать ему идентифицировать пользователя. -- [**User-Agent Client Hints**](https://web.dev/user-agent-client-hints/): строка [User-Agent](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/User-Agent) (UA)—одна из важных пассивных поверхностей [фингерпринтинга](https://w3c.github.io/fingerprinting-guidance/#passive) и вдобавок ее сложно анализировать. С помощью Client Hints (клиентских подсказок) разработчики могут активно запрашивать только ту информацию об устройстве или настройках пользователя, которая им необходима, вместо того чтобы извлекать эти данные из строки User-Agent. +- [**User-Agent Client Hints**](https://web.dev/user-agent-client-hints/): строка [User-Agent](https://developer.mozilla.org/docs/Web/HTTP/Headers/User-Agent) (UA)—одна из важных пассивных поверхностей [фингерпринтинга](https://w3c.github.io/fingerprinting-guidance/#passive) и вдобавок ее сложно анализировать. С помощью Client Hints (клиентских подсказок) разработчики могут активно запрашивать только ту информацию об устройстве или настройках пользователя, которая им необходима, вместо того чтобы извлекать эти данные из строки User-Agent. - [**Gnatcatcher**](https://github.com/bslassey/ip-blindness): позволяет ограничить возможность идентификации конкретных пользователей по IP-адресу. Предложение состоит из двух частей: [добровольный отказ от обработки IP-адресов](https://github.com/bslassey/ip-blindness/blob/master/willful_ip_blindness.md) позволяет сайтам сообщать браузеру, что они не идентифицируют пользователей по IP-адресу, в то время как Near-path NAT позволяет группам пользователей направлять свой трафик через один и тот же анонимизирующий сервер, фактически скрывая свои IP-адреса от владельцев сайтов. Gnatcatcher также предоставляет сайтам возможность получать доступ к IP-адресам в легитимных целях, таких как предотвращение злоупотребления, при условии прохождения сертификации и аудита. ### Идентификация diff --git a/site/ru/docs/privacy-sandbox/status/index.md b/site/ru/docs/privacy-sandbox/status/index.md index 424d8317a253..b227ff13732e 100644 --- a/site/ru/docs/privacy-sandbox/status/index.md +++ b/site/ru/docs/privacy-sandbox/status/index.md @@ -16,7 +16,7 @@ authors: *Старое название—«Измерение конверсии».* - [Текущее испытание origin trial](https://web.dev/origin-trials/): с Chrome 86 [теперь расширено](https://groups.google.com/u/1/a/chromium.org/g/attribution-reporting-api-dev/c/ZKf9T8sRqAM) до Chrome 93. -- [Регистрация для участия в испытании Origin Trial](https://developer.chrome.com/origintrials/#/view_trial/3411476717733150721). +- [Регистрация для участия в испытании Origin Trial](/origintrials/#/view_trial/3411476717733150721). - [Демонстрация](https://goo.gle/demo-event-level-conversion-measurement-api). - [Статус платформы Chrome](https://www.chromestatus.com/features/6412002824028160). - [Статус Blink](https://groups.google.com/a/chromium.org/g/blink-dev/search?q=conversion%20measurement). @@ -39,7 +39,7 @@ authors: ## Токены доверия - [Текущее испытание origin trial](https://web.dev/origin-trials/): с Chrome 84 [теперь расширено](https://groups.google.com/a/chromium.org/g/blink-dev/c/-W90wVkS0Ks/m/Jfh5-ZWpAQAJ) до Chrome 94. -- [Регистрация для участия в испытании Origin Trial](https://developer.chrome.com/origintrials/#/view_trial/2479231594867458049). +- [Регистрация для участия в испытании Origin Trial](/origintrials/#/view_trial/2479231594867458049). - [Демонстрация](https://trust-token-demo.glitch.me/). - [Статус платформы Chrome](https://www.chromestatus.com/feature/5078049450098688). - [Статус Blink](https://groups.google.com/a/chromium.org/g/blink-dev/search?q=trust%tokens). @@ -50,7 +50,7 @@ authors: ## Наборы собственных доменов - [Текущее испытание Origin Trial](https://web.dev/origin-trials/): Chrome с 89 по 93. -- [Регистрация для участия в испытании Origin Trial](https://developer.chrome.com/origintrials/#/view_trial/988540118207823873). +- [Регистрация для участия в испытании Origin Trial](/origintrials/#/view_trial/988540118207823873). - [Статус платформы Chrome](https://chromestatus.com/feature/5640066519007232). - [Статус Blink](https://groups.google.com/a/chromium.org/g/blink-dev/search?q=first-party%20sets). - [Предложение API](https://github.com/privacycg/first-party-sets): задавайте вопросы и участвуйте в обсуждении API в разделе [Issues](hhttps://github.com/privacycg/first-party-sets/issues). @@ -93,7 +93,7 @@ authors: - [Знакомство с испытаниями Chrome Origin Trial](https://web.dev/origin-trials/) - [Что такое сторонние испытания Origin Trial?](https://web.dev/third-party-origin-trials) -- [Знакомство с испытаниями Chrome Origin Trial](https://developer.chrome.com/blog/origin-trial-troubleshooting/) +- [Знакомство с испытаниями Chrome Origin Trial](/blog/origin-trial-troubleshooting/) - [Руководство по испытаниям Origin Trial для веб-разработчиков](https://github.com/GoogleChrome/OriginTrials/blob/gh-pages/developer-guide.md) - [Зачем нужны испытания Origin Trial](https://github.com/GoogleChrome/OriginTrials/blob/gh-pages/explainer.md) - [Проведение испытаний Origin Trial](https://www.chromium.org/blink/origin-trials/running-an-origin-trial) diff --git a/site/ru/docs/privacy-sandbox/trust-tokens/index.md b/site/ru/docs/privacy-sandbox/trust-tokens/index.md index 2b4c10f0711f..0cdbfe131f25 100644 --- a/site/ru/docs/privacy-sandbox/trust-tokens/index.md +++ b/site/ru/docs/privacy-sandbox/trust-tokens/index.md @@ -12,7 +12,7 @@ authors: ## Статус реализации - [Доступно в рамках испытания Origin Trial](https://web.dev/origin-trials/) в Chrome с 84 по 94. -- [Регистрация для участия в испытании](https://developer.chrome.com/origintrials/#/view_trial/2479231594867458049). +- [Регистрация для участия в испытании](/origintrials/#/view_trial/2479231594867458049). - [Демонстрация](https://trust-token-demo.glitch.me/). - [Интеграция с Chrome DevTools](https://developers.google.com/web/updates/2021/01/devtools?utm_source=devtools#trust-token). - [Статус платформы Chrome](https://www.chromestatus.com/feature/5078049450098688). @@ -40,7 +40,7 @@ authors: С помощью Trust Tokens API сайт может выдавать доверенным пользователям криптографически защищенные токены, которыми затем можно воспользоваться в другом месте. Токены безопасным образом хранятся в браузере пользователя и могут быть использованы в других контекстах для подтверждения благонадежности пользователя. Благодаря этому доверие к пользователю на одном сайте (например, в соцсети или почтовом сервисе) может быть передано на другой сайт (например, сайт издателя или интернет-магазина), не раскрывая личность пользователя и не давая возможности сопоставлять друг с другом сеансы на разных сайтах. -{% Aside 'key-term' %} [Фингерпринтинг](https://w3c.github.io/fingerprinting-guidance/#passive) позволяет сайтам идентифицировать и отслеживать отдельных пользователей, получая данные об их устройстве, операционной системе и настройках браузера (например, языковых настройках, строке [user-agent](https://developer.mozilla.org/en-US/docs/Web/API/NavigatorID/userAgent) и доступных шрифтах), а также изменениях в состоянии устройства. Это можно делать как на стороне сервера путем проверки заголовков запросов, так и на стороне клиента при помощи JavaScript. +{% Aside 'key-term' %} [Фингерпринтинг](https://w3c.github.io/fingerprinting-guidance/#passive) позволяет сайтам идентифицировать и отслеживать отдельных пользователей, получая данные об их устройстве, операционной системе и настройках браузера (например, языковых настройках, строке [user-agent](https://developer.mozilla.org/docs/Web/API/NavigatorID/userAgent) и доступных шрифтах), а также изменениях в состоянии устройства. Это можно делать как на стороне сервера путем проверки заголовков запросов, так и на стороне клиента при помощи JavaScript. Фингерпринтинг использует механизмы, о которых пользователи не знают и которые не могут контролировать. Сайты, такие как [Panopticlick](https://panopticlick.eff.org/) и [amiunique.org](https://amiunique.org/), показывают, как данные, полученные в результате фингерпринтинга, можно объединить, чтобы идентифицировать вашу личность.
{% endAside %} @@ -68,7 +68,7 @@ authors: ## Участвуйте и делитесь отзывами -- **Испытание Origin Trial**: зарегистрируйтесь и примите участие в [испытании Chrome Origin Trial](https://developer.chrome.com/origintrials/#/view_trial/2479231594867458049). +- **Испытание Origin Trial**: зарегистрируйтесь и примите участие в [испытании Chrome Origin Trial](/origintrials/#/view_trial/2479231594867458049). - **Демонстрация**: попробуйте [генерировать и использовать](https://trust-token-demo.glitch.me/) токены доверия. - **GitHub**: ознакомьтесь с [текстом предложения](https://github.com/WICG/trust-token-api) и [обсуждением, где можно задать свои вопросы](https://github.com/WICG/trust-token-api/issues). - **W3C**: обсудите сценарии использования из отрасли в группе [Improving Web Advertising Business Group](https://www.w3.org/community/web-adv/participants). diff --git a/site/zh/blog/new-in-devtools-93/index.md b/site/zh/blog/new-in-devtools-93/index.md index 2413c90142e9..4eb461af7ca9 100644 --- a/site/zh/blog/new-in-devtools-93/index.md +++ b/site/zh/blog/new-in-devtools-93/index.md @@ -55,7 +55,7 @@ Chromium 议题: [1182537](https://crbug.com/1182537) ## Attribution Reporting API 调试 {: #attribution-reporting } 现在，Attribution Reporting API 错误会显示在**问题**标签页那里。 -[Attribution Reporting](https://developer.chrome.com/docs/privacy-sandbox/attribution-reporting/)是一个新的 API，旨在帮助您在没有使用跨站标识符的情况下，评估用户行为（比如点击或者查看广告）所导致的转化率。 +[Attribution Reporting](/docs/privacy-sandbox/attribution-reporting/)是一个新的 API，旨在帮助您在没有使用跨站标识符的情况下，评估用户行为（比如点击或者查看广告）所导致的转化率。 {% Img src="image/dPDCek3EhZgLQPGtEG3y0fTn4v82/bkEGVEv5kKc9M6qBUmLz.png", alt="显示在问题标签页里的 Attribution Reporting API 错误信息", width="800", height="501" %} diff --git a/site/zh/blog/new-in-devtools-95/index.md b/site/zh/blog/new-in-devtools-95/index.md index d65115238900..4a15649970b2 100644 --- a/site/zh/blog/new-in-devtools-95/index.md +++ b/site/zh/blog/new-in-devtools-95/index.md @@ -102,8 +102,8 @@ link.access = 'admin'; link.search = `?access=${link.access}`; ``` - -试着在“控制台”中打出 `link`。自有属性现在是加粗并优先排序的。这些改动会让自定义属性更容易被发现，尤其对于有着很多继承属性的 [Web APIs](https://developer.mozilla.org/en-US/docs/Web/API)（例如 `URL`）。 + +试着在“控制台”中打出 `link`。自有属性现在是加粗并优先排序的。这些改动会让自定义属性更容易被发现，尤其对于有着很多继承属性的 [Web APIs](https://developer.mozilla.org/docs/Web/API)（例如 `URL`）。 {% Img src="image/dPDCek3EhZgLQPGtEG3y0fTn4v82/Ngjx6YRQsH3Fhl6DUZYl.png", alt="自有属性加粗并优先排序", width="800", height="561" %} diff --git a/site/zh/blog/new-in-devtools-96/index.md b/site/zh/blog/new-in-devtools-96/index.md index c912a67abf8f..76ac50d5075e 100644 --- a/site/zh/blog/new-in-devtools-96/index.md +++ b/site/zh/blog/new-in-devtools-96/index.md @@ -224,8 +224,8 @@ Chromium 议题: [1232937](https://crbug.com/1232937), [1255586](https://crbug.c ## 弃用应用程序面板里面的应用程序缓存边栏 {: #app-cache } - -由于 Chrome 以及基于 Chromium 的浏览器都已移除对 [AppCache](https://web.dev/appcache-removal/) 的支持，因此**应用**面板里面的[应用缓存](https://developer.chrome.com/docs/devtools/storage/applicationcache/)边栏现已被移除。 + +由于 Chrome 以及基于 Chromium 的浏览器都已移除对 [AppCache](https://web.dev/appcache-removal/) 的支持，因此**应用**面板里面的[应用缓存](/docs/devtools/storage/applicationcache/)边栏现已被移除。 {# https://chromium.googlesource.com/devtools/devtools-frontend/+/de4d15e955d6145674e3885cde8a5a70f1269b79 #} diff --git a/site/zh/docs/privacy-sandbox/attribution-reporting-introduction/index.md b/site/zh/docs/privacy-sandbox/attribution-reporting-introduction/index.md index 87e52f9ac094..b4ea57aca009 100644 --- a/site/zh/docs/privacy-sandbox/attribution-reporting-introduction/index.md +++ b/site/zh/docs/privacy-sandbox/attribution-reporting-introduction/index.md @@ -30,7 +30,7 @@ authors: ## 为什么需要这个 API？ -如今，广告转化测量通常依赖于[第三方 cookie](https://developer.mozilla.org/en-US/docs/Web/HTTP/Cookies#Third-party_cookies)。但是浏览器正在限制获取这些第三方 cookie，因为这些 cookie 可用于跨站跟踪用户并妨碍用户隐私。该 API 以保护隐私的方式实现这些测量，且无需第三方 cookie。 +如今，广告转化测量通常依赖于[第三方 cookie](https://developer.mozilla.org/docs/Web/HTTP/Cookies#Third-party_cookies)。但是浏览器正在限制获取这些第三方 cookie，因为这些 cookie 可用于跨站跟踪用户并妨碍用户隐私。该 API 以保护隐私的方式实现这些测量，且无需第三方 cookie。 ## 谁需要了解此 API？ @@ -71,7 +71,7 @@ authors: #### 在已部署的网站上对最终用户进行实验 -1. 通过注册[原始试验](https://developer.chrome.com/blog/origin-trials/)（如果可用）为最终用户启用 API。原始试验让您能够使用实验性功能并构建可以在有限时间内试用的功能。请注意，[第三方原始试验](https://developer.chrome.com/blog/third-party-origin-trials/)使广告服务和测量提供商等第三方行为者可以跨多个站点对 API 进行测试。**如需查看此 API 当前可用的原始试验，请前往[状态](#status)部分**。如需了解未来原始试验的相关信息，请加入[归因报告开发者邮件列表](https://groups.google.com/u/1/a/chromium.org/g/attribution-reporting-api-dev)。 +1. 通过注册[原始试验](/blog/origin-trials/)（如果可用）为最终用户启用 API。原始试验让您能够使用实验性功能并构建可以在有限时间内试用的功能。请注意，[第三方原始试验](/blog/third-party-origin-trials/)使广告服务和测量提供商等第三方行为者可以跨多个站点对 API 进行测试。**如需查看此 API 当前可用的原始试验，请前往[状态](#status)部分**。如需了解未来原始试验的相关信息，请加入[归因报告开发者邮件列表](https://groups.google.com/u/1/a/chromium.org/g/attribution-reporting-api-dev)。 2. 将 API 集成到您的网站和系统中。 @@ -138,8 +138,8 @@ authors: {% Aside %}将来不再使用第三方 cookie 时，该 API 将与其他隐私保护广告 API 相结合，从而覆盖端到端用例： -- 再营销：参见 [FLEDGE](https://developer.chrome.com/docs/privacy-sandbox/fledge/) -- 基于兴趣的广告选择：参见 [FLoC](https://developer.chrome.com/docs/privacy-sandbox/floc/) +- 再营销：参见 [FLEDGE](/docs/privacy-sandbox/fledge/) +- 基于兴趣的广告选择：参见 [FLoC](/docs/privacy-sandbox/floc/) {% endAside %} @@ -155,7 +155,7 @@ authors: - `🧪 Experiment (BROWSER_NAME)`：BROWSER_NAME 有可用的实验。Chrome 中将实验称为原始试验。 - `🚀 Stable (BROWSER_NAME)` ：BROWSER_NAME 中已默认提供该功能。 -{% Aside %} [当前原始试验](https://developer.chrome.com/origintrials/#/view_trial/3411476717733150721)（Chrome 实验 🧪）{% endAside %} +{% Aside %} [当前原始试验](/origintrials/#/view_trial/3411476717733150721)（Chrome 实验 🧪）{% endAside %} {% Aside 'caution' %}我们将运行多个原始试验（实验）。每轮运行情况将用来根据生态系统反馈对 API 进行改进和调整。{% endAside %} @@ -342,7 +342,7 @@ authors: ## 网站和用户控制 - 用户可以在用户设置`chrome://settings/privacySandbox`中选择退出。 -- 默认情况下，顶级上下文中会启用该功能。任意第三方无法在发布商不知情的情况下使用该 API，因为需要通过[许可策略](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Feature-Policy)在子 iframe 中启用归因报告 API。 +- 默认情况下，顶级上下文中会启用该功能。任意第三方无法在发布商不知情的情况下使用该 API，因为需要通过[许可策略](https://developer.mozilla.org/docs/Web/HTTP/Headers/Feature-Policy)在子 iframe 中启用归因报告 API。 ## 开放性问题 diff --git a/site/zh/docs/privacy-sandbox/attribution-reporting/index.md b/site/zh/docs/privacy-sandbox/attribution-reporting/index.md index 23c932a3115a..e624e2ee64e4 100644 --- a/site/zh/docs/privacy-sandbox/attribution-reporting/index.md +++ b/site/zh/docs/privacy-sandbox/attribution-reporting/index.md @@ -40,7 +40,7 @@ authors: ## 为什么需要这个 API？ {: #why-is-this-api-needed } -如今，广告转化测量通常依赖于[第三方 cookie](https://developer.mozilla.org/en-US/docs/Web/HTTP/Cookies#Third-party_cookies)。但是浏览器正在限制获取这些第三方 cookie，因为这些 cookie 可用于跨站跟踪用户并妨碍用户隐私。该 API 以保护隐私的方式实现这些测量，且无需第三方 cookie。 +如今，广告转化测量通常依赖于[第三方 cookie](https://developer.mozilla.org/docs/Web/HTTP/Cookies#Third-party_cookies)。但是浏览器正在限制获取这些第三方 cookie，因为这些 cookie 可用于跨站跟踪用户并妨碍用户隐私。该 API 以保护隐私的方式实现这些测量，且无需第三方 cookie。 ## 归因报告 API 的运作方式是怎样的？都有哪些功能？ @@ -57,7 +57,7 @@ authors: ## 参与并分享反馈 {: #engage } -- **原始试验**：[注册第一代原始试验（仅支持点击型转化）](https://developer.chrome.com/origintrials/#/view_trial/3411476717733150721)或[查看第一个演示（仅支持点击型转化）](https://goo.gle/demo-event-level-conversion-measurement-api)。 +- **原始试验**：[注册第一代原始试验（仅支持点击型转化）](/origintrials/#/view_trial/3411476717733150721)或[查看第一个演示（仅支持点击型转化）](https://goo.gle/demo-event-level-conversion-measurement-api)。 - 请加入[开发者邮件列表](https://groups.google.com/u/1/a/chromium.org/g/attribution-reporting-api-dev)，进而继续关注该 API 的下一次实现，该实现将提供更多功能并将在 Chrome 中投入实验（原始试验）。 - **GitHub**：阅读[提案](https://github.com/WICG/conversion-measurement-api/)、[提出问题并关注讨论](https://github.com/WICG/conversion-measurement-api/issues)。 - **W3C**：在[改善网络广告业务组](https://www.w3.org/community/web-adv/participants)中讨论行业用例，也可以加入[隐私社区组](https://www.w3.org/community/privacycg/)，参与围绕 WebKit/Safari API 的讨论。 diff --git a/site/zh/docs/privacy-sandbox/first-party-sets/index.md b/site/zh/docs/privacy-sandbox/first-party-sets/index.md index 2fed56c08e10..01f733de0b79 100644 --- a/site/zh/docs/privacy-sandbox/first-party-sets/index.md +++ b/site/zh/docs/privacy-sandbox/first-party-sets/index.md @@ -14,7 +14,7 @@ authors: ## 实现状态 - [源站试用](https://web.dev/origin-trials/)：Chrome 89 到 93。 -- [注册源站试用](https://developer.chrome.com/origintrials/#/view_trial/988540118207823873)。 +- [注册源站试用](/origintrials/#/view_trial/988540118207823873)。 - [Chrome 平台状态](https://chromestatus.com/feature/5640066519007232)。 - [Chromium 项目](https://www.chromium.org/updates/first-party-sets)。 @@ -69,7 +69,7 @@ authors: ## 参与和分享反馈 -- **源站试用**：注册并加入 [Chrome 源站试用](https://developer.chrome.com/origintrials/#/view_trial/988540118207823873)。 +- **源站试用**：注册并加入 [Chrome 源站试用](/origintrials/#/view_trial/988540118207823873)。 - **GitHub**：阅读[提案](https://github.com/privacycg/first-party-sets)、[提出问题并关注讨论](https://github.com/privacycg/first-party-sets/issues)。 - **开发者支持**：在 [Privacy Sandbox Developer Support 仓库](https://github.com/GoogleChromeLabs/privacy-sandbox-dev-support)中提出问题并加入讨论。 diff --git a/site/zh/docs/privacy-sandbox/overview/index.md b/site/zh/docs/privacy-sandbox/overview/index.md index f21e7f520a69..752c7101c7d6 100644 --- a/site/zh/docs/privacy-sandbox/overview/index.md +++ b/site/zh/docs/privacy-sandbox/overview/index.md @@ -45,7 +45,7 @@ Chrome 团队开发的主要提案如下。 ### 限制数据收集 - [**隐私预算**](https://www.youtube.com/watch?v=0STgfjSA6T8)：允许网站获取有关用户浏览器或设备的信息，但浏览器可以对网站可访问的信息总量设置配额，从而无法识别用户身份。 -- [**用户代理客户端提示**](https://web.dev/user-agent-client-hints/)：[用户代理](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/User-Agent) (UA) 字符串是一个重要的被动["指纹"收集](https://w3c.github.io/fingerprinting-guidance/#passive)图面，并且难以处理。客户端提示使开发者能够主动请求其确切需要的用户设备或条件相关信息，而不需要从用户代理字符串中解析这些数据。 +- [**用户代理客户端提示**](https://web.dev/user-agent-client-hints/)：[用户代理](https://developer.mozilla.org/docs/Web/HTTP/Headers/User-Agent) (UA) 字符串是一个重要的被动["指纹"收集](https://w3c.github.io/fingerprinting-guidance/#passive)图面，并且难以处理。客户端提示使开发者能够主动请求其确切需要的用户设备或条件相关信息，而不需要从用户代理字符串中解析这些数据。 - [**Gnatcatcher**](https://github.com/bslassey/ip-blindness)：限制通过访问个人用户 IP 地址来识别个人用户身份的能力。提案包含两部分：[Willful IP Blindness](https://github.com/bslassey/ip-blindness/blob/master/willful_ip_blindness.md) 为网站提供了一种使浏览器知晓其并未将 IP 地址与用户相联系的方式；以及 [**Near-path NAT**](https://github.com/bslassey/ip-blindness/blob/master/near_path_nat.md) 允许用户组通过同一个私有化服务器发送其流量，从而有效地对网站主机隐藏其 IP 地址。Gnatcatcher 还可确保需要出于合法目的（例如防止滥用）而访问 IP 地址的网站可以在获得认证和审核的情况下予以访问。 ### 身份 diff --git a/site/zh/docs/privacy-sandbox/status/index.md b/site/zh/docs/privacy-sandbox/status/index.md index 94b3fed2ebc6..8a519ab9e786 100644 --- a/site/zh/docs/privacy-sandbox/status/index.md +++ b/site/zh/docs/privacy-sandbox/status/index.md @@ -16,7 +16,7 @@ authors: *以前称为转化衡量。* - [当前源站试用](https://web.dev/origin-trials/)：现已从 Chrome 86 [扩展](https://groups.google.com/u/1/a/chromium.org/g/attribution-reporting-api-dev/c/ZKf9T8sRqAM)到 Chrome 93。 -- [注册源站试用](https://developer.chrome.com/origintrials/#/view_trial/3411476717733150721)。 +- [注册源站试用](/origintrials/#/view_trial/3411476717733150721)。 - [演示](https://goo.gle/demo-event-level-conversion-measurement-api)。 - [Chrome 平台状态](https://www.chromestatus.com/features/6412002824028160)。 - [Blink 状态](https://groups.google.com/a/chromium.org/g/blink-dev/search?q=conversion%20measurement)。 @@ -39,7 +39,7 @@ authors: ## 信任令牌 - [当前源站试用](https://web.dev/origin-trials/)：现已从 Chrome 84 [扩展](https://groups.google.com/a/chromium.org/g/blink-dev/c/-W90wVkS0Ks/m/Jfh5-ZWpAQAJ)到 Chrome 94。 -- [注册源站试用](https://developer.chrome.com/origintrials/#/view_trial/2479231594867458049)。 +- [注册源站试用](/origintrials/#/view_trial/2479231594867458049)。 - [演示](https://trust-token-demo.glitch.me/)。 - [Chrome 平台状态](https://www.chromestatus.com/feature/5078049450098688)。 - [Blink 状态](https://groups.google.com/a/chromium.org/g/blink-dev/search?q=trust%tokens)。 @@ -50,7 +50,7 @@ authors: ## 第一方集 - [当前源站试用](https://web.dev/origin-trials/)：Chrome 89 到 93。 -- [注册源站试用](https://developer.chrome.com/origintrials/#/view_trial/988540118207823873)。 +- [注册源站试用](/origintrials/#/view_trial/988540118207823873)。 - [Chrome 平台状态](https://chromestatus.com/feature/5640066519007232)。 - [Blink 状态](https://groups.google.com/a/chromium.org/g/blink-dev/search?q=first-party%20sets)。 - [API 提案](https://github.com/privacycg/first-party-sets)：有关 API 问题和讨论，请参阅[议题](hhttps://github.com/privacycg/first-party-sets/issues)。 diff --git a/site/zh/docs/privacy-sandbox/trust-tokens/index.md b/site/zh/docs/privacy-sandbox/trust-tokens/index.md index d6eda9ea842c..6cecdd675de8 100644 --- a/site/zh/docs/privacy-sandbox/trust-tokens/index.md +++ b/site/zh/docs/privacy-sandbox/trust-tokens/index.md @@ -12,7 +12,7 @@ authors: ## 实现状态 - [源站试用](https://web.dev/origin-trials/)：Chrome 84 到 94。 -- [注册试用](https://developer.chrome.com/origintrials/#/view_trial/2479231594867458049)。 +- [注册试用](/origintrials/#/view_trial/2479231594867458049)。 - [演示](https://trust-token-demo.glitch.me/)。 - [Chrome DevTools 集成](https://developers.google.com/web/updates/2021/01/devtools?utm_source=devtools#trust-token)。 - [Chrome 平台状态](https://www.chromestatus.com/feature/5078049450098688)。 @@ -40,7 +40,7 @@ authors: 借助 Trust Tokens API，网站可以向其信任的用户颁发加密令牌，随后可在其他位置使用。令牌由用户的浏览器安全地存储，然后可以在其他上下文中赎回以确认用户的真实性。这样即可将一个网站（例如社交媒体网站或电子邮件服务）的用户信任信息传达到另一个网站（例如发布商或在线商店），而无需识别用户身份或跨网站链接身份。 -{% Aside 'key-term' %} ["指纹"收集](https://w3c.github.io/fingerprinting-guidance/#passive)使网站能够通过获取有关其设备、操作系统和浏览器设置（例如语言偏好设置、 [用户代理](https://developer.mozilla.org/en-US/docs/Web/API/NavigatorID/userAgent)和可用字体）或设备状态变更的数据来识别和跟踪个别用户。这可以通过检查请求标头在服务器上完成，也可以使用 JavaScript 在客户端上完成。 +{% Aside 'key-term' %} ["指纹"收集](https://w3c.github.io/fingerprinting-guidance/#passive)使网站能够通过获取有关其设备、操作系统和浏览器设置（例如语言偏好设置、 [用户代理](https://developer.mozilla.org/docs/Web/API/NavigatorID/userAgent)和可用字体）或设备状态变更的数据来识别和跟踪个别用户。这可以通过检查请求标头在服务器上完成，也可以使用 JavaScript 在客户端上完成。 "指纹"收集使用用户不会意识到且无法控制的机制。[Panopticlick](https://panopticlick.eff.org/) 和 [amiunique.org](https://amiunique.org/) 等网站展示了如何结合"指纹"数据来识别您的个人身份。{% endAside %} @@ -68,7 +68,7 @@ authors: ## 参与并分享反馈 -- **源站试用**：注册并参加 [Chrome 源站试用](https://developer.chrome.com/origintrials/#/view_trial/2479231594867458049)。 +- **源站试用**：注册并参加 [Chrome 源站试用](/origintrials/#/view_trial/2479231594867458049)。 - **演示**：尝试信任令牌的[颁发和赎回](https://trust-token-demo.glitch.me/)。 - **GitHub**：阅读[提案](https://github.com/WICG/trust-token-api)、[提出问题并关注讨论](https://github.com/WICG/trust-token-api/issues)。 - **W3C**：在 [Improving Web Advertising Business Group](https://www.w3.org/community/web-adv/participants) 中讨论行业用例。 diff --git a/tools/linting/bad-urls.js b/tools/linting/bad-urls.js new file mode 100644 index 000000000000..c571a5aa18f6 --- /dev/null +++ b/tools/linting/bad-urls.js @@ -0,0 +1,83 @@ +/* + * Copyright 2020 Google LLC + * + * Licensed under the Apache License, Version 2.0 (the "License"); + * you may not use this file except in compliance with the License. + * You may obtain a copy of the License at + * + * https://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an "AS IS" BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + * See the License for the specific language governing permissions and + * limitations under the License. + */ + +const rule = require('unified-lint-rule'); +const {URL} = require('url'); +const visit = require('unist-util-visit'); +const siteData = require('../../site/_data/site.json'); +const excludedFromLinkChecks = [ + 'CODE_OF_CONDUCT.md', + 'CONTRIBUTING.md', + 'README.md', +]; + +module.exports = rule('remark-lint:bad-urls', checkURL); + +// Based on this Stack Overflow answer: https://bit.ly/3ELKYq3 +const locale = /^\/[a-z]{2,3}-[a-z0-9]{2,4}(-[a-z]{2})?/i; + +/** + * Walk the AST for the markdown file and find any bad URLs. + * @param {*} tree An AST of the markdown file. + * @param {*} file The markdown file. + */ +function checkURL(tree, file) { + visit(tree, 'link', visitor); + + /* eslint-disable require-jsdoc */ + function visitor(node) { + const [markdownFile] = file.history; + const nodeUrl = node.url; + if (!nodeUrl) { + return; + } + const parsed = new URL(nodeUrl, siteData.url); + + // If URL hostname is "wiki.developer.mozilla.org", warn to change to + // "developer.mozilla.org". + if (parsed.hostname === 'wiki.developer.mozilla.org') { + const reason = 'Change URL hostname to "developer.mozilla.org".'; + file.message(reason, node); + } + + // If a URL starts with developer.chrome.com, yell about it, since those + // links must be relative, not absolute. We also must use nodeUrl instead + // of the parsed URL object since the latter throws for relative links. + if ( + nodeUrl.startsWith('https://developer.chrome.com') && + !excludedFromLinkChecks.includes(markdownFile) + ) { + const relative = parsed.pathname + parsed.hash; + const absolute = parsed.href; + const reason = `Internal links must be relative. Use ${relative} instead of ${absolute}.`; + file.message(reason, node); + } + + // If the URL is to MDN and contains localization info (e.g., en-US), warn + // to remove the localization part of the URL. + if ( + parsed.hostname === 'developer.mozilla.org' && + locale.test(parsed.pathname) === true + ) { + // Not happy about this, but the types linter kept barfing on error TS2488 + // (which is not what the web.dev site does) - jlwagner + const [matchedLocale] = parsed.pathname.match(locale) || ['en-US']; + const reason = `An MDN link contains a locale (${matchedLocale}). Please remove the locale from the link.`; + + file.message(reason, node); + } + } +}