There's a perplexing issue I've encountered while attempting to launch a page containing WebGL content using a nightwatchJS-based framework:
When opening the page directly in Chrome, WebGL is properly detected. The Graphics Feature Status in chrome://gpu/ shows that most features are hardware accelerated.
However, when accessing the page through nightwatch, WebGL is not recognized and the Graphics Feature Status in chrome://gpu/ indicates that most features are software only.
If manually opening Chrome before initiating the nightwatch process, WebGL is still not detected in the new session, with the Graphics Feature Status showing software-only features.
Even when opening Chrome manually and running nightwatch with the same session profile, the page fails to load. Despite this, the Graphics Feature Status displays hardware acceleration for most features.
It's worth noting that everything was working smoothly until the end of August, when Chrome was updated. I attempted to update my version of chromedriver but without success, as Chrome automatically updates itself and doesn't permit downgrading to a specific version.
Has anyone successfully made a webgl page function with nightwatch? If so, could you provide insight on how to enable WebGL and hardware acceleration, and ultimately load the page via the nightwatch interface on both default and custom sessions?