Stub WebGL while replaying

[jasonLaster]

We have seen a couple examples where WebGL crashes while replaying with Failed to create WebGL context: Unknown error.

The exception has a control flow impact while replaying. In Nashi's case, the component that tried to create the WebGL context threw and did not render its children.

and everything under our DeckGL component is not rendering including html stuff (text, overlays), even though our error boundary is at the page level.

i think its because that the html overlays depend on the gl context to do projections from lat lng to pixel x y so it might not be possible its likely the html elements exist but just don't render where we expect them

I wonder if stubbing WebGL while replaying would improve this. I think this would be similar conceptually with how we use a simpler Garbage Collector. The MVP stubbed WebGL would probably just need to keep the same interface and effectively be a no-op.

CC #58

[jasonLaster]

This affects

• Facebook
• Nashi
• Cameron's Vaccine tracker

Both Nashi and Cameron are using mapbox

[bhackett1024]

We now return null when trying to create a WebGL context instead of throwing, fitting with the spec for getContext() and unbreaking some of the formerly broken pages. There isn't much we can do though to stub out WebGL though without things breaking in new and fascinating ways. We can message that the page uses WebGL and things might not work right (#314) but beyond that we just have to go and get recording/replaying WebGL to actually work.