3 ms·
Is it idiosyncratic to assume that two variants of the canvas API support the same things?
by AshleysBrain 4y ago
Is it idiosyncratic to assume that two variants of the canvas API support the same things?
- bzzzt 4y agoConsidering it's a big API with dozens of methods I'd be surprised if two implementations would agree exactly.
- AshleysBrain 4y agoI would have assumed browsers had one internal implementation and exposed it through both APIs. They wouldn't want to have two separate implementations of a large amount of complex code.
- cxr 4y agoYes, and it's a little reckless to even get to a state where, even in the presence of bonafide bugs re non-standard behavior, just showing "a blank screen" when your app dies is a possibility. Add some basic error detection/reporting.
- AshleysBrain 4y agoWe did have basic error detection and reporting. For example if it failed to get WebGL in a normal HTML canvas, it would show a "WebGL not supported" error message with some diagnostic details and some advice about what the user could do about it. The problem in this case is a gotcha where there are two ways to access the canvas API, one supporting WebGL, and the other not - a case we never anticipated, nor had happened with any previous browser.