1800880 - (clipchamp) Clipchamp not supported in Firefox

Status: ASSIGNED

(Web Compatibility :: Site Reports, task, P1)

Description

[Dennis Schubert [:denschub]]

Clipchamp, now a Microsoft product, isn't supported in Firefox. From the WebCompat bug, where one of their engineers commented, we've learned that there are a couple of platform features and bugs that are relevant here.

Let's use this metabug to keep track of those!

Comment 1

[Dennis Schubert [:denschub]]

Tentatively adding bug 1486454 as another dependency, as per the comment in the web-bug. It might be a different performance issue, but it's worth keeping track of that in some way.

Comment 2

[az [:az]]

I tested Clipchamp spoofing the UA on both nightly and my WIP rVFC implementation. On nightly, the video doesn't show at all, and neither video nor audio work when you click play. With the WIP patches, the video interface is visible, you can apply filters / etc, and you can navigate the timeline. Currently, when you click on play, it plays back audio but frames aren't updating properly. I should be able to get this working better with some changes.

Comment 3

[Jeff Muizelaar [:jrmuizel]]

I did some brief testing of clipchamp and it seemed to mostly work. I've reached out to an engineer on the product in https://github.com/webcompat/web-bugs/issues/59616#issuecomment-2379433251 to see how things are looking now.

Comment 4

[az [:az]]

Changed my UA to bypass the "browser not supported page" and tested clipchamp briefly and it appears to be working (uploaded multiple clips, added text + transitions, etc.). Not sure what more needs to be done on this one.

Comment 5

[Jeff Muizelaar [:jrmuizel]]

(In reply to az [:az] from comment #4)

Changed my UA to bypass the "browser not supported page" and tested clipchamp briefly and it appears to be working (uploaded multiple clips, added text + transitions, etc.). Not sure what more needs to be done on this one.

Outreach to Microsoft to ask them if there's any reason they're blocking Firefox. You can write to them using the mozilla-microsoft-discuss list.

Comment 6

[az [:az]]

I reached out to MS for comment. Will update when I hear back.

Comment 7

[Jeff Muizelaar [:jrmuizel]]

Chrome mask doesn't allow me to signin. We should figure out why

Comment 8

[Dennis Schubert [:denschub]]

Let's set diagnosis-team: webcompat for now due to comment 7.

Comment 9

[Holger Benl [:hbenl]]

It does work if you enable Chrome Mask for https://app.clipchamp.com (it looks at window.navigator.userAgent).
The problem is that the signup button is on https://clipchamp.com and https://app.clipchamp.com will immediately redirect to https://clipchamp.com/unsupported-browser/ without Chrome Mask. To enable Chrome Mask on https://app.clipchamp.com you need to somehow pause on that domain, I did so by enabling the "Script First Statement" event listener breakpoint.
I played with the app for a few minutes and did not find anything that looked broken.

Comment 10

[Daniel Holbert [:dholbert]]

Per comment 9, it sounds like comment 7 turned out to just be a limitation of Chrome Mask being origin-specific in its masking (and the site works if you enable Chrome Mask for an additional origin).

--> Removing needs-diagnosis; this is already flagged as webcompat:needs-contact which seems to be the appropriate status for the UA-sniffing here.

Comment 11

[Daniel Holbert [:dholbert]]

(In reply to Jeff Muizelaar [:jrmuizel] from comment #5)

Outreach to Microsoft to ask them if there's any reason they're blocking Firefox.

(In reply to az [:az] from comment #6)

I reached out to MS for comment. Will update when I hear back.

az: did you hear anything back about this? (Maybe worth repeating the outreach if you didn't get a message back or if things went quiet.)

(Per comment 4 and comment 9, it sounds like things work just fine here if we pretend to be Chromium. Maybe/hopefully the block here is historical and no longer needed.)

Comment 12

[az [:az]]

I didn't hear anything back so I just sent out another message. I'll update here when I find out more.

Comment 13

[Daniel Holbert [:dholbert]]

(In reply to Daniel Holbert [:dholbert] from comment #10)

--> Removing needs-diagnosis; this is already flagged as webcompat:needs-contact which seems to be the appropriate status for the UA-sniffing here.

(er whoops, it looks like I didn't actually remove this keyword. :) Doing so now.)

Comment 14

[az [:az]]

Heard back from MS - they have nothing new on their side to report. I asked if they could share a general timeframe with us - if I get more info, I'll share it here.

Comment 15

[Daniel Holbert [:dholbert]]

Thanks. Given that...

• this seems to be working if we spoof as Chrome (comment 3, comment 4, comment 9)
• we're not getting anything back in the way of reasons-that-Firefox-is-being-blocked
• we've made an effort to ask the site to remove the block (but are not yet clean on when they'll do that)

...this is probably ready to just be sitepatched to spoof as Chrome, in the interests of getting things working for our users, unless/until the site lifts the UA-sniffing block.

Comment 16

[az [:az]]

As an update - MS said that they're trying to follow up with the people responsible for testing on their side but didn't give a timeframe.

Comment 17

[Dennis Schubert [:denschub]]

I agree with comment 15, let's try shipping a site-patch, given how long it's been.

Comment 18

[Thomas Wisniewski [:twisniewski]]

Their app doesn't support mobile right now, so I'll add a desktop override for now.

Comment 19

[Thomas Wisniewski [:twisniewski]]

Attachment: Bug 1800880 - add a UA override for clipchamp.com; r?denschub

Comment 20

[Pulsebot]

Pushed by [e-mail]:
https://github.com/mozilla-firefox/firefox/commit/f8f6eba8ddc8
https://hg.mozilla.org/integration/autoland/rev/276945c541b2
add a UA override for clipchamp.com; r=denschub,webcompat-reviewers

Comment 21

[Cristian Tuns]

https://hg.mozilla.org/mozilla-central/rev/276945c541b2