You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After updating the library from version 26 to 27 I noticed that my tasks are no longer centered in the date box.
I used to achieve that by setting the time of the date to 12:00, but that no longer works, the task is always at the start of the date.
I found some potential leads - Time is ignored only when [dayWorkingTime]="[{ from: 0, to: 24 }]" is set, and only if the date is in standard time
Without [dayWorkingTime]="[{ from: 0, to: 24 }]"
With [dayWorkingTime]="[{ from: 0, to: 24 }]"
Maybe I'm using the dayWorkingTime wrong, if I set "from" to be equal to 1, it works, but because it is only breaking for the standard time, it leads me to believe it is some kind of an issue.
The text was updated successfully, but these errors were encountered:
We were able to replicate the reported issue where the milestone position does not render correctly when using the dayWorkingTime property in the Gantt chart. This issue occurs in Gantt chart version 28.2.6.
We have identified that this issue has been fixed in the latest version of the Gantt chart. We recommend upgrading to version 28.2.7 to resolve the problem. We have attached a sample for your reference.
After updating the library from version 26 to 27 I noticed that my tasks are no longer centered in the date box.
I used to achieve that by setting the time of the date to 12:00, but that no longer works, the task is always at the start of the date.
I found some potential leads - Time is ignored only when
[dayWorkingTime]="[{ from: 0, to: 24 }]"
is set, and only if the date is in standard timeWithout
[dayWorkingTime]="[{ from: 0, to: 24 }]"
With
[dayWorkingTime]="[{ from: 0, to: 24 }]"
Maybe I'm using the dayWorkingTime wrong, if I set "from" to be equal to 1, it works, but because it is only breaking for the standard time, it leads me to believe it is some kind of an issue.
The text was updated successfully, but these errors were encountered: