Meta: Improve Cross-Browser Compatibility

[amacneil]

This is a meta-issue tracking work happening to improve cross-browser compatibility. Currently, we only support Chrome (v76+?).

• Edge: I don't believe anyone has tested, but since it uses Blink it might work?
• Safari, and all browsers on iOS/iPadOS (which are forced to use Webkit) (Safari support #149)
• Firefox
• https://github.com/foxglove/studio/issues/2505

[ic]

I would like to just share the latest container to this day does not work at all on Firefox. It has become such a minor browser that it may not be relevant, but main one here.

The error trace is little interesting, blocked at initialisation.

Also, I am on an beta version of the Firefox (97.0b2 (64-bit)), not always stable, yet everything else seems to work as expected.

Good luck with all the tasks ahead (beyond browser support!)

[amacneil]

We don't support Firefox yet, since it's lacking a few features and we have not yet built workarounds (also, we have not yet set up cross-browser testing which is a pre-requisite to proper support).

However, the error you're seeing is weird. It looks like maybe related to an extension you have installed? I can visit studio.foxglove.dev in FF (Ubuntu 20.04 ARM) just fine. Does that only happen in the container for you or does it also happen on studio.foxglove.dev?

[jtbandes]

Per instructions in the readme, I just tried running docker run -it --rm -p "8080:8080" ghcr.io/foxglove/studio:latest and visiting localhost:8080 in Firefox 96.0.1, and it works for me. What data source are you loading into Studio?

[ic]

We don't support Firefox yet, since it's lacking a few features and we have not yet built workarounds (also, we have not yet set up cross-browser testing which is a pre-requisite to proper support).

However, the error you're seeing is weird. It looks like maybe related to an extension you have installed? I can visit studio.foxglove.dev in FF (Ubuntu 20.04 ARM) just fine. Does that only happen in the container for you or does it also happen on studio.foxglove.dev?

Thank you @amacneil for your prompt feedback. And sorry for the late reply.

As for today, the online version at studio.foxglove.dev does work fine, indeed! It does point out that the only supported browser is Chrome, but seems functional (not used much at this point).

[ic]

Per instructions in the readme, I just tried running docker run -it --rm -p "8080:8080" ghcr.io/foxglove/studio:latest and visiting localhost:8080 in Firefox 96.0.1, and it works for me. What data source are you loading into Studio?

I could not reach the data loading step :-D

If working in 96.x, then a problem with the version I am using (beta 97).

Given your feedback, please discard my comment, as it should be transient issue.

We are a handful on Firefox interested in Studio, and will watch any call for testers.

[amacneil]

I think those errors are either happening because you're using a beta version of Firefox, or because of some extension you have installed. I would be curious to hear if it works in the latest stable version of Firefox with no extensions loaded?

[TBK]

I can confirm that it works perfectly fine with Microsoft Edge (100.0.1185.44) on Windows 11.

Newer Edge versions are based on Chromium.

[amacneil]

Yeah we should probably list Edge as officially supported and remove the warnings, since it's all Chromium under the hood.

[joewong00]

Hi, is there any updates on this? Foxglove websocket still cannot be opened on chrome/safari/edge in tablets or phones despite being the latest version. Thanks.

[jtbandes]

Hi,
There’s still no official update to share on this. However the issue you’re describing sounds like you are encountering a security error rather than a cross-browser compatibility issue. If you can enable SSL on your websocket server (wss://) then it should load in any browser on any device.

[joewong00]

Hi, I already tried using SSL on websocket server. Unfortunately I am still unable to connect to the ros master using latest chrome on IOS. Is it really already fully supported on any browser and any device?

[Jooolee]

I have same scene and something wrong.

[Jooolee]

when resolve this problem? Our team need play bag in Phone..

in Iphone, webpack-dev-serve disconnected! and Stop to 'Setting render frame to world'

In Chrome Web. it is ok. It can show log 'Setting render frame to World'

[Jooolee]

In Phone safari（webkit），It look like waiting load bag.