[ANGULAR] Preserving vertical scroll position when changing allocation

[korneld]

Hi all,

We’re encountering an issue where, when users attempt to reallocate a task, the scroll position is not preserved. As a result, the user's focus is lost from the resource to which the task was allocated.

I’ve created a demo project and recorded two videos to illustrate the behavior:

1. The user changes the resource from 1 to 7 — the scroll position shifts, and the user loses context.

2. The user changes the resource from 1 to 12 — the scroll position is preserved.

Is there a way we can improve the scroll behaviour ? Specifically, what would it mean - to consistently preserve the scroll position across different contexts?

In the attachment, videos and running angular project. View port: 1200x550.

[alex.l]

Hi,

What is going on on the video? What buttons you pressed? Please provide steps to reproduce this? Did you use inbox features for that or something manually written?

[marcio]

Hey korneld,

Thanks for reaching out and for the demo.

I tried to reproduce the behavior on the videos you attached, but all worked as expected. Could you please confirm that I'm trying to reproduce this correctly? Also, could you clear the npm cache just to make sure you're using the latest version of library?

[korneld]

Sorry for not explaining earlier how I'm changing the allocation — I assumed the video and code would make that clear.

Here are the steps:

1. The user clicks on a task assigned to resource 2.

2. When the task is clicked, I use the resource time ranges feature to render a red lane (we call this the allocation lane). In the real system, the allocation lane has different colors to help users make better decisions. For demo purposes, I’m using only a red lane.

3. Then, I scroll down to resource 7.

4. I click on the red lane for resource 7. When this happens, I change the task's allocation from resource 2 to resource 7.

Please note that resource 7 is not fully visible, and also consider the window size. I’ve attached both a video and a screenshot showing the window dimensions for reference.

Let me know if you need more info.

[korneld]

Hey,

Let me know if the repro steps make sense and if you’re able to reproduce the issue.

Cheers,
KD

[alex.l]

Hi,

Thank you for clarification! I've opened a ticket for that. I don't see such problem in vanilla, so I guess it's Angular/wrapper related issue we need to fix https://github.com/bryntum/support/issues/11180
You can subscribe on ticket updates to be notified when it's done.

[biernati]

Hello Bryntum, do you have any dates when you are going to work on this bug? It's been opened well over a month ago and we would like to understand when we can expect a resolution?
Thanks
Michal

[ghulam.ghous]

Hey Michal,

We have marked the ticket as high prio and it will be fixed soon. High prio tickets usually takes upto 2 to 3 weeks usually. Please subscribe to the ticket to keep track of updates.

[biernati]

Hello, I still see no updates on this ticket - it's been another month and still no one has been assigned to work it...

[ghulam.ghous]

Hi,

Unfortunately we were not able to get back to it. We will try to check this soon. You can subscribe to the ticket for the updates.