V6 Text with Shadow Error - Is it a Bug?

[milonic]

Hi Guys,

Just wanted to check with you first before I submit a bug report.

If I add a shadow to a text object. Export as a JSON Object with this.canvas.toObject() then reload, I get error "Uncaught (in promise) TypeError: classRegistry.getClass(...).fromObject(...).then is not a function"

Has anything changed in V6 regarding shadows? I had a look but couldn't see anything.

The interesting thing is; if I remove: "type":"shadow" it seems to work, very odd.

Here's some code,

var canvas = new fabric.Canvas('canvasObj')

var testJSON={
	"version": "6.0.0-beta19",
	"objects": [
		{
			"fontSize": 80,
			"fontWeight": "normal",
			"fontFamily": "Times New Roman",
			"fontStyle": "normal",
			"lineHeight": 1.16,
			"text": "Some Text",
			"charSpacing": 0,
			"textAlign": "left",
			"styles": [
			],
			"path": null,
			"pathStartOffset": 0,
			"pathSide": "left",
			"pathAlign": "baseline",
			"underline": false,
			"overline": false,
			"linethrough": false,
			"textBackgroundColor": "",
			"direction": "ltr",
			"type": "IText",
			"version": "6.0.0-beta19",
			"originX": "left",
			"originY": "top",
			"left": 20,
			"top": 20,
			"fill": "ffffff",
			"stroke": "blue",
			"strokeWidth": 3,
			"strokeDashArray": null,
			"strokeLineCap": "butt",
			"strokeDashOffset": 0,
			"strokeLineJoin": "miter",
			"strokeUniform": false,
			"strokeMiterLimit": 4,
			"scaleX": 1,
			"scaleY": 1,
			"angle": 0,
			"flipX": false,
			"flipY": false,
			"opacity": 1,
			"shadow": {
				"color": "blue",
				"blur": 40,
				"offsetX": 0,
				"offsetY": 0,
				"affectStroke": false,
				"nonScaling": false,
				"type": "shadow"
			},
			"visible": true,
			"backgroundColor": "",
			"fillRule": "nonzero",
			"paintFirst": "fill",
			"globalCompositeOperation": "source-over",
			"skewX": 0,
			"skewY": 0
		}
	]
}

canvas.loadFromJSON(testJSON,function(e){}).then( 
(i) => {
	canvas.renderAll()
})

Try removing "type":"shadow" - it works if you do.

Do you want me to submit a report?

[asturur]

i think this is fixed in latest beta 20. It was recently fixed here:
#9712

[milonic]

Ooh, I had no idea there was a Beta20 out.

Just tried that and it fixes the problem.