From bdd31d10f5bd8f99b2baf1ac315b5343dde5209b Mon Sep 17 00:00:00 2001 From: "Brian R. Bondy" Date: Wed, 25 Mar 2026 15:14:04 -0400 Subject: [PATCH] Fix stale wiki link in patching docs (#35000) The wiki content was moved into the docs folder, so the external link to brave-browser/wiki/Patching-Chromium#making-methods-virtual now just redirects. Use a local anchor instead. --- docs/patching_and_chromium_src.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/patching_and_chromium_src.md b/docs/patching_and_chromium_src.md index 9dd726fc8f3..cc7fd62bf85 100644 --- a/docs/patching_and_chromium_src.md +++ b/docs/patching_and_chromium_src.md @@ -23,7 +23,7 @@ To change an upstream logic it's often best to simply subclass a Chromium class, You will need to patch (see the below documentation) for some small trivial things in this case: - Create instances of your class instead of the Chromium class. - Possibly add a `friend` member to the base class you're subclassing. -- Possibly add a `virtual` keyword to functions you'd like to subclass - [example](https://github.com/brave/brave-browser/wiki/Patching-Chromium#making-methods-virtual) +- Possibly add a `virtual` keyword to functions you'd like to subclass - [example](#making-methods-virtual) Header patches should use preprocessor defines when possible. The define should always be the last thing in `public` so you can change to `protected` or `private` inside the define. ```