use new report api in viewer

[connorjclark]

currently getting our own warning thrown at us in console

Please adopt the new report API in renderer/api.js.

[adamraine]

The report api does not support everything in ViewUIFeatures. We will probably need to add the saveGist and refresh callbacks to the base ui features.

[connorjclark]

ViewerUIFeatures extends from the base report features class and we don't really need to modify that.

this issue is just about switching to the new DOM constructor and changing whatever breaks from that

[adamraine]

this issue is just about switching to the new DOM constructor and changing whatever breaks from that

The warning message is talking about using the API in renderer/api.js, something that is not used in the viewer app and would not change with #15964.

I understand the warning condition looks for this._dom.rootEl, but I think that's because rootEl was introduced for the new API (#13277)

[connorjclark]

Just want to get rid of this console warning in the viewer. I don't think it's worth doing more here, but technically there is more to be done.

[adamraine]

If using the new report API is not a priority and the console warning is just noise at this point, then we should just delete the warning message and track migration to the new API here. #15964 neutralizes the warning but it doesn't actually adopt the new API so I don't think #15964 should close this issue.

[connorjclark]

It's still of relevance to external people using our report renderer. We just don't expect them to need all the things the viewer does.