You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently (seemingly within the last two months) there's been a change/update in Google Chrome on android (or android system webview) that has removed support for the "OES_texture_float" extension. All maps apps throw errors when this extension is not available.
This has been reproduced on Pixel 6a devices (Shane, Tyler, Tyler's partner). Surprisingly, I haven't been able to track down a recent outcry about this issue causing errors elsewhere. Becky's Pixel 3 does not reproduce the error, so it may be specific to Google's more recent processors.
The functionality is available without extensions in webgl2, and there's been a bit of discussion about making regl compatible with it. regl-project/regl#561 It's likely that this wouldn't play nice without significant updates to maps though.
A stopgap could be sniffing for extension support and surfacing a more friendly user facing error than the current one.
Just really odd that we'd lose support for a previously supported extension!
The text was updated successfully, but these errors were encountered:
Recently (seemingly within the last two months) there's been a change/update in Google Chrome on android (or android system webview) that has removed support for the "OES_texture_float" extension. All
maps
apps throw errors when this extension is not available.This has been reproduced on Pixel 6a devices (Shane, Tyler, Tyler's partner). Surprisingly, I haven't been able to track down a recent outcry about this issue causing errors elsewhere. Becky's Pixel 3 does not reproduce the error, so it may be specific to Google's more recent processors.
The functionality is available without extensions in webgl2, and there's been a bit of discussion about making
regl
compatible with it. regl-project/regl#561 It's likely that this wouldn't play nice without significant updates tomaps
though.A stopgap could be sniffing for extension support and surfacing a more friendly user facing error than the current one.
Just really odd that we'd lose support for a previously supported extension!
The text was updated successfully, but these errors were encountered: