use relative links instead of https://www.chromium.org/ [website : main]

181 views
Skip to first unread message

Mike Frysinger (Gerrit)

unread,
Dec 19, 2024, 11:27:34 AM12/19/24
to blink-api-ow...@chromium.org

Mike Frysinger has uploaded the change for review

Commit message

use relative links instead of https://www.chromium.org/

This improves sandbox website navigation by not constantly bouncing
us back to the production site.
Change-Id: I90c4a987db5e32d2e8b3d9a2a430d2bc3c4f1962

Change diff


Change information

Files:
  • M site/Home/chromium-privacy/privacy-sandbox/third-party-cookie-phaseout/index.md
  • M site/Home/chromium-security/brag-sheet/index.md
  • M site/Home/chromium-security/bugs/index.md
  • M site/Home/chromium-security/education/security-tips-for-ipc/index.md
  • M site/Home/chromium-security/enamel/goals-for-the-origin-info-bubble/index.md
  • M site/Home/chromium-security/marking-http-as-non-secure/index.md
  • M site/Home/chromium-security/quarterly-updates/index.md
  • M site/Home/chromium-security/reviews-and-consulting/index.md
  • M site/Home/chromium-security/root-ca-policy/apply-for-inclusion/index.md
  • M site/Home/chromium-security/root-ca-policy/index.md
  • M site/Home/chromium-security/root-ca-policy/moving-forward-together/index.md
  • M site/Home/chromium-security/security-reviews/index.md
  • M site/Home/chromium-security/ssca/index.md
  • M site/administrators/configuring-policy-for-extensions/index.md
  • M site/blink/developer-faq/index.md
  • M site/blink/index.md
  • M site/blink/launching-features/index.md
  • M site/blink/origin-trials/running-an-origin-trial/index.md
  • M site/blink/webcrypto/index.md
  • M site/blink/webidl/index.md
  • M site/chromium-os/build/bypassing-tests-on-a-per-project-basis/index.md
  • M site/chromium-os/build/tour-of-the-chromiumos-buildbot/index.md
  • M site/chromium-os/chromiumos-design-docs/boot-design/index.md
  • M site/chromium-os/chromiumos-design-docs/developer-mode/index.md
  • M site/chromium-os/chromiumos-design-docs/lucid-sleep/index.md
  • M site/chromium-os/chromiumos-design-docs/recovery-mode/index.md
  • M site/chromium-os/chromiumos-design-docs/verified-boot-crypto/index.md
  • M site/chromium-os/developer-library/getting-started/setup-chromebook/index.md
  • M site/chromium-os/developer-library/glossary/index.md
  • M site/chromium-os/developer-library/guides/code-review/code-reviews-and-submitting-code/index.md
  • M site/chromium-os/developer-library/guides/containers/cros-vm/index.md
  • M site/chromium-os/developer-library/guides/containers/crostini-developer-guide/index.md
  • M site/chromium-os/developer-library/guides/debugging/debug-buttons/index.md
  • M site/chromium-os/developer-library/guides/debugging/debugging-features/index.md
  • M site/chromium-os/developer-library/guides/debugging/debugging/index.md
  • M site/chromium-os/developer-library/guides/development/chrome-commit-pipeline/index.md
  • M site/chromium-os/developer-library/guides/development/contributing/index.md
  • M site/chromium-os/developer-library/guides/development/developer-guide/index.md
  • M site/chromium-os/developer-library/guides/development/development-basics/index.md
  • M site/chromium-os/developer-library/guides/development/sandboxing/index.md
  • M site/chromium-os/developer-library/guides/development/simple-chrome-workflow/index.md
  • M site/chromium-os/developer-library/guides/device/crosfleet/index.md
  • M site/chromium-os/developer-library/guides/device/developer-mode/index.md
  • M site/chromium-os/developer-library/guides/device/flashing-chromiumos/index.md
  • M site/chromium-os/developer-library/guides/enterprise/enterprise-policy/index.md
  • M site/chromium-os/developer-library/guides/firmware/pd-firmware-update/index.md
  • M site/chromium-os/developer-library/guides/hardware-schematics/chamelium/index.md
  • M site/chromium-os/developer-library/guides/hardware-schematics/twinkie/index.md
  • M site/chromium-os/developer-library/guides/ipc/dbus-in-chrome/index.md
  • M site/chromium-os/developer-library/guides/kernel/kernel-development/index.md
  • M site/chromium-os/developer-library/guides/kernel/using-an-upstream-kernel-on-snow/index.md
  • M site/chromium-os/developer-library/guides/localization/creating-and-translating-strings/index.md
  • M site/chromium-os/developer-library/guides/portage/package-upgrade-process/index.md
  • M site/chromium-os/developer-library/guides/rust/rust-on-cros/index.md
  • M site/chromium-os/developer-library/guides/testing/autotest-developer-faq/index.md
  • M site/chromium-os/developer-library/guides/testing/cpp-writing-tests/index.md
  • M site/chromium-os/developer-library/guides/testing/firmware-test-manual/index.md
  • M site/chromium-os/developer-library/guides/testing/igt/index.md
  • M site/chromium-os/developer-library/guides/testing/power-testing/index.md
  • M site/chromium-os/developer-library/guides/testing/running-smoke-suite-on-a-vm-image/index.md
  • M site/chromium-os/developer-library/guides/testing/unit-tests/index.md
  • M site/chromium-os/developer-library/guides/third-party/coreboot/coreboot-upstream/index.md
  • M site/chromium-os/developer-library/guides/third-party/coreboot/index.md
  • M site/chromium-os/developer-library/reference/development/chromium-os-faq/index.md
  • M site/chromium-os/developer-library/reference/development/developer-information-for-chrome-os-devices/cr-48-chrome-notebook-developer-information/how-to-boot-ubuntu-on-a-cr-48/index.md
  • M site/chromium-os/developer-library/reference/development/developer-information-for-chrome-os-devices/dell-chromebook-11/index.md
  • M site/chromium-os/developer-library/reference/development/developer-information-for-chrome-os-devices/index.md
  • M site/chromium-os/developer-library/reference/development/developer-information-for-chrome-os-devices/samsung-chromebook-2/index.md
  • M site/chromium-os/developer-library/reference/release/releases/index.md
  • M site/chromium-os/developer-library/reference/release/understanding-chromeos-releases/index.md
  • M site/chromium-os/developer-library/reference/security/hardening-prioritizing-guidelines/index.md
  • M site/chromium-os/developer-library/reference/security/selinux/index.md
  • M site/chromium-os/developer-library/reference/security/write-protection/index.md
  • M site/chromium-os/developer-library/reference/user-sessions/user-sessions/index.md
  • M site/chromium-os/developer-library/training/codelabs/autotest-client-tests/index.md
  • M site/chromium-os/developer-library/training/codelabs/server-side-test/index.md
  • M site/chromium-os/gentoo-package-upgrade-process/index.md
  • M site/chromium-os/getting-started-with-platform2/index.md
  • M site/chromium-os/glitch-vulnerability-status/index.md
  • M site/chromium-os/meltdown-spectre-vulnerability-status/index.md
  • M site/chromium-os/obsolete/quiche-notes/index.md
  • M site/chromium-os/packages/crash-reporting/debugging-a-minidump/index.md
  • M site/chromium-os/packages/crash-reporting/faq/index.md
  • M site/chromium-os/packages/libchrome/index.md
  • M site/chromium-os/platform/index.md
  • M site/chromium-os/quick-start-guide/index.md
  • M site/chromium-os/user-experience/form-factors/tablet/index.md
  • M site/developers/deep-memory-profiler/index.md
  • M site/developers/design-documents/chromium-graphics/how-to-get-gpu-rasterization/index.md
  • M site/developers/design-documents/chromium-graphics/index.md
  • M site/developers/design-documents/cookbook/index.md
  • M site/developers/design-documents/extensions/how-the-extension-system-works/docs/how-docs-are-served/index.md
  • M site/developers/design-documents/extensions/proposed-changes/apis-under-development/desktop-notification-api/index.md
  • M site/developers/design-documents/extensions/proposed-changes/apis-under-development/font-settings/index.md
  • M site/developers/design-documents/gpu-accelerated-compositing-in-chrome/gpu-architecture-roadmap/index.md
  • M site/developers/design-documents/gpu-accelerated-compositing-in-chrome/index.md
  • M site/developers/design-documents/http-authentication/writing-a-spnego-authenticator-for-chrome-on-android/index.md
  • M site/developers/design-documents/idealized-mediastream-design/index.md
  • M site/developers/design-documents/idl-build/index.md
  • M site/developers/design-documents/index.md
  • M site/developers/design-documents/layered-components-technical-approach/index.md
  • M site/developers/design-documents/making-chrome-independent-of-extensions/index.md
  • M site/developers/design-documents/network-stack/network-bug-triage/downloads-bug-triage/index.md
  • M site/developers/design-documents/network-stack/network-stack-objectives/index.md
  • M site/developers/design-documents/oop-iframes/index.md
  • M site/developers/design-documents/oop-iframes/oop-iframes-rendering/index.md
  • M site/developers/design-documents/profile-architecture/index.md
  • M site/developers/design-documents/sync/model-api/index.md
  • M site/developers/design-documents/sync/old-sync-clients-data-override-protection/index.md
  • M site/developers/gerrit-guide/index.md
  • M site/developers/how-tos/build-instructions-chromeos/index.md
  • M site/developers/how-tos/depottools/presubmit-scripts/index.md
  • M site/developers/how-tos/get-the-code-v2/index.md
  • M site/developers/how-tos/get-the-code/multiple-working-directories/index.md
  • M site/developers/how-tos/getting-around-the-chrome-source-code/index.md
  • M site/developers/how-tos/gpu-overdraw-debugging-tool/index.md
  • M site/developers/how-tos/index.md
  • M site/developers/how-tos/trace-event-profiling-tool/index.md
  • M site/developers/how-tos/trace-event-profiling-tool/trace-event-reading/index.md
  • M site/developers/how-tos/trace-event-profiling-tool/using-frameviewer/index.md
  • M site/developers/lock-and-condition-variable/index.md
  • M site/developers/memory-bloat/index.md
  • M site/developers/npapi-deprecation/index.md
  • M site/developers/profiling-chromium-and-webkit/index.md
  • M site/developers/rendering-performance-case-study-1/index.md
  • M site/developers/speed-hall-of-fame/index.md
  • M site/developers/telemetry/profiling/index.md
  • M site/developers/testing/adding-performance-tests/index.md
  • M site/developers/testing/browser-tests/index.md
  • M site/developers/tools-we-use-in-chromium/grit/grit-regression-test-plan/index.md
  • M site/developers/tools-we-use-in-chromium/grit/index.md
  • M site/developers/web-idl-interfaces/index.md
  • M site/developers/web-platform-status/index.md
  • M site/developers/webview-changes/index.md
  • M site/nativeclient/day-to-day/codereview/index.md
  • M site/nativeclient/getting-started/getting-started-background-and-basics/index.md
  • M site/nativeclient/how-tos/how-to-write-assembler-for-x86-nacl-platform/index.md
  • M site/nativeclient/pnacl/aligned-bundling-support-in-llvm/index.md
  • M site/nativeclient/pnacl/developing-pnacl/index.md
  • M site/teams/input-dev/index.md
  • M site/teams/layout-team/meeting-notes/tuesday-march-15-2016/index.md
  • M site/updates/same-site/index.md
  • M site/updates/ua-reduction/index.md
