Grid Header Alignment with Percent

I thought this was posted before, but if so I am not searching for it correctly, so asking. (And apologies if this is a duplicate.)

When when using percent for column widths in a grid do the headers not align with the data when a scroll bar is present. (I believe the documentation also states performance is better when percent over pixels.) They align perfectly when there is no scroll bar, but each field appears slightly more off with each column.

The picture shows the alignment being off (pink lines) in the top part, while they are correct for the same grid when there is not scroll bar.

Any suggestions?

MBPM 9.2.1.0

Find more posts tagged with

BPM

Comments

Daniel_Michael

I sent a reply in the ticket, but for anyone else who might run into this issue. It looks like it's resolved in IE by using the compatibility view settings.

You'll probably want to clear your cache and do an iisreset as well. I had run into an issue where I hadn't done either and the compat view settings didn't appear to change anything until an f5, and I had cleared my sessions and tried in private browsing.

Brian Mellert

However, as I replied in the ticket, we have compatibility mode set for all of our BPM sites. While it seemed to have worked for the simple grid you sent to me, it didn't work with a normal/editable grid. (No idea if the editable capability made a difference.)

Nils Wyldbore

Have you tried anchoring your grid to top, left, bottom, right? I've found that makes the form auto-refresh and resize the columns correctly.

There is also the UseQuickResize web.config setting, which when set to 1 does not help the formatting of grid columns.

Brian Mellert

Yes, the grids are anchored to all 4 sides as I want the fields to use as much real estate as is available. That is the reason to use percent in my opinion, otherwise it wouldn't matter as much.

Out UseQuickResize is not set intentionally since "Set "UseQuickResize" to "1" to use a less accurate but faster form resize". Accuracy is the key to end users. We had it set at one point because performance was very poor on IE7/V9.1, but performance appears resolved on V9.2.1/IE8-9.