Closed Bug 1632634 Opened 4 years ago Closed 2 years ago

Google stadia streaming support

Categories

(Web Compatibility :: Site Reports, enhancement)

enhancement
Not set
normal

Tracking

(firefox86 affected, firefox102 affected)

RESOLVED WONTFIX
Tracking Status
firefox86 --- affected
firefox102 --- affected

People

(Reporter: monteiro, Assigned: ksenia)

References

()

Details

(Keywords: webcompat:needs-diagnosis)

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:75.0) Gecko/20100101 Firefox/75.0

Steps to reproduce:

Trying google stadia free or paid service.

Actual results:

Google stadia requires a chromium based browser.

Expected results:

We should investigate why Firefox doesn't work even when changing the useragent.

Hi monterro,

Thanks for your report.

I'll go ahead and change the ticket type to Enhancement, and add it to the Web Compatibility component in the hope that someone from their team can look at this.

Regards,
Virginia

Type: defect → enhancement
Component: Untriaged → Desktop
Product: Firefox → Web Compatibility
Version: 75 Branch → unspecified

I'm able to log in while spoofing as Chrome, will try to do some testing

Flags: needinfo?(kberezina)

The issue still occurs on my side.
URL: https://stadia.google.com/warning/8
https://prnt.sc/wdne7q

Tested with:
Browser / Version: Firefox Nightly 86.0a1 (2020-12-30)
Operating System: Windows 10 Pro

Status: UNCONFIRMED → NEW
Ever confirmed: true
Assignee: nobody → kberezina

Teo, in bug 1696812 comment0, you mentioned that there is a standalone open source package for supporting Google Stadia on Firefox, would you mind to provide more information about that? I wonder if there is any importand web API which Stadia needs but Firefox doesn't support yet?
Thank you.

Flags: needinfo?(g_mode)

(In reply to Alastor Wu [:alwu] from comment #5)

Teo, in bug 1696812 comment0, you mentioned that there is a standalone open source package for supporting Google Stadia on Firefox, would you mind to provide more information about that? I wonder if there is any importand web API which Stadia needs but Firefox doesn't support yet?
Thank you.

Teo's comment about using Nativefier and Electron is just Chromium by another name, as Nativefier makes Electron apps, which are in fact Chromium under the hood (so unfortunately not Firefox).

@Alastor Wu

This is the github link of that app, although I reckon it probably is not useful for being implemented in Firefox anyway

https://github.com/liberodark/stadia-app

Flags: needinfo?(g_mode)

I found this discussion but not sure if it's correct, just keep it as a record. I think we should contact google and see what they need in order to run Stadia on Firefox.

Blocks: media-triage

(In reply to Alastor Wu [:alwu] from comment #8)

I found this discussion but not sure if it's correct, just keep it as a record. I think we should contact google and see what they need in order to run Stadia on Firefox.

I've done some poking around, but only minimally, if you go to https://stadia.google.com/ubisoftplus?accounts_redirect (this seems to break their user agent filtering easily), then go try to play a game you get a WebRTC error, so it definitely seems to be something about Firefox' WebRTC implementation (be it something that's not standard or something Firefox is missing).

Contacting Google and trying to get that relationship moving would definitely be the most productive thing though IMO, rather than trying to reverse engineer the WebRTC issue.

Per comment9, move this into webrtc-triage.

Blocks: webrtc-triage
No longer blocks: media-triage

(In reply to Wyatt Childers from comment #9)

(In reply to Alastor Wu [:alwu] from comment #8)

I found this discussion but not sure if it's correct, just keep it as a record. I think we should contact google and see what they need in order to run Stadia on Firefox.

I've done some poking around, but only minimally, if you go to https://stadia.google.com/ubisoftplus?accounts_redirect (this seems to break their user agent filtering easily), then go try to play a game you get a WebRTC error, so it definitely seems to be something about Firefox' WebRTC implementation (be it something that's not standard or something Firefox is missing).

Contacting Google and trying to get that relationship moving would definitely be the most productive thing though IMO, rather than trying to reverse engineer the WebRTC issue.

Could you attach a copy of this error?

Flags: needinfo?(Wyatt710)

(In reply to Byron Campen [:bwc] from comment #11)

Could you attach a copy of this error?

It's not a detailed error, it's simply: "WebRTC: <hash like thing> line 6 > injectedScript:459" where "<hash like thing>" is some hash like string. I'm censoring it as I can't say for sure if it's related to (potentially sensitive) session information or not.

Flags: needinfo?(Wyatt710)

We plan to have a chat with their devs to see if we can figure out why they don't support Firefox.

No longer blocks: webrtc-triage
Flags: needinfo?(kberezina)

The issue is still reproducible. Firefox is an unsupported browser:

https://prnt.sc/rZFc7xuYK9rv

Tested with:

Browser / Version: Firefox Nightly 102.0a1 (2022-05-25) (64-bit) / Chrome Version Version 102.0.4004.63 (Official Build) (64-bit)
Operating System: Windows 10 PRO x64

Status: NEW → ASSIGNED
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.