Clarification regarding context loss handling

Khronos' documentation on handling context loss states:

Don’t check for null on creation
var program = gl.createProgram();
if (program === null) // BAD!!!
You should really only get null from these functions if the context is lost and in that case there’s no reason to check. WebGL is designed so that for the most part everything just runs as normal even when a program or shader is null.

However, it's recently come to my attention that implementations will raise errors if you apply the "keep on truckin'" approach recommended in the above documentation:

https://github.com/microsoft/TypeScript-DOM-lib-generator/issues/1262#issuecomment-1054917371

Is the documentation incorrect, or are the implementations incorrect?

Start with the linked Khronos Handling Context Lost documentation and the TypeScript-DOM-lib-generator issue comment. Compare the documented null-handling guidance with the implementation behavior described there, then determine whether the documentation or implementations need correction. Done means the discrepancy is resolved and the relevant guidance is clarified.