Limitations of WGLMakie backend (tracking issue)

[kbarros]

WGLMakie loads interactive graphics inside a web context. It can be useful with Jupyter notebooks, or for remote Sunny sessions where a GLMakie connection isn't possible. However, support for WGLMakie is still maturing. If you encounter graphics issues, consider using GLMakie instead for a more reliable experience.

Major outstanding problems with WGLMakie:

• Incompatibility with many Jupyter notebook environments (Fail gracefully if WGLMakie incompatibility is detected MakieOrg/Makie.jl#3769). IJulia is compatible, but others (like the VSCode notebook browser) are not.

Would be nice to have:

• Enable more precompiling of WGLMakie MakieOrg/Makie.jl#4103.
• WGLMakie DataInspector does not cover everything MakieOrg/Makie.jl#3773.

Many other problems have been resolved or mitigated:

• Inconsistent activation of widgets (Inconsistent mouse-over activation of widgets in WGLMakie MakieOrg/Makie.jl#3752).
• Missing fonts for some characters (WGLMakie DataInspector is missing some font characters MakieOrg/Makie.jl#3516).
• Fix transforming surface normals MakieOrg/Makie.jl#3722
• Mouse-over lines does not give reliable information (Strange behavior when inspecting lines in WGLMakie MakieOrg/Makie.jl#3672)
• Cannot vendor WGLMakie custom fonts A workaround is to select from the Makie built-in fonts.
• Interactive WGLMakie figure throws errors (Interactive WGLMakie figure throws errors MakieOrg/Makie.jl#3781). See issue comments for remaining bugs, which seem linked to Bonito.
• Occasional WGLMakie crashes inside VSCode panel #290.