I'm seeing an issue where using the "type" attribute in a canvas tag to specify chart type seems to cause an exception to be thrown (TypeError: undefined is not a function). For example, doing something like
<canvas chart type="Line" ...></canvas>
rather than
<canvas linechart ...></canvas>
causes an exception to be thrown (at line 62 in angles.js).
If the type attribute is used to specify the chart type within a canvas tag, the type variable in angles.js appears to be undefined, so the function can't be called. Specifying the chart type in a canvas tag using an aliased type (ex. linechart) seems to work just fine, however.
Not 100% sure if the root of the problem lies within angles itself, or if it's an issue on my end. Just thought I would post my experience here to be safe.
I'm seeing an issue where using the "type" attribute in a canvas tag to specify chart type seems to cause an exception to be thrown (
TypeError: undefined is not a function). For example, doing something likerather than
causes an exception to be thrown (at line 62 in
angles.js).If the
typeattribute is used to specify the chart type within a canvas tag, thetypevariable in angles.js appears to be undefined, so the function can't be called. Specifying the chart type in a canvas tag using an aliased type (ex. linechart) seems to work just fine, however.Not 100% sure if the root of the problem lies within angles itself, or if it's an issue on my end. Just thought I would post my experience here to be safe.