GitHub user innovark37 created a discussion: Conditional formatting logic - Why do empty cells get max-opacity color?
### Description Empty/null cells are being highlighted with FULL color intensity when they technically shouldn't match the comparison logic. ### Here's what happens: - Set up: value < 10 with "warning" color scheme - Result: Cells with value 5 → subtle warning color ✅ - Also: Empty cells → BRIGHT warning color ❓ The empties end up visually dominating the table, pulling attention away from actual data points that genuinely satisfy the condition. There seems to be a mismatch between: 1. Visual treatment (full opacity, strong color) 2. Logical meaning (does `NULL < 10` actually make sense?) Current visual weight: 🟡 Empty cells - Full opacity, bright colors (most noticeable) 🟠 Matching values - Lower opacity, subtle highlighting (less noticeable) ⚪ Normal cells - No highlight This inverts the visual priority - the least important cells (empties) become the most visually prominent. ### Proposal for Discussion Could we consider any of these approaches? **A. Fix the logic (recommended):** - `NULL < 10` → FALSE (no highlight) - Aligns with database semantics - Solves visual distraction **B. Fix the visuals (if logic is intentional):** - Empty highlights get different styling - Never use full opacity for uncertain matches - Clear visual distinction **C. Add clarity (minimum):** - Tooltip explaining why empty was highlighted - Documentation of this behavior - Option to toggle "include NULLs in comparisons" GitHub link: https://github.com/apache/superset/discussions/36812 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
