ref mapbox/mapbox-gl-js#2444

As of [email protected] WebGL 2 is required.

However, this library still outputs the value true when checking for support.

This library should now be updated to reflect the support based on the WebGL version so that it can be used inside of [email protected]

This module should fail for older versions of browser that no longer work: mapbox/mapbox-gl-js#8742

• publish to npm
• publish mapbox-gl-plugins repo

Hi everybody, today we started using the supported() method of mapbox-gl to check support before showing mapbox on an older version of Firefox that was throwing exceptions. After checking for support, the older version of Firefox is working great and skipping the map. But we still see some warnings.

Are those warnings that are logged in the process of checking support? Does this library do that differently?

@lucaswoj can we clarify in the readme what failIfMajorPerformanceCaveat means?

Chrome has been unsupported on OS X 10.6.8 for quite a while. The latest version seems to be 49.0.2623.

I'm getting reports that the compileShader part doesn't work on all those machines. It terminates with

AssertionError
null == true

For this line:
https://github.com/mapbox/mapbox-gl-js/blob/7c951985e4d967abc048ce5568c4edd6add05c8b/src/render/program.js#L44

Do you have any idea how to detect compilation errors? Or just blacklist OS X 10.6 + Chrome?
I don't have access to any such machine here.

Two scenarios where the browser Brave breaks mapbox gl

• mapbox/mapbox-gl-js#9186
• mapbox/mapbox-gl-js#8377

mapbox-gl-supported should check for these limitations and return false if we're going to be unable to render the map.

Hello,

I tested the "mapbox-gl-supported" on Android version 4.4.2 but the test does not fail though the map is not displayed properly:

The console is saying:
"WebGL : INVALID_OPERATION: drawArrays:attribs not setup correctly.
"WebGL : INVALID_OPERATION: no ELEMENT_ARRAY_BUFFER bound

I can add that on the same phone, under Chrome, the same map is displayed properly.

Should another test be added ?

Thanks

There is a cool example of Mapbox on https://www.mapbox.com/bites/00115/
Do you have the same example with Mapbox gl?
or If it's not available. Do you have access to source code to share it with me?

I need to use notSupportedReason method inside my webpack project.

How do that? We need a PR?

I'm running Google Chrome version 87.0.4270.0 (Official Build) dev (64-bit), which is currently the stock build on Fedora. Apps running Mapbox-gl now no longer work. Your detector states:

MAPBOX GL JS IS NOT SUPPORTED (INSUFFICIENT WEBGL SUPPORT)

This needs to be fixed before this Chrome release becomes mainline.

• kv, Karen

i am using gl-mapbox and i got error "Uint8ClampedArray" and "ReferenceError: Can't find variable: mapboxgl " in safari browser.

I am using this version GL-Jquery.

Open this link "https://dev1.usedirect.com/Californiamapbox" and right click on page and select Inspect element you can see error..

Now that we use named exports in v2, we should export webGLContextAttributes directly instead of making in a property of the supported function. I overlooked this but should be a quick change — only used internally in GL JS v2 and not documented, so might not need a semver-major.

Some older browsers, like (Chrome Mobile 36) doesn't support ArrayBuffer.isView, yet it's required.

The error being raised is:

Object function ArrayBuffer() { [native code] } has no method 'isView'

I'm using mapboxgl.supported() in an app to display a warning if map cannot work.
The problem is that since 1.5.0 it is using gl.createShader(gl.VERTEX_SHADER) code, which is throwing exception in Mobile Safari 9 on iPads and a bunch of other older browsers.

The exception is

r.createShader is not a function. (In 'r.createShader(r.VERTEX_SHADER)', 'r.createShader' is undefined)

This wouldn't be a big problem, but this library is supposed to detect especially these unsupported browsers without breaking the main app and unfortunately with recent release this happens.

The solution is maybe as simple as testing for gl.createShader first. I cannot test it, as I have no Mobile Safari / old iPads, I only see it in Sentry errors.

I've migrated a website to Mapbox GL JS and I'd like to show some friendlier warning to users with unsupported browsers. Such as "WebGL is not enabled" or "Please update your browser".

Right now it requires me to copy-paste the code from index.js into my own project.

I'd be nice to have .isWebGLSupportedCached exported as module's variables.

The NPM package name for this repo is still mapbox-gl-js-supported - will you be publishing this under the new name from now on?

Hello,

My team and I are working on an app that uses react-map-gl and mapLibre-gl-js. Our live site is required to run in a strict content security policy environment, so I've been following the steps in the maplibre documentation for setting the workerUrl. No issues in firefox, but chrome gives the same "refused to create worker from blob" every time.

I finally determined that this is caused by react-map-gl's call to the supported function, which creates a worker from a blob URL, which causes an error and indicates that the browser is not supported. This seems inaccurate because there is a fix for the content security policy issues, which would mean the browser is supported. It would be very useful to have a similar fix for the supported function.

Let me know if this is the wrong place for this issue, and thank you for your help.

moved from mapbox/mapbox-gl-js#1613

• check that Blob is defined
• check that WebWorkers can be spawned from a Blob