@Saki thanks for the update. We are currently in final test phase before a go live and this issue clearly is blocking the go-life. Do you have a rough idea on when to expect a fix release for this? Just so that we can make some plans.
Second thing is you postet our reproduction on github, including our .npmrc file that contains our product token. Can you please remove that .npmrc from the zip file so that our token is not exposed to the world wide web? Thanks in advance.
i reported the bug beginning of february and was told it should be fixed within 2-3 weeks. Now we have april.. and the ticket is not even started! Its a big, big, big issue!! It's a big issue in production. When it can be expected to be fixed? This issue influences a lot of other issues we also experience with bryntum, where we also created bugs for. But none of them are in progress. We use Bryntum Grid on a very basic level, but Bryntum Grid is on a high level buggy and it does not seem that reported bugs get fixed in any near future. It's nearly unusable. At the moment we strongly regret that we payed for bryntum. It does not seem to be worth the money. If there will be no progress at all we will need to say good by to bryntum to get our product running.
