Inputs report web page has some errors

[hschilling]

Description

When viewing the inputs report HTML file, these errors are shown in the browser console log

inputs.html:8 Uncaught TypeError: Cannot read properties of null (reading 'offsetWidth')
    at r.elVisible (inputs.html:8:21787)
    at c.redraw (inputs.html:8:42038)
    at We.redraw (inputs.html:8:113572)
    at setup_tabulator (inputs.html:60:9)
    at inputs.html:63:17

Uncaught TypeError: cell.getData is not a function
    at columns.<computed>.tooltip (inputs.html:52:21)
    at Be.loadTooltip (inputs.html:8:380899)

Example

Run any OpenMDAO script that generates an inputs.html file and then open it in a browser. Open the Inspect tool in the browser and look at the Console.

OpenMDAO Version

3.30.1-dev

Relevant environment information

No response

[jsrogan]

I was reading up about the second issue listed (cell.getData is not a function), and found this:

https://stackoverflow.com/questions/69942537/tabulator-v5-tooltip-cell-getdata-is-not-a-function

While the issue described and the fix is slightly different, in the comments one of the tabulator developers mentions how tooltips have been completely overhauled in tabulator v5. I'm not sure which version we are using but if changes were made to tooltip and we were using a prior version and upgraded without adapting it could be why we are seeing this error now

EDIT: Want to take a deeper look at this issue, can anyone confirm an OpenMDAO script that generates an inputs.html file as the description suggests? want to read more about the issue

[coleyoung5]

I am working with jsrogan on this issue and I ran the paraboloid_min.py file in the "Getting Started" portion of the documentation which produced an inputs.html report. Under inspection of the Console when I look at this file in my browser, I see no errors listed, as can be seen in the attached screenshot. I was curious if my understanding of this issue is incorrect, and that I should be looking elsewhere in the Console to see these errors, or if the issue has already been resolved.