Fix typos in design principles.
Replaces WebContents::SupportsUserData which doesn't exist with WebContentsUserData
Change-Id: I976827c379f81554fc990afaa7cd12f19b2ddba3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5823230
Reviewed-by: Scott Violet <[email protected]>
Commit-Queue: Erik Chen <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1348370}
diff --git a/docs/chrome_browser_design_principles.md b/docs/chrome_browser_design_principles.md
index c3794475..16c42b89 100644
--- a/docs/chrome_browser_design_principles.md
+++ b/docs/chrome_browser_design_principles.md
@@ -96,7 +96,7 @@
* This class should own all tab-centric features. e.g. print preview,
lens overlay, compose, find-in-page, etc.
* If the feature requires instantiation of
- `WebContents::SupportsUserData`, it should be done in this class.
+ `content::WebContentsUserData`, it should be done in this class.
* For desktop chrome, `TabHelpers::AttachTabHelpers` will become a
remove-only method. Clank/WebView may continue to use section 2 of
`TabHelpers::AttachTabHelpers` (Clank/WebView only).
@@ -106,7 +106,7 @@
* We defer to //components/OWNERS for expertise and feedback on the
architecture of these features, and encourage feature-owners to
proactively reach out to them.
- * Lazy instantiation of `WebContents::SupportsUserData` is an
+ * Lazy instantiation of `content::WebContentsUserData` is an
anti-pattern.
* `BrowserWindowFeatures` (member of `Browser`)
* example: omnibox, security chip, bookmarks bar, side panel
