Kendo timeline range in the gantt can be miscalculated if children have start and end days earlier that their parent.
This happens to due oversight in TimelineBaseViewService.getRange function. Two variables startResult and endResult are calculated using only top-level entities from the supplied data hierarchy.
This stackblitz shows 2 cases.
- The item is out of the bounds on the left due to an earlier start date than its parent's start date.
- The item is rendered either as three dots or out of bounds on the right side (depends on the browser. Firefox tend to display three dots, Chrome clips the right side) due to end date being later than its parent's end date.
That's mostly visible on Day and Week timelines, however I believe can be reproduced on monthly and yearly views if the date spread is large enough.
Hi Yanmario.
Thank you for the clarification.
If it's an intended behaviour, I would recommend explicitly stating this in the documentation (unless it already is).
Also, it means that with recently added drag&drop editing support whenever a parent is moved, the children have to be moved altogether. That might sound logical, but it can be easily overlooked. Even the example on the Angular Gantt Example from the official docs is affected by this constraint. If you move the first item "Software validation, research and implementation" to the right, it leads to the same issue of items being outside of the Gantt timeline range.
