Canvas 2D code should not have IIDs on concrete implementation classes

NEW
Unassigned

Status

()

Core
Canvas: 2D
6 years ago
6 years ago

People

(Reporter: bjacob, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

This is a bit like what bug 705668 did for WebGL.

The Canvas 2D impl has IIDs on concrete implementation classes, which seems weird.

Is any of that meant to allow checking object type with do_QueryInterface? If yes, the new better way to ensure that objects are of the expected type is probably to mark interfaces as builtinclass in the IDL, no?
(Reporter)

Updated

6 years ago
Summary: Canvas 2D code should have IIDs on concrete implementation classes → Canvas 2D code should not have IIDs on concrete implementation classes
You need to log in before you can comment on or make changes to this bug.