[GH-ISSUE #4] Deprecate Browser runner in favor of Web runner #2

Open
opened 2026-10-30 22:07:11 +00:00 by bsakaguchi · 8 comments
Owner

Originally created by @tannisroot on GitHub (Mar 9, 2019).
Original GitHub issue: https://github.com/lutris/web-runner/issues/4

Originally assigned to: @daniel-j on GitHub.

Web runner is far more advanced, works way better and can do the same things Browser runner can.
So why does the latter still exist and even comes pre-installed with default Lutris configuration and no option to remove it?

Originally created by @tannisroot on GitHub (Mar 9, 2019). Original GitHub issue: https://github.com/lutris/web-runner/issues/4 Originally assigned to: @daniel-j on GitHub. Web runner is far more advanced, works way better and can do the same things Browser runner can. So why does the latter still exist and even comes pre-installed with default Lutris configuration and no option to remove it?
Author
Owner

@aboogesnickle commented on GitHub (Apr 20, 2019):

Currently I am unable to use web runner for Duelyst because it does not support WebGL. I am using the Browser Runner with my default browser right now to play it.

Some one comment on this saying that the Electron Browser that Web Runner uses needs to be updated, but I would like to use the Browser Runner until that is fixed.

<!-- gh-comment-id:485123399 --> @aboogesnickle commented on GitHub (Apr 20, 2019): Currently I am unable to use web runner for Duelyst because it does not support WebGL. I am using the Browser Runner with my default browser right now to play it. Some one comment on this saying that the Electron Browser that Web Runner uses needs to be updated, but I would like to use the Browser Runner until that is fixed.
Author
Owner

@tannisroot commented on GitHub (Jan 1, 2020):

Web runner does support WebGL. Can't test the game though as it's region locked.

<!-- gh-comment-id:570057220 --> @tannisroot commented on GitHub (Jan 1, 2020): Web runner does support WebGL. Can't test the game though as it's region locked.
Author
Owner

@strycore commented on GitHub (Jan 1, 2020):

I can reproduce this issue. I'm moving it in the buildbot web-runner repo since this requires a runner update.

Screenshot from 2020-01-01 14-44-58

<!-- gh-comment-id:570089893 --> @strycore commented on GitHub (Jan 1, 2020): I can reproduce this issue. I'm moving it in the ~~buildbot~~ web-runner repo since this requires a runner update. ![Screenshot from 2020-01-01 14-44-58](https://user-images.githubusercontent.com/280336/71647030-65f4f600-2ca5-11ea-9aa3-ed48356eedd0.png)
Author
Owner

@strycore commented on GitHub (Jan 1, 2020):

@daniel-j that might be an option to pass at build time?

<!-- gh-comment-id:570090216 --> @strycore commented on GitHub (Jan 1, 2020): @daniel-j that might be an option to pass at build time?
Author
Owner

@tannisroot commented on GitHub (Jan 2, 2020):

Various test pages show that our Web runner does actually support WebGL:
image
Perhaps this is some user agent crap?

<!-- gh-comment-id:570129506 --> @tannisroot commented on GitHub (Jan 2, 2020): Various test pages show that our Web runner does actually support WebGL: ![image](https://user-images.githubusercontent.com/10602045/71654799-b1aaac80-2d44-11ea-814b-9f0d91b5c71f.png) Perhaps this is some user agent crap?
Author
Owner

@rejexy commented on GitHub (Feb 21, 2020):

Screenshot from 2020-02-21 16-10-32
I have same problem with webGL

<!-- gh-comment-id:589648430 --> @rejexy commented on GitHub (Feb 21, 2020): ![Screenshot from 2020-02-21 16-10-32](https://user-images.githubusercontent.com/60342258/75037495-5cc61f80-54c5-11ea-9c55-832fd6021889.png) I have same problem with webGL
Author
Owner

@rejexy commented on GitHub (Feb 21, 2020):

I found solution. Usage electron from distro repo supports webGL.

<!-- gh-comment-id:589653374 --> @rejexy commented on GitHub (Feb 21, 2020): I found solution. Usage electron from distro repo supports webGL.
Author
Owner

@Medath commented on GitHub (May 5, 2020):

I'm pretty sure just upgrading the electron version in the web runner will help. At least my testing from quite a while ago suggests that. The current web runner uses an electron version that's over two and a half years old by now

<!-- gh-comment-id:624327905 --> @Medath commented on GitHub (May 5, 2020): I'm pretty sure just upgrading the electron version in the web runner will help. At least my [testing from quite a while ago](https://github.com/lutris/buildbot/issues/89) suggests that. The current web runner uses an electron version that's over two and a half years old by now
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
lutris/web-runner#2
No description provided.