htcnokia opened a new issue, #43084:
URL: https://github.com/apache/superset/issues/43084
### Bug description
### Environment
- Apache Superset version: 6.1.0
- Chart Type: Pivot Table (v2)
### Summary
This issue addresses two key rendering and usability concerns in the Pivot
Table visualization:
1. [Bug] Conditional formatting renders inconsistent or abnormal background
colors within the same column.
2. [Feature Request] Need for text truncation (ellipsis) support on Row
dimension fields with long text.
---
### Issue 1: Conditional Formatting Anomaly in Same Column (Bug)
* **Description**: When applying conditional formatting rules (e.g., color
scales or threshold ranges) to a metric column in a Pivot Table, the rendered
background colors across cells within the same column are occasionally
inconsistent or abnormal relative to their numeric values.
* **Expected Behavior**: Color scales should linearly reflect the cell
values relative to the rest of the column based on the set rule.
* **Actual Behavior**: Certain cells display background colors that do not
align with their relative value ordering (e.g., a smaller value receiving a
darker background than a larger value).
---
### Issue 2: Support Text Truncation for Row Dimension Fields (Feature
Request)
* **Description**: When row dimension fields contain long string values, the
table column stretches excessively, causing visual clutter, poor readability,
and unnecessary horizontal scrolling.
* **Proposed Solution**:
- Add a chart control setting to truncate long text in Row labels using an
ellipsis (...), with a configurable max-width or character limit.
- Provide a hover tooltip displaying the full unabbreviated text when a
row label is truncated.
---
### Steps to Reproduce
1. Create a Pivot Table (v2) chart in Superset 6.1.0 using a dataset with
long text row dimension values.
2. Apply Conditional Formatting to a metric column.
3. Observe that conditional colors do not map strictly to value magnitudes
in the column, and long row labels expand the table without truncation.**
* **Standard Format**: Structured according to standard open-source GitHub
Issue guidelines, clearly separating the bug report from the feature request
with reproduction steps.
* **Terminology Alignment**: Uses official Superset chart terms (*Pivot
Table v2*, *Row Dimensions*, *Conditional Formatting*) to ensure project
maintainers can quickly triage the issue.
* **GitHub Tip**: If the maintainers request separate submissions, you can
easily split this draft into two distinct posts—one under the Bug template and
one under the Feature Request template.
### Screenshots/recordings
<img width="520" height="509" alt="Image"
src="https://github.com/user-attachments/assets/8f25d64c-5f3d-443e-8c32-aa34e8a5f661";
/>
### Superset version
master / latest-dev
### Python version
3.11
### Node version
16
### Browser
Chrome
### Additional context
_No response_
### Checklist
- [ ] I have searched Superset docs and Slack and didn't find a solution to
my problem.
- [ ] I have searched the GitHub issue tracker and didn't find a similar bug
report.
- [ ] I have checked Superset's logs for errors and if I found a relevant
Python stacktrace, I included it here as text in the "additional context"
section.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
