1796796 - Firefox 106 fails on netflix with DisplayLink

Status: RESOLVED WONTFIX

(Core :: Audio/Video: Playback, defect)

Description

[smallufo]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/106.0.0.0 Safari/537.36

Steps to reproduce:

Open netflix and play any video

Actual results:

No video output, just audio.

Expected results:

Video should output OK.

It works with Firefox 105 , but failed with Firefox 106. I think there's something wrong with the updated WebRTC library incorporated in v106.

Environment : MacBookAir M2 with DisplayLink , with 2 external monitors.

Video recordings below :
Firefox 106, failed : https://youtu.be/qBKBK5to41w
Firefox 105, OK : https://youtu.be/Jrx6ZdISrL8

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Core::WebRTC: Audio/Video' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 2

[philip.oliver98]

I also have this issue - had to rollback to 105 for now.
MacBook Pro Intel with DisplayLink

DisneyPlus also fails, looks like it could be DRM compatability issue

Comment 3

[Jeff Muizelaar [:jrmuizel]]

Can you try getting a regression window with mozregression?

Comment 4

[Jim Mathies [:jimm]]

Also, could you check to see if this works in Chrome?

Comment 5

[smallufo]

(In reply to Jim Mathies [:jimm] from comment #4)

Also, could you check to see if this works in Chrome?

No , Chrome always fails with DisplayLink enabled . I have to disable DisplayLink to make Netflix correctly work on the only one external monitor.
That's why I switched to Firefox, which Netflix works correctly on both external monitors.
But after Firefox 106, the behavior is the same with Chrome.

Comment 6

[Brad Werth [:bradwerth] | Out until Feb 2025]

Possibly fixed by Bug 1797292. Please re-test on Nightly.

Comment 7

[Brad Werth [:bradwerth] | Out until Feb 2025]

(In reply to Brad Werth [:bradwerth] from comment #6)

Possibly fixed by Bug 1797292. Please re-test on Nightly.

Sorry, I misunderstood the issue. This is expected DRM behavior.