I checked, and I don’t have such variable there at all. It shows:
Window protocol: **xwayland**.
Driver WebGL 2 WSI info:
EGL_MESA_configless_context EGL_MESA_drm_image EGL_MESA_image_dma_buf_export EGL_MESA_query_driver EGL_NOK_texture_from_pixmap EGL_WL_bind_**wayland_display**
EGL_EXT_platform_x11 EGL_EXT_platform_device EGL_MESA_platform_surfaceless EGL_EXT_explicit_device EGL_KHR_**platform_wayland** EGL_EXT_**platform_wayland** EGL_KHR_platform_gbm EGL_MESA_platform_gbm EGL_EXT_platform_xcb
IsWebglOutOfProcessEnabled: 1
Ah, I just realized, I don’t use stock firefox but firefox-appmenu-bin - this may do the whole difference. It’s a version with applied patches for global menus.
Anyway, I’m not an expert and since it works for me, I don’t want to mess it up.
Also, I don’t have any special Wayland related global environmental variables.
I use a laptop with Nvidia hybrid graphics and Wayland works pretty great.
Maybe you don’t need that variable? Did you add this manually? In the past we had to use several variables to enable Wayland and Nvidia related things like EGL strings, but it’s not needed anymore.
Moderator edit: In the future, please use proper formatting: [HowTo] Post command output and file content as formatted text