Understanding WebView Rendering Pipeline

443 views
Skip to first unread message

Rahul Patel

unread,
Aug 12, 2024, 2:26:35 PM8/12/24
to android-webview-dev
Hello,
I have been trying to understand  WebView rendering pipeline, and how its implemented and its design choice. 

Chromium Primarily provides onScreen ( rendering directly into visible surface) and off-screen (rendering into an intermediate buffer) based rendering, and looking at the latest version of WebView/Chromium it looks like WebView currently doing off-screen based rendering using FBO,  do we have any doc for this design choice? specially benefits of using FBO over surface-less

Any inputs will be help!


Thanks,
 RP

Nate Fischer

unread,
Aug 12, 2024, 5:13:53 PM8/12/24
to Rahul Patel, android-webview-dev, bo...@chromium.org, vas...@chromium.org
I'm not sure about the exact design choice here, but maybe Bo or Vasiliy will know.

Nate Fischer | Software Engineer | ntf...@google.com



--
You received this message because you are subscribed to the Google Groups "android-webview-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-webview...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/android-webview-dev/2dd58d6c-41b1-4dd0-aea2-d7be67c8a171n%40chromium.org.

Bo Liu

unread,
Aug 14, 2024, 12:46:23 PM8/14/24
to Nate Fischer, Rahul Patel, android-webview-dev, vas...@chromium.org
Webview doesn't own the surface it renders to, and it's libhwui that directs where webview renders to. *Most of the time* it should be the visible surface and that FBO function should return 0.
Reply all
Reply to author
Forward
0 new messages