Some errors with the material skin

Gantt
#1

Some errors with the material skin.
Sometimes a horizontal line appears when it scrolls vertically up the timeline.
The last line on the grid is not displayed.
The vertical line on the right side of the grid should go to the end of the gantt, but finish before;

In addition, the timeline could be completely filled by cells until it touches the bottom line of the gantt. Currently if you have 3 tasks, there is an empty white part in the timeline and this is not aesthetically good.

#2

Not sure if this is referring to the same issue.

In 6.1.7, there’s a line at the bottom of the grid.

image

In 6.2.0, there’s no line.

image
image734×394 18.4 KB

#3

This error happens when using smart_rendering, in version 6.2 comes by default.

#4

Hello everyone.
Thank you for reporting about the issue.
Yes, it happens because of the smart rendering. I added the bug in our internal tracker, and the dev team will fix it in the future. I cannot give you any ETA, but I will notify you when the issue is fixed.

Now, as a workaround, you can add the following style rules:

.gantt_data_area .gantt_task_row:last-child, .gantt_grid_data .gantt_row:last-child {
  border-bottom: none;
} 
    
.gantt_task_bg{
  border-bottom: 1px solid #d7d7d7;
}
  
.gantt_grid_data > div:last-child{
  width: 100% !important;
  visibility: visible !important;
  border-bottom: 1px solid #d7d7d7;  
}

The following snippet demonstrates how it works:
https://snippet.dhtmlx.com/f8ae16cc1

1 Like
#5

I also had to include the following code:

.gantt_row, .gantt_task_row{
    background-color:inherit !important;
}

For some reason the background-color: #FFF was hiding the bottom border. Now it’s ok.

#6

Hello Douglas,
Thank you for letting me know. I forwarded that information to the dev team, and they will check if it is required to include that to fix the issue or it happens because of something else.

1 Like
#7

Hello everyone.
The dev team fixed the bug with the bottom border in the material skin:
https://docs.dhtmlx.com/gantt/whatsnew.html#x8318x90x8319x

You can see that the bug is no longer reproduced in the following sample:
http://snippet.dhtmlx.com/5/87990b55c