Bug 235626 - [WPE][GTK] Feature Request: WebGL2 Support
Summary: [WPE][GTK] Feature Request: WebGL2 Support
Status: RESOLVED DUPLICATE of bug 166536
Alias: None
Product: WebKit
Classification: Unclassified
Component: ANGLE (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-01-25 20:29 PST by Saijin_Naib
Modified: 2022-06-12 14:00 PDT (History)
6 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Saijin_Naib 2022-01-25 20:29:41 PST
It'd be wonderful if Epiphany (and other Webkit-GTK based projects) could support WebGL2 as it would open the usage of them up to many different use-cases.
WebGL1 support seems to be solid, but in my case, I must use WebGL2 to be able to render PoTree data, for instance.
Comment 1 Michael Catanzaro 2022-01-26 06:22:10 PST
That is currently conditional on USE_ANGLE_WEBGL, which we set to OFF.

Tangent follows:

ANGLE is an unwanted dependency and we should prefer to delete it, rather than depend further on it. An ideal future: WebKit would not use any ANGLE internals, ANGLE would install a shared library with proper library versioning and API/ABI stability for whatever symbols that WebKit needs, and we would either delete it from Source/ThirdParty or at least exclude it from our tarball releases. But sadly, there are no signs that ANGLE developers intend to work on fixing any of that. In the meantime... here we are.

Assuming that we wanted to, I don't know what it would take to turn on USE_ANGLE_WEBGL.
Comment 2 Saijin_Naib 2022-01-26 07:54:59 PST
Michael, thank you for the additional context. Good to understand that this isn't a small lift or even something that can be done near-term. Unfortunately, this means that Epiphany is not fit for purpose for me, but I'll keep monitoring into the future as I like it overall.
Comment 3 Adrian Perez 2022-06-12 14:00:47 PDT
We have an older bug about this, so let's mark this as duplicate
and keep further discussion in #166536 :)

*** This bug has been marked as a duplicate of bug 166536 ***