dump.measurementDisplayHistogram doesn't work

[tcNickolas]

Describe the bug I tried to use %config dump.measurementDisplayHistogram=true both for single-qubit and for multi-qubit systems.

• For single-qubit systems, in Firefox this doesn't do anything in addition to the regular DumpMachine output, in Edge see the next behavior.
• For multi-qubit systems (I tried with 2 qubits), this adds a display similar to that of %debug, but instead of being a fixed-size output, it grows uncontrollably to dozens of screen lengths, until I restart the kernel and clear the output.

To Reproduce Steps to reproduce the behavior:

1. I used Qubit and MultiQubitSystems tutorials, the first demos truncated to the first DumpMachine. I can repro this both on my machine and on the Katas' Binder.

Expected behavior A fixed-size window with a diagram similar to that printed by %debug.

Screenshots The top screen of the ever-growing display:

System information

• OS: Windows 10
• Browser: Firefox and Edge
• IQ# version: 0.17.2105.143879 (on Binder), 0.16.2104138035 (locally)

[cgranade]

I can confirm a local reproduction for this as well. Using web console to set a breakpoint on the canvas height changing, I can tell that it's chart.js that is resizing the chart as part of its scroll handler. Effectively, on scroll, chart.js seems to think it needs to grow the chart, which then causes another scroll, and so forth. Not sure of the root cause yet, tho.