Open Bug 1272193 Opened 5 years ago Updated 2 years ago

Test and handle nested webglcontextcreationerror

Categories

(Core :: Canvas: WebGL, defect, P3)

defect

Tracking

()

People

(Reporter: jgilbert, Unassigned)

References

Details

(Keywords: feature)

This will likely crash the content process right now.

Consider disabling the event from within an event.
However, this might be a useful usecase. (ok, that failed, let's try again)
In particular, trying webgl1 if webgl2 failed.

To some degree, this is a 'stop hitting yourself' sort of thing, but we should handle it the same way, say, stack overflows work in JS.
Keywords: feature
Type: defect → task
Priority: -- → P3
Assignee: jgilbert → nobody
Type: task → defect
You need to log in before you can comment on or make changes to this bug.