Open Bug 1730666 Opened 10 months ago Updated 15 days ago

LinkedIn video meetings not available for Firefox


(Web Compatibility :: Desktop, defect)



(Webcompat Priority:P2, firefox94 affected, firefox103 affected)

Webcompat Priority P2
Tracking Status
firefox94 --- affected
firefox103 --- affected


(Reporter: contact, Unassigned)




(Keywords: webcompat:site-wait, Whiteboard: [wfh])


(1 file)

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:92.0) Gecko/20100101 Firefox/92.0

Steps to reproduce:

On a private chat on LinkedIn I created a LinkedIn's video meeting.

The feature / button "Create video meeting" appears when I mentioned a date and time in the chat.

Actual results:

In the chat the preview of the featured link to LinkedIn's video meeting gave the message "LinkedIn video meetings aren’t available for Firefox. Please try a different browser."

Expected results:

The the preview of the featured link to LinkedIn's video meeting should mention teh user name, time and date and link to the call.

OS: Unspecified → All
Hardware: Unspecified → Desktop
Whiteboard: [wfh]
Version: Firefox 92 → unspecified

The message in the console is

11:42:45.137 Uncaught (in promise) CallingCommunicationError: BrowserNotSupported
    CallingCommunicationError aod99tj0849nhubiul43zki3h:4239
    CallStack aod99tj0849nhubiul43zki3h:109400
    CallClient aod99tj0849nhubiul43zki3h:110327
    initACS aod99tj0849nhubiul43zki3h:111583
    value aod99tj0849nhubiul43zki3h:115509
    promise callback*value aod99tj0849nhubiul43zki3h:115506
    value aod99tj0849nhubiul43zki3h:115485
    getClient aod99tj0849nhubiul43zki3h:115572
    fetchConferenceClient aod99tj0849nhubiul43zki3h:2731
    fetchConferenceClient aod99tj0849nhubiul43zki3h:3422
    openVirtualMeetingModal ad4qp8k9kf39ytdxbeqiuptu9:1233
    b 2912n3vj9vgysx0q5r9dbht3m:7236
    y 2912n3vj9vgysx0q5r9dbht3m:7245
    invokeWithOnError 2912n3vj9vgysx0q5r9dbht3m:6092
    flush 2912n3vj9vgysx0q5r9dbht3m:6076
    flush 2912n3vj9vgysx0q5r9dbht3m:6104
    _end 2912n3vj9vgysx0q5r9dbht3m:6205
    end 2912n3vj9vgysx0q5r9dbht3m:6153
    _run 2912n3vj9vgysx0q5r9dbht3m:6212
    _join 2912n3vj9vgysx0q5r9dbht3m:6210
    join 2912n3vj9vgysx0q5r9dbht3m:6165
    h 2912n3vj9vgysx0q5r9dbht3m:3799
    handleEvent 2912n3vj9vgysx0q5r9dbht3m:3167
    s 2912n3vj9vgysx0q5r9dbht3m:3598
    handleEvent 2912n3vj9vgysx0q5r9dbht3m:3167
    handleEvent 2912n3vj9vgysx0q5r9dbht3m:3025
    n 2912n3vj9vgysx0q5r9dbht3m:3043
    t 2912n3vj9vgysx0q5r9dbht3m:3056

and this is quite clear.

        const n = getBrowserInfo()
        if ('chrome' !== && 'chromium' !== && 'edgeanaheim' !== && 'safari' !== throw new CallingCommunicationError({
          message: CallStackErrorMessages.BrowserNotSupported,
          code: METHOD_NOT_ALLOWED

This is just user agent sniffing.

Let's try to fake the UA to be chrome.
The meeting starts when I fake the UA. There are errors in the console, but it's mostly working.

The main error is related to

Uncaught (in promise) TypeError: RTCPeerConnection.getStats: Argument 1 does not implement interface MediaStreamTrack.

I see a couple of issues on bugzilla related to getStats and MediaStreamTrack

Maybe Paul will know if it's a known issue.

Flags: needinfo?(padenot)
Ever confirmed: true

302 jib or pehrsons for this API.

Flags: needinfo?(padenot)
Flags: needinfo?(jib)
Flags: needinfo?(apehrson)

By spec there's RTCPeerConnection.getStats(optional MediaStreamTrack? selector = null), RTCRtpSender.getStats() and RTCRtpReceiver.getStats(). All of which we implement.

Chromium has RTCRtpSender.getStats(), RTCRtpReceiver.getStats() and a non-standard legacy version RTCPeerConnection.getStats(RTCStatsCallback successCallback, optional MediaStreamTrack? selector).

It seems likely that LinkedIn is using the chromium-specific legacy version and are passing a callback. Can we verify this and reach out?

Flags: needinfo?(kdubost)
Flags: needinfo?(jib)
Flags: needinfo?(apehrson)
Webcompat Priority: --- → P2
Flags: needinfo?(kdubost)
Summary: LinkedIn's video meeting → LinkedIn video meetings not available for Firefox

Contacted them on the partner mailing list

This is still an issue.

Tested with:
Browser / Version: Firefox Nightly 103.0a1 (2022-06-20)
Operating System: Windows 10 Pro

You need to log in before you can comment on or make changes to this bug.