[B3/RC1/RC2] Weird stuff happening on Chrome 18/19

[rhapsodyv]

Yes. It's a really big problem now. It's impossible to work in chrome now.

I have tried debugger the problem, but the layout calculation has a lot of code and the problem just don't happen when I'm debugging.

Are sencha devs working on it?

[rhapsodyv]

I think I found a solution!! How the problem seems to be random, I can't guarantee that is 100% working.

I don't know why, but the functions: ContextItem.jsetWidth and ContextItem.js: setHeight are being called with NaN.

So, the fix is simple: place an if in the init of this functions:

extjs-4.1.0-rc1/src/layout/ContextItem.js: line +/- 1243

setWidth: function (width, dirty /*, private {Boolean} force */) {
var me = this,
comp = me.target,
frameBody, frameInfo, padding;


if (isNaN(width)) {
return;
}

and

extjs-4.1.0-rc1/src/layout/ContextItem.js: line +/- 1203
setHeight: function (height, dirty /*, private {Boolean} force */) {
var me = this,
comp = me.target,
frameBody, frameInfo, padding;


if (isNaN(height)) {
return;
}


It's just a temporary fix. Now my team can back to work in chrome.

[cbaj26]

+1. I've noticed this issue with Chrome on Windows 7. On the Mac, I've had no problems with Chrome. I'm using Chrome 18 on both w/ ExtJS 4.1 RC1

[cbaj26]

I think I found a solution!! How the problem seems to be random, I can't guarantee that is 100% working.

I don't know why, but the functions: ContextItem.jsetWidth and ContextItem.js: setHeight are being called with NaN.

So, the fix is simple: place an if in the init of this functions:

extjs-4.1.0-rc1/src/layout/ContextItem.js: line +/- 1243

setWidth: function (width, dirty /*, private {Boolean} force */) {
var me = this,
comp = me.target,
frameBody, frameInfo, padding;


if (isNaN(width)) {
return;
}

and

extjs-4.1.0-rc1/src/layout/ContextItem.js: line +/- 1203
setHeight: function (height, dirty /*, private {Boolean} force */) {
var me = this,
comp = me.target,
frameBody, frameInfo, padding;


if (isNaN(height)) {
return;
}


It's just a temporary fix. Now my team can back to work in chrome.

@rhapsodyv - You deserve a medal. That fix works great!

[droessner]

Thanks rhapsodyv! Those changes seem to be working for me as well. I didn't do any additional debugging, but just wanted to confirm that I am also seeing the functions being called with NaN as the parameter.

[raphaelhbohrer]

Nice

[scancubus]

we just started getting this problem on chrome 18 update today. Any sencha team want to comment? We are going into production this weekend!

[rhapsodyv]

Have you tried my solution?
It's working fine. Try it until sencha release the right correction...

[bobringer]

rhapsodyv, you are my hero

[scancubus]

I just got upgraded to Chrome 18, and I cant stop getting the AW SNAP error in chrome...NEVER got this in chrome 17, and now chrome 18 is the standard version. Any help, this is killin me.