12.0p Bug with cut off data in ListGrid columns when using showRowNumbers: true

[Blama]

Hi Isomorphic,

trying to create a different testcase, I noticed this bug, where there are numbers being cut of in current v12.0p_2019-12-10:

isc.ListGrid.create({
    ID: "dsListGrid",
    width: "100%",
    height: "100%",
    autoFetchData: true,
    dataSource: "supplyItem",
    showRowNumbers: true
});

Best regards
Blama

[Isomorphic]

This should be resolved for SC 12.0p and newer branches in the nightly builds dated 2019-12-22 and beyond.

[Blama]

Hi Isomorphic,

I can see it is fixed in SNAPSHOT_v12.1d_2019-12-24, but there is no new 12.0p so far.

Best regards,
Blama

[Blama]

Hi Isomorphic,

I can see it is fixed in v12.0p_2020-01-04 as well.

Best regards,
Blama

[Blama]

Hi Isomorphic,

can you think of a reason that this still happens, but for date fields only?

I does happen for me in SmartGWT v12.0p_2020-03-11/PowerEdition, but not in the local run SmartClient showcase sample (http://localhost:8080/showcase/?id=fetchOperationFS) in the similar (2 days different) v12.0p_2020-03-13/PowerEdition version. This is the correct working sample:

isc.ListGrid.create({
    ID: "dsListGrid",
    width: "100%",
    height: "100%",
    autoFetchData: true,
    dataSource: "supplyItem",
    showRowNumbers: true,
    canRemoveRecords: true,
    minFieldWidth: 50,
    initialCriteria: {units: "Roll"},
    groupByField: "category",
    canEdit: true,
    //rowNumberFieldProperties: {width: 50, canDragResize: true, canGroupBy: true, showDefaultContextMenu: true},
    removeFieldProperties: {width: 50, canDragResize: true, canGroupBy: true, showDefaultContextMenu: true}
});

In my project, it's somehow related to showRowNumbers, but I can't put my finger to what exactly is causing this. I'm using SuperDevMode with my project and commented basically everything else out, that might interfere. Do you have any ideas or pointers?

Best regards
Blama

[Isomorphic]

We would guess that you have bad CSS in your project - probably setting left/right padding to different amounts on different cells, which can also be caused by only specifying padding values on some styles but not others. This causes the native rendering engine on some browsers to start cutting off values, because it gets confused by different CSS on different cells.

[Blama]

Hi Isomorphic,

thanks for the fast answer. I'll investigate in this direction now.

Best regards
Blama

[Blama]

Hi Isomorphic,

thanks, it is related to the last line here:

.specialCol,
.specialColOver,
.specialColSelected,
.specialColSelectedOver,
.specialColDisabled {
  background-color: #fafafa;
  color: #000000;
  line-height: 22px;
  padding: 0px; --this line
}

It seems it was added for some time in 2019 but then removed again.

Best regards
Blama