-
Notifications
You must be signed in to change notification settings - Fork 2.5k
AddRowHeader causes grid misalignment #3050
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@PaulL1 I also encountered this issue. |
This was referenced Mar 22, 2015
Moved this into the plunker: http://plnkr.co/edit/leP2x2FanozxMOD7grhF?p=preview |
PaulL1
added a commit
to PaulL1/ng-grid
that referenced
this issue
Mar 28, 2015
Change the style computations with the aim of making them deterministic and able to calculate widths in a single pass rather than being iterative. Fix angular-ui#3050, and somewhat improves angular-ui#1957, at least to my eye. Changes are: - change renderContainer updateColumnWidths to calculate across all visible columsn in all render containers, rather than trying to calculate one render container at a time (cannot otherwise work with * and %, these are of the whole grid, not just one render container) - change header updateColumnWidths to just rely on the renderContainer, not do it again itself in a slightly different way - change updateColumnWidths to be simpler, and to calculate percentages in a way that I think makes more sense - change resize feature to not attempt to 'resizeAround' the changed column, but rather allow updateColumnWidths to deal with it - change pinning to not call refresh twice when moving a column, this is now unnecessary - updates to tutorials
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When you use addRowHeader in conjunction with pinning and/or selection, you can get into situations where the grid doesn't render correctly. It looks like the width of the left render container is being incorrectly calculated.
There are probably workarounds by calling refresh or handleWindowResize (and in my real application, expanding a grouped row does it), but the point is that we shouldn't need to.
I think this may be a test case that will inform our grid refresh refactoring (if we ever do that), refer http://ui-grid.info/docs/#/api/design-rendering-cycle.
I will attach a plunker when plunker decides it'd like to start saving again. Until then the app.js and index.html are here so I can recreate later.
The text was updated successfully, but these errors were encountered: