clipchamp.com - Firefox is unsupported browser

[webcompat-bot]

URL: https://clipchamp.com/en/unsupported-browser/

Browser / Version: Firefox 81.0
Operating System: Windows 10
Tested Another Browser: No

Problem type: Something else
Description: Not compatible
Steps to Reproduce:

View the screenshot

Browser Configuration

• None

From webcompat.com with ❤️

[softvision-oana-arbuzov]

Thanks for the report, I was able to reproduce the issue.

Tested with:
Browser / Version: Firefox Nightly 83.0a1 (2020-10-08)
Operating System: Windows 10 Pro

Moving to Needsdiagnosis for further investigation.

[liamengland1]

Bad bot

[karlcow]

with a chrome UA it is working. This is intentional.

  function (e, t, r) {
    "use strict";
    r.r(t),
      r.d(t, "isSupportedBrowser", function () {
        return i;
      }),
      r.d(t, "isMobileBrowser", function () {
        return o;
      });
    r(5);
    var n = r(2),
      i = function () {
        var e = Object(n.getParser)(window.navigator.userAgent);
        return (
          (function (e) {
            return (
              ("desktop" === e.getPlatformType() ||
                "" === e.getPlatformType()) &&
              "Blink" === e.getEngine().name
            );
          })(e) &&
          ((function (e) {
            return e.satisfies({ chrome: ">=75" }) || !1;
          })(e) ||
            (function (e) {
              return e.satisfies({ edge: ">=80" }) || !1;
            })(e))
        );
      },
      o = function () {
        var e = Object(n.getParser)(window.navigator.userAgent);
        return "desktop" !== e.getPlatformType() && "" !== e.getPlatformType();
      };
    o()
      ? (window.location.href = "https://clipchamp.com/unsupported-device/")
      : i() ||
        (window.location.href = "https://clipchamp.com/unsupported-browser/");
  },

chrome ≧ 75 and edge ≧ 80

To be contacted to understand why.

[tomb-msft]

Hi! I'm an engineer working on Clipchamp. Happy to provide any info you need.

For some historical context, there have been Chrome-only features we've had a hard dependency on in the past (such as SharedArrayBuffers). To the best of my knowledge there aren't any blockers now, and we'll be prioritising building workarounds for missing functionality soon to get the app into a place where we feel comfortable with customers using it on other browsers. Which I am especially keen on as I use FF as my daily driver :)

That said, there are a handful of missing, different, and slow features we've identified in Firefox, generally around video:

• HTMLVideoElement.requestVideoFrameCallback is missing in Firefox. Mozilla's current position for this is positive.
• Web Codecs ImageDecoder, VideoDecoder and VideoEncoder are all missing in Firefox. Mozilla's position is positive. We have WASM fallbacks for these, but ideally we'd like to get rid of them in the future.
• createImageBitmap with a HTMLImageElement referencing an SVG file will always rasterize the SVG at the intrinsic size in the file, ignoring the width/height of the img element and the resizeWidth/resizeHeight options. Compared to Chrome/Edge which always rasterizes at the resizeWidth/resizeHeight size. As far as I can tell these both don't match the spec exactly, although Chrome's behaviour is certainly more useful. I'll look at filing a Firefox bug for this in the near future.
• createImageBitmap with a HTMLVideoElement seems to block and is very slow - it blocked for ~110ms each animation frame in my test. Compared to Chrome/Edge which returns immediately and resolves the returned promise very shortly after, before the next animation frame. texImage2D with a video element is also very slow - ~7ms in FF compared to ~0.5ms in Chrome/Edge under identical environments. This FF bug seems to be related but I haven't looked too closely yet.

We haven't done much investigation with Safari yet, although I'd guess the list would look similar.

Let me know if you need anything else!

[denschub]

That is very useful, thanks so much, @tomb-msft! I filed a new metabug on Bugzilla, https://bugzilla.mozilla.org/show_bug.cgi?id=clipchamp, to track the missing/buggy things there. If you do file a new bug for the createImageBitmap, please feel free to add that new bug as a dependency (just enter "clipchamp" in a new bug's "blocks" field) - or just ping one of us. :)

We're also happy to look into performance or interop issues ourselves, if you can provide a testcase or something that would allow us to look into it!

---

I tend towards closing this bug as a duplicate of the bugzilla bug. But since this also affects Safari, I'll leave this open in case @karlcow needs it!

[jrmuizel]

@tomb-msft Firefox implements webcodecs and HTMLVideoElement.requestVideoFrameCallback now. Are you able to retest to see if the other issues that you referred to in #59616 (comment) still exist?