Issues with ListGrid headerSpan titles

[jfarmer]

While testing SmartClient “v11.0p_2016-09-07/PowerEdition Deployment” (using Chrome 53 and Internet Explorer 11) we found several issues with header spans.

For the following examples, see the provided JavaScript file (headerSpan-noWrap-autoSize-01.js). Using the Feature Explorer running the above SmartClient version, go to the “Grids > Appearance > Column order” page, paste the provided code in the “columnOrder.js” tab, then click the “Try it” button.
________________________
ISSUE #1:

On initial grid display, each headerSpan correctly shows the full, unwrapped title, and the columns in the span widen as necessary, but the grid Summary row and Body columns are misaligned from the grid header (see headerSpan-01.png).

________________________
ISSUE #2:

Calling ListGrid.autoFitFields() at any time (such as immediately after initial grid display) incorrectly horizontally truncates header span titles (see headerSpan-02.png), rather than auto-sizing them as on initial grid display, and incorrectly sets ListGrid.autoSizeHeaderSpans to false. We expect that after manual auto-fit the grid would appear exactly the same as on initial grid display. Note: This occurs whether or not any columns are frozen.

________________________
ISSUE #3:

Clicking “Cash Contrib per Region” column header to sort by the column shows the Ascending sort icon (see headerSpan-03.png). Note that the header height does not change with the addition of the Ascending sort icon.

Clicking the “Cash Contrib per Region” column header again, shows the Descending icon, but note that header height increases (see headerSpan-04.png). Click the “Cash Contrib per Region” column header again to sort Ascending, and the header height decreases. We expect the header height to be the same whether the “Cash Contrib per Region” column is sorted Ascending or Descending.

[Isomorphic]

Hi,
We just wanted to add a quick note to let you know this is being looked at but we don't yet have any information for you. As soon as we do we'll follow up with more detail here (likely tomorrow)

Regards
Isomorphic Software

[Isomorphic]

We've made a change to address the first issue here, which was a clear bug.
We believe the third issue is also resolved, but please let us know if you continue to see it.

These fixes should be present in the next nightly build, dated Sep 22 or above, in both the 11.0 and 11.1 branches.

The second issue is working as designed. ListGrid.autoFitFields() is a method to perform a one-time resize of every field to make it fit its title or contents (as if the user had drag-resized the headers). Doing this resets, or overrides autoSizeHeaderSpans - as it would if a user drag resized the headers.

Regards
Isomorphic Software

[jfarmer]

Thanks for addressing these issues. We are testing a recent nightly build to confirm the fixes.

In the meantime, regarding Issue #2 not being a bug, we respectfully disagree. Please consider the following simpler example of a ListGrid without headerSpans. For this example, see attached JavaScript file (header-noWrap-noClip-01.js). Using the Feature Explorer, go to the “Grids > Appearance > Column order” page, paste the provided code in the “columnOrder.js” tab, then click the “Try it” button.

On initial grid display, the column header titles are correctly not-wrapped and not-clipped (header-noWrap-noClip-01.png). Note that after manual Auto-Fit All, the header titles don't change -- they are still not-clipped horizontally. So when headerSpan titles are defined to be not-wrapped and not-clipped, we expect them to behave to a manual Auto-Fit All consistently with header titles (they should not be clipped either).

[Isomorphic]

We understand that this is your point of view, and you've expressed it previously, and we respectfully disagreed and we still respectfully disagree.

If you're looking for a different behavior here from what the framework provides, it could be added as another feature - something you call from a customized menu for example - but we will not be changing the default behavior, which we know for a certainty is what various other groups of end users actually want.