Scroll Issue in 2.0.11

[ManojSridhar]

In my ng-grid the horizontal scroll is creating problem. Only certain columns are visible. When i scroll right i get empty grid.

[ManojSridhar]

So @PaulL1 is this a bug and currently there is no work around for this?

[PaulL1]

It looks to be potentially a bug. I have little experience with 2.x, so not qualified to comment in a lot of detail - what I normally do is to classify the 2.x defects as such so that if someone with 2.x experience has time to look at it they can do so. In general terms most of the team work on 3.x now, and there are very few people left on the team who still have 2.x expertise - one of the hazards of open source I guess.

[ManojSridhar]

Ok, adding few points : I have enabled and disabled pinning but the columns are yet not displayed in right. i am not dealing with any performance improvement, i am not even able to get the last few columns after any time.

http://stackoverflow.com/questions/26884036/horizontal-scrolling-of-ng-grid

[ManojSridhar]

Where can i get 3.x. Is the release stabilised?

[PaulL1]

3.0 rc15 is available via bower - bower install angular-ui-grid. It is not fully stable, but is quite close.

[ManojSridhar]

Is there huge work to do in code wise if i change my ng-grid to ui-grid?

[ManojSridhar]

I have downloaded 3.0 from https://github.com/angular-ui/ng-grid In the downloaded file which is the one i want to include in my project. I have 2.0.11 already used in my project.

[ManojSridhar]

And in this example http://plnkr.co/edit/UfFnsZ?p=preview the horizontal scrollbar works fine for ng-grid. But for my case the ng-grid has issue with scrollbar. This is really confusing.

[ManojSridhar]

I have found answer for the issue. Actually there were two steps to be followed: * The width of each column should be given in px format only. There will be some issue if it is given in %format. * The ng-grid.css have to be updated to have .ngviewport class with overflow:auto. In my project .ngviewport did not have overflow and this too was a reason for the issue.

[c0bra]

@ManojSridhar did that workaround take care of it for you? If so I'll go ahead and close this. Thanks.