Change size: L
Delta: 143 files changed, 338 insertions(+), 379 deletions(-)
Open in Gerrit

Related details

Attention set is empty
Submit Requirements:
  • requirement is not satisfiedCode-Review
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. DiffyGerrit
Gerrit-MessageType: newchange
Gerrit-Project: website
Gerrit-Branch: main
Gerrit-Change-Id: I90c4a987db5e32d2e8b3d9a2a430d2bc3c4f1962
Gerrit-Change-Number: 6109482
Gerrit-PatchSet: 1
Gerrit-Owner: Mike Frysinger <vap...@chromium.org>
unsatisfied_requirement
open
diffy

chromium-website-scoped@luci-project-accounts.iam.gserviceaccount.com (Gerrit)

unread,
Dec 19, 2024, 10:03:15 PM12/19/24
to Dirk Pranke, chromium-websi...@chops-service-accounts.iam.gserviceaccount.com

chromium-we...@luci-project-accounts.iam.gserviceaccount.com submitted the change with unreviewed changes

Unreviewed changes

2 is the latest approved patch-set.
The change was submitted with unreviewed changes in the following files:

```
The name of the file: site/chromium-os/packages/crash-reporting/debugging-a-minidump/index.md
Insertions: 3, Deletions: 3.

@@ -141,17 +141,17 @@
## ==If backtrace in gdb did not help==

Sometimes, the gdb backtrace command ([Use gdb to show a
-backtrace](/chromium-os/how-tos-and-troubleshooting/crash-reporting/debugging-a-minidump#TOC-Use-gdb-to-show-a-backtrace))
+backtrace](#use-gdb-to-show-a-backtrace))
doesn't show a stack trace any better than that of minidump_stackwalk ([Use
minidump_stackwalk to show a stack
-trace](/chromium-os/how-tos-and-troubleshooting/crash-reporting/debugging-a-minidump#TOC-Use-minidump_stackwalk-to-show-a-stack-trace)).
+trace](#use-minidump_stackwalk-to-show-a-stack-trace)).
If you think there's more to it than what those two are showing you, try this
method to naively dump all the known symbol addresses seen on the stack. You'll
see some false positives, but you may just find the name of a function that
seems like a plausible place to look.

First, start from the above step of [using gdb to show a
-backtrace](/chromium-os/how-tos-and-troubleshooting/crash-reporting/debugging-a-minidump#TOC-Use-gdb-to-show-a-backtrace).
+backtrace](#use-gdb-to-show-a-backtrace).
We can reuse the gdb command file that was generated for it. Googlers: If you
didn't use my generate_gdb_command_file script, you can manually create the gdb
command file containing any "add-symbol-file" commands you ran.
```
```
The name of the file: site/chromium-os/packages/crash-reporting/faq/index.md
Insertions: 1, Deletions: 1.

@@ -31,7 +31,7 @@
checkout with `sudo emerge google-breakpad`.

Once you have `minidump-2-core`, you can look at section [Use gdb to show a
-backtrace](/chromium-os/how-tos-and-troubleshooting/crash-reporting/debugging-a-minidump#TOC-Use-gdb-to-show-a-backtrace)
+backtrace](/chromium-os/packages/crash-reporting/debugging-a-minidump/#use-gdb-to-show-a-backtrace)
of the [Debugging a Minidump
File](/chromium-os/packages/crash-reporting/debugging-a-minidump) guide. This is
my collection of instructions for how I've made use of `gdb` given a minidump
```

Change information

Commit message:
use relative links instead of https://www.chromium.org/

This improves sandbox website navigation by not constantly bouncing
us back to the production site.

I rewrote updates/same-site/ a bit more to use auto-TOC since the
all the links in the manually curated TOC were broken.
Change-Id: I90c4a987db5e32d2e8b3d9a2a430d2bc3c4f1962
Reviewed-by: Dirk Pranke <dpr...@google.com>
Commit-Queue: Mike Frysinger <vap...@chromium.org>
Branch: refs/heads/main
Submit Requirements:
  • requirement satisfiedCode-Review: +1 by Dirk Pranke
Open in Gerrit
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. DiffyGerrit
Gerrit-MessageType: merged
Gerrit-Project: website
Gerrit-Branch: main
Gerrit-Change-Id: I90c4a987db5e32d2e8b3d9a2a430d2bc3c4f1962
Gerrit-Change-Number: 6109482
open
diffy
satisfied_requirement
Reply all
Reply to author
Forward
0 new messages