Thanks for the link.
I don't have time to spend looking around all forum bugs. There is no official fix for this one. I have no more time to spend, on beta releases. I think I'll wait for a 4.1 release or 4.1.x stable release.

Same here, I'm willing to wait. Maybe by Summer 2012 (aka Q3), we'll have a good working version of the 4.1.x branch... (?) Until then, I'm sticking with 4.0.7.

Perfection as a goal is a nice idea that can point one in a specific direction. However, since "perfection" is an ever changing (evolving?) and moving target, one must admit that perfection can never be obtained...

When in doubt, check the d4mn source code!
================================================
And here are my terms...

I don't care if you use my source code. (Known as "Code.")

I don't care if I get any monetary compensation.

I do care to receive credit for Code provided. So, please keep my name in the comments for Code provided.

Code is provided without warranty "AS-IS" and I claim absolutely no warranty nor liability to the quality, security, and run-ability on any platform.

By using Code, you accept all risk inherit with Code regardless if Code has known and yet to be discovered bugs.

You are welcome to change and improve the Code to best meet your needs.

I don't care if you use the Code in a commercial or open-source project.

I have tried Ext 4.1.0 beta 2 and have had serious compatibilty issues:

For example, tbtext elements were misaligned. Secondly, the width of variuos form's fields were broken or changed (these all for the Google Chrome browser). Moreover, when I switched to Firefox, some of the fields in 'hbox' layout in 'fieldcontainer' either disappeared or weren't rendered properly at all.

I'm not critisizing you too heavily, but really hope that 'Ext 4.1.0 stable' will be really stable. When you were launching Ext JS 4, there were superficial claims that it will be faster than 3.4.

Ok, after the one year, we all discovered that even 4.1 would not be as fast as 3.4.

Please improve the documentation in regard to the store attribute.
When does it need to be the full qualified classname e.g. MyApp.store.Foo and when the storeId.
I also had a hard time finding that adding a store to the stores config option of a controller automatically registers a storeId for it!

Pivot Grid

Pivot Grid

We are using Pivot grid in out existing ExtJs app. We are planning to move to ExtJs 4. Looked in to Beta 2 release of ExtJs 4.1 and looks like Pivot grid is still not included in this release. When can we expect Pivot grid as part of ExtJs 4?

Comparison of 4.0.7 and 4.1b2 Buffered Grid

Comparison of 4.0.7 and 4.1b2 Buffered Grid

Hi, I've done a comparison of the b2 buffered grid on 4.0.7 - for a grid that is 500 rows by 24 columns.

b2 initializes very quickly in comparison to 4.07, particularly if the number of rows is increased to 5000 rather than 500. Unfortunately, the scrolling in 4.1b2 is very jearky, and not something I can put in front of my clients, whilst 4.0.7 is very smooth.

Is there a smoothing solution in the pipeline for 4.1, are there any changes I can make to PagingScroller to improve the smoothness of the scrolling?