For MCLs which are unlikely to have a Load more option, we could leave the minimum width unset to make the Coverage column shrink when empty. If this is done also for MCLs with a load more option then the column could resize each time "Load more" is selected.

Thats right Gill. We do not have a width set for the coverage column on that specific MCL, https://github.com/folio-org/ui-agreements/blob/master/src/components/EntitlementsAgreementsList/EntitlementAgreementsList.js#L42

Thanks for the update .So when the initial Coverage column width is calculated, if rows in the first batch have no coverage and the column width is set to its absolute minimum, when the user selects "Load more" it is not possible to recalculate the column width. This would make any coverage in the second batch of rows display poorly. Like you say, it wouldn't be good to have the columns resize each time the user loads more rows, especially if all columns were responding to content in the same way.

For info, the Coverage column in the MCL of agreements, displayed on the E-resource record, behaves similar to the way described in the issue. E.g. where the resource has no coverage the column is displayed at an absolute minimum:

With coverage the column width increases e.g.

Is this because the column has no minimum set, Adi?

IIRC, the decision was for us to find a correct min value to set for the coverage column. Reason being, we have scenarios where an MCL row might not have a coverage until very far down the list (eg: an MCL row that has a coverage only after clicking the load more). MCL cant measure data that isnt there, this mean the MCL needs to mesaure the column width `mid-scroll` (this capability isnt there in the MCL yet) and that means the columns would shift in size as you scrolled. So, I think finding that right min width is the immediate solution.

Hi . You spoke to John Coburn a while ago about this. Did anything come of it?