Hey, sorry for the slow reply.
Could you file a bug at crbug.com about this and link it to me? It will be
easier to continue specific discussions there. Looks like WARP fallback is
working but WebGL is blocklisted for some other reason when it shouldn't be.
Geoff
On Thu, Sep 4, 2025 at 2:02 AM F
Hey,
Chrome can roll out features with server-side configurations to do A/B
comparisons or fix breakages without re-releasing, that's what's happening
here. Starting in 139, some users are opted into the deprecation. More will
be opted in over time until 100%.
We're considering unblocking llvmpip
It is the expected behaviour. The rollout is happening slowly within the
139 release.
There are no plans for a default software fallback on Linux right now but
we're thinking about the issue. I think it's unlikely that Chrome can ship
with its own packaged lavapipe but I want to make sure it's use
The experiment is currently rolled out to 1% of users.
Geoff
On Fri, Aug 22, 2025 at 4:40 PM Fred Potter wrote:
> Thanks, Geoff. Those args do help me test the WARP path, and it seems to
> be working great. And, glad to hear SwiftShader is always replaced with
> WARP, and there's no case wher
I'm not sure exactly how to read this file but it looks right to me:
disable "AllowSoftwareGLFallbackDueToCrashes"
disable "AllowSwiftShaderFallback"
enable "AllowD3D11WarpFallback"
How are you testing? You can use "--enable-features=AllowD3D11WarpFallback
--disable-features=AllowSoftwareGLFallbac
No plans, unfortunately. Chromium isn't set up to easily share resources
between different GL drivers right now.
On Tue, Jul 29, 2025 at 2:00 PM PhistucK wrote:
> I am just curious... Are there any plans to add WebGL 2 software rendering
> support/fallback? My machine can use fewer and fewer Web
Hey Erik, Ashley, Rick,
I want to be clear that I think having high WebGL availability is a good
thing. I don't think that users with software WebGL have a great experience
but it's likely better than no availability, at least for drawing static
things. What pushes this over the line and warrants
Hey Ashley,
I suspect the M133 in the chrome status page will be updated to a later
release. I also put the bug link (https://issues.chromium.org/40277080) on
that page.
Thanks for the feedback. Right now we're in a situation where we definitely
need to remove SwiftShader WebGL support but we're
On Wednesday, October 23, 2024 at 8:21:22 AM UTC-7 Yoav Weiss wrote:
> Can y'all flip the review bits for
> privacy/security/enterprise/testing/debuggability?
>
Done!
On Wed, Oct 23, 2024 at 11:23 AM Alex Russell
wrote:
> Thanks for the explanation, Geoff. We discussed at today's OWNERS meetin
I'll describe a use case that become better/possible:
The user creates a texture with the 'bgra8unorm' format but as an
additional view format of 'rgba8unorm-srgb':
const texture = device.createTexture({
size: [4, 4],
format: 'rgba8unorm',
usage: GPUTextureUsage.RENDER_ATTACHMENT |
GPUText
10 matches
Mail list logo
