Inconsistent rendering of Great tables in dark mode.

Open
#11,554 5 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@Garcia-786 is already working on this.

Since Nov 1, 2026.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
html, python
Domain
frontend

Research direction

Start by running the provided reproduction with Great Tables in dark mode, then compare the direct cell output with the mo.as_html(tbl) output embedded in mo.md. The issue names no source files or tests, so trace how those two rendering paths handle the table; done means the table renders consistently in both cases.

Written by the indexing model from the issue text.

Description

bug upstream
Describe the bug

Hi.

I Am observing inconsistent rendering of Great Tables depending on how it is rendered in dark mode of marimo notebook.

There might be an issue with great tables utilizing transparency, however, I am not able to understand why this inconsistency might occur and if it is a bug. Is marimo's interactivity of the table something that might interfere in this case?

As a code cell's output (Correct rendering)

Image

Transparent background when using mo.Html within mo.md.

Image

Thank you for the great work!

Will you submit a PR?
  • Yes
Environment
Environment
{
  "marimo": "0.25.2",
  "editable": false,
  "location": "/usr/local/lib/python3.13/site-packages/marimo",
  "OS": "Linux",
  "OS Version": "4.19.0-gvisor",
  "Processor": "",
  "Python Version": "3.13.11",
  "Locale": "C",
  "Binaries": {
    "Browser": "Mozilla/5.0 (X11; Linux x86_64; rv:158.0) Gecko/20100101 Firefox/158.0",
    "Node": "v22.23.4",
    "uv": "0.12.1 (x86_64-unknown-linux-gnu)"
  },
  "Dependencies": {
    "click": "8.5.0",
    "docutils": "0.23",
    "itsdangerous": "2.2.0",
    "jedi": "0.19.2",
    "markdown": "3.10.2",
    "narwhals": "2.24.0",
    "packaging": "26.3",
    "psutil": "7.2.2",
    "pygments": "2.20.0",
    "pymdown-extensions": "10.21.3",
    "pyyaml": "6.0.3",
    "starlette": "1.3.1",
    "tomlkit": "0.15.1",
    "typing-extensions": "4.16.0",
    "uvicorn": "0.51.0",
    "websockets": "17.4"
  },
  "Optional Dependencies": {
    "altair": "6.2.2",
    "anywidget": "0.11.0",
    "duckdb": "1.5.4",
    "loro": "1.13.1",
    "nbformat": "5.10.4",
    "openai": "3.19.1",
    "pandas": "3.0.3",
    "polars": "1.42.1",
    "pyarrow": "25.0.0",
    "pytest": "9.1.1",
    "python-lsp-ruff": "2.3.1",
    "python-lsp-server": "1.14.0",
    "ruff": "0.15.22",
    "sqlglot": "30.12.0",
    "ty": "0.0.61",
    "vegafusion": "2.0.3"
  },
  "Experimental Flags": {}
}
Code to reproduce
Code
# /// script
# requires-python = ">=3.13"
# dependencies = [
#     "great-tables==1.1.0",
# ]
# ///

import marimo

__generated_with = "0.25.2"
app = marimo.App(width="medium", auto_download=["html"])


@app.cell
def _():
    import marimo as mo
    import polars as pl
    from great_tables import exibble, GT
    tbl = GT(exibble)
    return mo, tbl


@app.cell
def _(tbl):
    tbl
    return


@app.cell
def _(mo, tbl):
    mo.md(f"In markdown as f-string {mo.as_html(tbl)} ")
    return


if __name__ == "__main__":
    app.run()

Dominant language
Python
Stars
22.9k
Forks
1.3k
Avg merge
1d 10h
Merged PRs (30d)
380

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from marimo-team/marimo

All issues in marimo-team/marimo

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.