Aleksandra Budnik comments

Results 578 comments of


                                            Aleksandra Budnik

Adding a large number of rows breaks the table with a maximum stack exceeded error.

I'm closing this issue as solved in Handsontable v12.1.3.

fixedColumnsLeft with rowHeaders hidden creates a 1px shift

Hi @Maxoudela if you define the height for your `IMG` the issue should be gone https://jsfiddle.net/L9k2dvbc/ Please confirm if it works for you.

fixedColumnsLeft with rowHeaders hidden creates a 1px shift

Thanks to @aninde we discussed that it is OK on Chrome but is not working well on Firefox ![Zrzut ekranu 2020-10-13 o 13 29 44](https://user-images.githubusercontent.com/10757813/95855180-49b7d680-0d58-11eb-97e7-e281cfd6bc4e.png) (effect on scrolling to the...

fixedColumnsLeft with rowHeaders hidden creates a 1px shift

Those issues might be related. I would prefer to keep them in one place. Nevertheless, we may end up separating them after doing the investigation.

fixedColumnsLeft with rowHeaders hidden creates a 1px shift

The issue is still replicable, v12.1.2 demo https://jsfiddle.net/785ckhry/1/ Result ![Screenshot 2022-09-13 at 15 30 34](https://user-images.githubusercontent.com/10757813/189914260-b7f13ab4-d901-43c3-851c-07f057ef41ce.png)

[12.1.0] DropDown menu doesn't show again after filtering with nestedHeaders

Seems to be related to https://github.com/handsontable/handsontable/issues/9753

[12.1.0] DropDown menu doesn't show again after filtering with nestedHeaders

Update: Related issue just got fixed in v12.2.0 https://github.com/handsontable/handsontable/issues/9753 This issue is still replicable in 12.2.0

Delete removed core methods from definition file: `rowOffset`, `colOffset`

I'm closing this issue as done and released in Handsontable v12.1.3

`afterChange` doesn't fire if binded to component directly

Hi @zumm https://jsfiddle.net/t1x0z58f/1/ One small change the `:` instead of `@` in the hook declaration in the component's props.

`afterChange` doesn't fire if binded to component directly

I see what you mean, @zumm. [Here's an example](https://michaelnthiessen.com/pass-function-as-prop/) of what is often used as what should be. Currently, however, it's standardized for all of our wrappers.