toStandaloneHtml renders empty cells when cellContentLimit = -1

Open Beginner friendly
#2,225 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
kotlin

Research direction

Start by tracing toStandaloneHtml with DisplayConfiguration(cellContentLimit = -1) and inspect how the limit affects generated table cell content. Use the reproducer to generate repro.html and check whether values appear in Chrome or Safari; done means the cells show their values without truncation.

Written by the indexing model from the issue text.

Description

Version: DataFrame 1.0.0-rc02

When I open the standalone HTML output generated with cellContentLimit = -1 in a browser, the table shows empty rows instead of cell values. This happens in both Chrome and Safari.

Expected behavior: cellContentLimit = -1 should disable content truncation without hiding cell values.

Image

Reproducer code:

import org.jetbrains.kotlinx.dataframe.api.dataFrameOf
import org.jetbrains.kotlinx.dataframe.io.DisplayConfiguration
import org.jetbrains.kotlinx.dataframe.io.toStandaloneHtml

fun main() {
    dataFrameOf("a", "b", "c", "d", "e")(
        "a", "b", "c", "d", "e",
        "f", "g", "h", "i", "j",
        "k", "l", "m", "n", "o",
        "p", "q", "r", "s", "t",
        "u", "v", "w", "x", "y",
        "aa", "bb", "cc", "dd", "ee",
        "ff", "gg", "hh", "ii", "jj",
        "kk", "ll", "mm", "nn", "oo",
        "pp", "qq", "rr", "ss", "tt",
        "uu", "vv", "ww", "xx", "yy"
    )
        .toStandaloneHtml(DisplayConfiguration(cellContentLimit = -1))
        .writeHtml("repro.html")
}
Dominant language
Kotlin
Stars
1.1k
Forks
87
Avg merge
2d 21h
Merged PRs (30d)
40

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

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 Kotlin/dataframe

All issues in Kotlin/dataframe

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.