.save gives a very large picture with table only taking up a small fraction

[thomasfrederikhoeck]

Prework

• Read and agree to the code of conduct and contributing guidelines.
• If there is already a relevant issue, whether open or closed, comment on the existing thread instead of posting a new issue.

Description

.save gives a very large picture with table only taking up a small fraction

Reproducible example

• Post a minimal reproducible example (MRE) so the maintainer can troubleshoot the problems you identify. A reproducible example is:
  • Runnable: post enough code and data so any onlooker can create the error on their own computer.
  • Minimal: reduce runtime wherever possible and remove complicated details that are irrelevant to the issue at hand.
  • Readable: format your code according to the Style Guide for Python Code.

When I run the following:

import polars as pl
from great_tables import GT

df = pl.DataFrame({"My very nice column":[1,2,4],"My other very nice column": [3,4,5]})
GT(df).save("plot.png")

it produces this image (notice all the whitespace).

Expected result

I would have exected the resulting image to be "zoomed" in (no whitespace).

Development environment

• Operating System: [e.g., Linux, macOS, Windows]
• great_tables Version: 0.1.13
• Windows
• selenium 4.26.1

Additional context

Add any other context about the problem here.

[machow]

Shoot, sorry this isn't capturing just the table. What browser and browser version are you using? There's some funkiness with how browsers reckon the size of the table that we try to work around :/.

[ritviksahajpal]

I have the same issue, I am using the latest Chrome version (130.0.6723.117). Related, is there a way to set the DPI of the image saved when using GT.save()? thanks for a great package btw!

[ritviksahajpal]

Getting the same error with edge as well

[thomasfrederikhoeck]

@machow weirdly , I don't see the error anymore :-) I'm using Chrome 130.0.6723.117 (64-bit) on Windows.

[HagaiHargil]

Hi, any updates on this? I also mentioned it in #424, at least for me this issue is still relevant.

Do you need further data? I just tested it on a fresh GT install with one of the examples from the Examples pages, and I received that same huge image when using .save().