Horizontal and vertical lines appear in merged Spreadsheet cells that are disabled

[PekoPPT]

Bug report

Horizontal and vertical lines appear in the merged Spreadsheet cells when they are disabled.

** Possible workaround could be to apply the following CSS:

      #spreadsheet > div.k-spreadsheet-view > div.k-spreadsheet-fixed-container > div.k-spreadsheet-pane > div.k-spreadsheet-data > div.k-state-disabled {
        opacity: 1;
        color: #a3a3a3;
      }

Reproduction of the problem

1. Open this Dojo and run it
2. There are is a horizontal line above the cell with text "Merged DISABLED cell and there is a horizontal line above". There is a vertical line inside the cell with text "Two cells are merged horizontally and the result cell is disabled. There is a vertical line that should not appear"

Current behavior

When Spreadsheet cells are merged and the result cell is disabled, there are horizontal or vertical lines that appear inside the merged cell.

Expected/desired behavior

No lines should appear inside the merged cells, no matter if they are enabled or disabled.

Environment

• Kendo UI version: 2020.3.1021
• jQuery version: x.y
• Browser: [all]

[veselints]

I have tried the following two approaches, with no success:

• Setting opacity: 1 on the .k-spreadsheet-cell.k-state-disabled and setting opacity: 0.6 on the inner text container. That would not result in opacity being applied to the background of the cell;
• Using a pseudo :after element to overlay the .k-spreadsheet-cell.k-state-disabled. However, the cell comment element (the red triangle in the upper right corner) is also a pseudo :after element on the cell. Hence, the styles of the overlay element will mix with the styles for the comment.

[martintabakov]

Also reported in #1557769

[jhsct]

This does not appear to be resolved yet. Is there an expected date of implementation?

[veselints]

The fix is yet not scheduled for implementation. That is why I could not provide an estimate of when it will be available. Nevertheless, I have just raised the priority of this item, so that it moves sooner in our implementation queue.