The holds awaiting pickup report should not be fixed-width. The table can be very wide, especially with the width of "Cancel and return to..." buttons with long branch names.
Created attachment 69510 [details] [review] Bug 19751: Holds awaiting pickup report should not be fixed-width This patch changes the grid used for the holds awaiting pickup report so that the results are full page and fluid instead of fixed-width. To test, apply this patch and the patch for Bug 19700 if necessary. View the holds awaiting pickup report. The report should fluidly fill the page width. Test with the CircSidebar system preference enabled and disabled.
Patch tested with a sandbox, by George Williams <george@nekls.org>
Created attachment 69512 [details] [review] Bug 19751: Holds awaiting pickup report should not be fixed-width This patch changes the grid used for the holds awaiting pickup report so that the results are full page and fluid instead of fixed-width. To test, apply this patch and the patch for Bug 19700 if necessary. View the holds awaiting pickup report. The report should fluidly fill the page width. Test with the CircSidebar system preference enabled and disabled. Signed-off-by: George Williams <george@nekls.org> Signed-off-by: BWS Sandboxes <ByWaterSandboxes@gmail.com>
Created attachment 69600 [details] [review] Bug 19751: Holds awaiting pickup report should not be fixed-width This patch changes the grid used for the holds awaiting pickup report so that the results are full page and fluid instead of fixed-width. To test, apply this patch and the patch for Bug 19700 if necessary. View the holds awaiting pickup report. The report should fluidly fill the page width. Test with the CircSidebar system preference enabled and disabled. Signed-off-by: George Williams <george@nekls.org> Signed-off-by: BWS Sandboxes <ByWaterSandboxes@gmail.com> Signed-off-by: Josef Moravec <josef.moravec@gmail.com>
Pushed to master for 18.05, thanks to everybody involved!
Pushed to stable for 17.11.01, awesome work all!
Pushed to 17.05.x, will be in v17.05.07 This looks more bug than enhancement.