Two svg compile tests fail in Chrome 54

[Narretz]

These two tests fail in Chrome 54 and Win 10.

angular.js/test/ng/compileSpec.js

Lines 442 to 467 in 5cce6e2

	if (supportsForeignObject()) {
	it('should handle foreignObject', inject(function() {
	element = jqLite('<div><svg-container>' +
	'<foreignObject width="100" height="100"><div class="test" style="position:absolute;width:20px;height:20px">test</div></foreignObject>' +
	'</svg-container></div>');
	$compile(element.contents())($rootScope);
	document.body.appendChild(element[0]);
	var testElem = element.find('div');
	expect(isHTMLElement(testElem[0])).toBe(true);
	var bounds = testElem[0].getBoundingClientRect();
	expect(bounds.width === 20 && bounds.height === 20).toBe(true);
	}));
	it('should handle custom svg containers that transclude to foreignObject that transclude html', inject(function() {
	element = jqLite('<div><svg-container>' +
	'<my-foreign-object><div class="test" style="width:20px;height:20px">test</div></my-foreign-object>' +
	'</svg-container></div>');
	$compile(element.contents())($rootScope);
	document.body.appendChild(element[0]);
	var testElem = element.find('div');
	expect(isHTMLElement(testElem[0])).toBe(true);
	var bounds = testElem[0].getBoundingClientRect();
	expect(bounds.width === 20 && bounds.height === 20).toBe(true);
	}));

[gkalpak]

👍 I think they started failing on Chrome v53 btw.

[gkalpak]

The reason why they fail is that <foreignObject> elements and their descendants seem to be reported as being 25% larger in each dimension 😕
For example, <foreignObject style="width: 100px; height: 100px;">...</foreignObject>, will be reported as being 125px x 125px by getBoundingClientRect(), although it will have the correct size actually.

[gkalpak]

Actually, it doesn't seem to be Windows-specific. I can make it fail on Ubuntu too.
See #15452 (comment).