Error when testing using Toogle DOM deactive

[marogalli]

When I run my view tests with Toogle DOM deactive, I got the error :

Error: Invalid value for <svg> attribute width="undefined"
tests.html:1Error: Invalid value for <svg> attribute height="undefined"
tests.html:1Error: Invalid value for <svg> attribute width="undefined"

If I open the DOM on right side the error is gone.

Is this expected? Any way to avoid it?

Tks

[mats]

Is this in IE? Can you produce a test case for us that we can investigate? To force dom to be visible for certain tests, use the forceDOMVisible flag for that test.

https://www.bryntum.com/products/siesta/ ... DOMVisible

[marogalli]

Mats,

I am using Chrome.

This is reproducible just when you test 2 views in sequence not updating the browser.
Create 2 files with the content below :

StartTest(function(t) {		
		var view = Ext.create('Ext.Window', {
			 	renderTo: Ext.getBody(),
			 	height : 300,
			 	width : 300
	     });
			
			view.show();

});

Keep the view DOM closed during the test. Run the first (no errors), run the second (got the error), run the first again(got the error). If I refresh the browser and click the first the error is gone. If I keep clicking the first test I got no errors, but when I click the second the errors began.

Let me know If it was possible to reproduce.

[mats]

Not reproducible. Sure you don't have cached files etc?

[marogalli]

Strange...

My Chrome has in its configuration : Network -> Disable Cache checked.

This problem does not happen in Firefox. No clue what is going on.

At this moment, this errors is not affecting my test suite. I will go back to this issue for further analysis later.

Tks

[marogalli]

I think it is not a caching problem.

I ran Chome in Incognito mode, thus for sure no cache is done, but the error persists.

[mats]

ok, if it still happens in the next Siesta release please file a ticket here https://www.assembla.com/spaces/bryntum/support/tickets and we'll investigate further.

[nickolay]

Yes, I also seen this. This looks like an error from ExtJS, probably caused by feature testing. Should be gone once we'll switch the harness UI to Ext4.1