Visual Debugging Techniques for Reactive Data Visualization
Abstract
Interaction is critical to effective visualization, but can be difficult to author and debug due to dependencies among input events, program state, and visual output. Recent advances leverage reactive semantics to support declarative design and avoid the “spaghetti code” of imperative event handlers. While reactive programming improves many aspects of development, textual specifications still fail to convey the complex runtime dynamics. In response, we contribute a set of visual debugging techniques to reveal the runtime behavior of reactive visualizations. A timeline view records input events and dynamic variable updates, allowing designers to replay and inspect the propagation of values step‐by‐step. On‐demand annotations overlay the output visualization to expose relevant state and scale mappings in‐situ. Dynamic tables visualize how backing datasets change over time. To evaluate the effectiveness of these techniques, we study how first‐time Vega users debug interactions in faulty, unfamiliar specifications; with no prior knowledge, participants were able to accurately trace errors through the specification.
Integrity signals
Registry
Cites
Statistics
Claims the paper makes
Claims other papers make about this one
Each is checked against this paper’s own text: does it say what the citing paper says it does?
Making a system seamless for someone inevitably makes it frictional for someone else [19].
“However, making a system seamless for someone inevitably makes it frictional for someone else [19].”
From Considering Visualization Example Galleries (2024) · cites this paper as [19]
Cited by
Sorted by citations
Considering Visualization Example Galleries
Yang, J., McNutt, A. M., & Battle, L. (2024) · 2024 IEEE Symposium on Visual Languages and Human-Centric Computing (VL/HCC) · doi:10.1109/vl/hcc60511.2024.00043 · Cited by 5 · see citing works
“L ITE editor [59] includes specialized affordances for those libraries, such as debugging [20] and performance [64] tools.”
Background
- Authors
- Hoffswell, J., Satyanarayan, A., & Heer, J.
- Affiliations
- University of Washington (US)
- Stanford University (US)
- Venue
- Computer Graphics Forum
- Publisher
- Wiley
- Published
- 2016-06
- Volume
- 35
- Issue
- 3
- Pages
- 271-280
- ISSN
- 0167-7055 (ISSN-L)
- 1467-8659
- OpenAlex
- W2469097875
- Cited by
- 24
- References
- 0
- Citations by year
- 2026: 1 · 2025: 2 · 2024: 3 · 2023: 2 · 2022: 2 · 2021: 3 · 2020: 4 · 2019: 2 · 2018: 2 · 2017: 3
- FWCI
- 1.58
- Type
- journal article
- Language
- en
- Open access
- closed
- Locations
- Computer Graphics Forum (publishedVersion)
- Topics
- Physical Sciences › Computer Science › Computer Vision and Pattern Recognition › Data Visualization and Analytics
- Physical Sciences › Computer Science › Computer Graphics and Computer-Aided Design › Computer Graphics and Visualization Techniques
- Physical Sciences › Computer Science › Software › Software Testing and Debugging Techniques
- Keywords
- visual debugging, reactive programming, data visualization, Vega, dynamic tables, runtime behavior, error tracing
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review