From 9a4f845f721071e68644a80d22dd0e209ad93e62 Mon Sep 17 00:00:00 2001 From: Erick Zhao Date: Mon, 2 Dec 2024 20:12:02 -0800 Subject: [PATCH] Update blog/migrate-to-webcontentsview.md Co-authored-by: Charles Kerr --- blog/migrate-to-webcontentsview.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/blog/migrate-to-webcontentsview.md b/blog/migrate-to-webcontentsview.md index 9fdb24dc8..0abdc47fb 100644 --- a/blog/migrate-to-webcontentsview.md +++ b/blog/migrate-to-webcontentsview.md @@ -42,8 +42,7 @@ For the most part, each instance where your app instantiates new BrowserViews ca :::info By default, `WebContentsView` instantiates with a white background, while `BrowserView` instantiates with a transparent background. - If you used to use the default transparent background setting with your `BrowserView` instances, you will need to set the - background colour manually with a RGBA hex value with the alpha (opaqueness) channel set to `00`. + To get a transparent background in `WebContentsView`, set its background color to an RGBA hex value with an alpha (opaqueness) channel set to `00`: ```diff + this.webContentsView.setBackgroundColor("#00000000");