Future Web Platform Enhancments
Maintainers usually reply within 1 day
@AristurtleDev is already working on this.
Since Sep 17, 2026.
Assessment
This issue has not been assessed yet.
Description
This issue is to track future implementations for the Web platform that are not going in the first release cycle. These are excluded from the first release cycle either because the change is larger than just the web platform and would affect all platforms and needs design discussion, or it's a limitation due to the current vendor versions we use such as SDL2
- Gamepad Vibration: This is not available in the current SDL2 + Emscripten path for web. Would require updating to SDL3
- Mouse XButtons: In SDL2 + Emscripten, the switch case check for mouse button explicitly only has cases for left, middle, and right mouse buttons, xbuttons are skipped.
- Mouse Lock: There is support for this through SDL2 + Emscripten, however implementing this would need to be something that is designed for and implemented on all platforms, not just web. The reason for this is that web is implemented as part of the new
MonoGame.Framework.Nativeproject, which we do not declare#ifdirectives for platform specific behavior on the native side. Instead platform specific behavior is handled in the native code. This means a new API likeMouse.LockCursorwould need to be implemented for all native platforms, not just web. So a larger design conversation needs to happen for this before implemented. - Support Independent MRT Blend State: MojoShader currently emits legacy GLSL ES 1 style source, including
gl_FragData[n]. This works for ordinary single output shaders on WebGL2, but multiple fragment outputs rely on the legacy WebGL 1 draw buffers extension path, which is not usable in WebGL2. Supporting MRT with independent blend states requires a WebGL2 compatible GLSL ES 3 shader path. We can add a runtime translation layer now but it's not ideal and would just be a temporary workaround. MonoGame's shader system is being reworked to replace MojoShader, so this feature is being deferred until then.
- Dominant language
- C#
- Stars
- 14.7k
- Forks
- 3.1k
- Avg merge
- 13h 17m
- Merged PRs (30d)
- 5
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from MonoGame/MonoGame
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
maintenance
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
bug dependencies platform: macos scope: native
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
maintenance scope: build
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
All issues in MonoGame/MonoGame
Similar issues
-
area:frontend bug FE P3
Difficulty 1/5 Under an hour Newbie friendliness 72/100
klasolsson81/jobbliggaren#2288 ·
Maintainers usually reply within 1 day
-
CLI: stale build hint, non-gofmt autocomplete output and a leftover `--revit=<year>` in the docsOpenCommand Line Utility (CLI)
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
pyrevitlabs/pyRevit#4217 ·
Maintainers usually reply within 1 day
-
area: ui bug ready
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 1 day
-
account bug effort:S P2
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
nightscout/nocturne#3745 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
modelcontextprotocol/csharp-sdk#2031 ·
Maintainers usually reply within 1 day