scrollTo doesn't work with higher rowHeight

[projectX21]

Hello everyone,

I've found a little Bug:
If you use a custom rowHeight, the scrollTo will not scroll exactly to the specified row.

I have a little example:
http://plnkr.co/edit/bO4JGSCeraASMTZ04zhA?p=preview

When you scroll down, and click the button "Go to top" afterwards, it will not scroll exactly to the first row.

Do you have a workaround for that problem? This is needed in my project.

Thank you for your help!

[yehuabin]

Can $http.get support cross domain?

[projectX21]

Sorry but I don't get it. Is that related to my question?

[yehuabin]

sorry not related. that just my a question

[imbalind]

@projectX21 the problem is here where you can see:

var pixelsToSeeRow = ((seekRowIndex + 1) * self.options.rowHeight);

here the +1 is needed to account for the header, but this is obviously right only if rowHeight === headerHeight. To make it more generic this should come:

var pixelsToSeeRow = ((seekRowIndex) * self.options.rowHeight + self.headerHeight);

[projectX21]

Thank you very much for this hint!

But is there a possibilty to get this work without modifing the source code?

[imbalind]

Meh.. I don't think so. Unless you can afford to have headers as high as the rows are.

[imbalind]

Here's a modified version of the plunkr, I had to add a minified version of ui-grid.js because of size issues.

[kylehoehns]

@JLLeitschuh any idea when the 3.0.8 release is scheduled? We are running into this same issue after upgrading from 3.0.1 to 3.0.7 and were hoping we could get this fix before our next release.

[projectX21]

But ist there an option to define the height of the header? On the wiki page I don't find such a property.

[lvostinar]

This issue is still not fixed. See http://plnkr.co/edit/aIxHXHKTSlxeSDavfqtR?p=preview . When pressing Scroll to top it scrolls to row with id 498. Scrolling is not really correct, row is only partially visible (with header height). So, now, scrolling as first row works well but scrolling as last row is broken.

See also comments from #4204 , which is a duplicate issue.