timvanscherpenzeel / detect-features Goto Github PK

First off, this is an awesome library! Thanks for making and sharing this.

It's similar to a small library we built for our Mozilla Games initiative: browser_feature_test (demo here)

Anyway, WebXR (VR + AR) is the new experimental API that will be soon superceeding WebVR.

Here's a helpful blog post by @toji (Chrome engineer on WebXR + WebGL + Gamepad) on the experimental WebXR support behind a feature flag in Chrome Canary: https://blog.tojicode.com/2018/02/early-access-to-webxr-device-api-in.html

And here are the two specs:

• https://immersive-web.github.io/webvr/spec/1.1/ — navigator.getVRDisplays, VRDisplay, etc.
• https://immersive-web.github.io/webxr/spec/latest/ — navigator.xr, XRDevice, etc.

Long story short: for WebXR, we just need to check for truthiness of navigator.xr as opposed to navigator.getVRDisplays.

Many thanks for this library and for your help going forward with this library!

It would be nice to get back the full userAgent string. I see that getFeatures is already using it via detect-ua would be nice to include device.userAgent perhaps under browserFeatures.browserType

HEllo! I want to implement your detection for PHP script on Wordpress behind Apache / Nginx , but its not quite easy to use something like https://gist.github.com/MStruntze/d7de3ea07b2777ca9f6d , especially if I dont know anything about javascript/node .

Maybe you know where I can get some parts of your script but on clean JS library?

Possible solution...

isAdBlockEnabled.ts

export const isAdBlockEnabled = async () => {
  try {
    await fetch('https://www3.doubleclick.net', {
      method: 'HEAD',
      mode: 'no-cors',
      cache: 'no-store',
    });
    return false;
  } catch (err) {
    return true;
  }
};