[ANSWERED] Javascript error when adding filter to schedule with scroll

[kerstin]

Hi,

We have a problem using the scheduler with filter option. I can reproduce the error in your bigdataset example like this:

1. Add feature filterBar: true

2. Open the example, scroll down to show row 298

3. In surname filter, type "ck"

4. Javascript error "Cannot read property 'id' of undefined" at HorizontalEventMapper.matchRowTranslation

[johan.isaksson]

Hi,

Reproduced, created a ticket to track the issue here: https://app.assembla.com/spaces/bryntum/tickets/7672

[johan.isaksson]

Hi,

This issue has been fixed in our sources. The behaviour when applying filters has changed, it will now always return to the top

[Luffy]

Hi,

Below error is occurred while scrolling my project which is using drag drop tasks between different scheduler instances.
I have no idea what is the reason for this and this error is giving very rarely.

Do you have any idea why this happens ?

bryntum version 2.2.5

console_err.png (31.06 KiB) Viewed 2835 times

[mats]

Try upgrading to latest 3.x version, most likely it's fixed there.

[Luffy]

Hi,

As you told updated to the latest version on 3.0.1.
Now that console error comes more often.

This happens after refreshed the app and scroll the below scheduler.

console_err.png (60.51 KiB) Viewed 2829 times

[mats]

Can you reproduce it in our samples? How do we reproduce it?

[daansatortec]

We also still encounter this bug. Can easily be reproduced:

* Enable sorting on resources.
* Have a sufficiently large number of resources such rows can be scrolled out of view (and are reused for other resources).
* Scroll all the way down.
* Enable a filter.

I modified the big data example slightly to have the option to enable filtering. You can find the code here: https://pastebin.com/bwXiWDyD

A video that shows how to reproduce the error is attached.

Hopefully the issue can be resolved a.s.a.p. as our customers are experiencing problems with our application due to this issue.

[Animal]

Thanks for the comprehensive reproduce info. I have created a ticket for this and it will be fixed in the next release.

https://github.com/bryntum/support/issues/401

[daansatortec]

it will be fixed in the next release

I just saw the new 3.1.0 release came out. But the changelog doesn't mention the fix, while the ticket says it is resolved. So, does the new release contain the fix?