Hi @Kaniz Fatma​ ,

thanks for showing me the link. This helps if you are in control of the generated html-object. If the html-content comes from a library, that is where the problems start, because I cannot wrap displayHTML().

(I can of course look for that line and rebuild my own databricks-compatible version of the lib, but this would be improvisation, not solving the issue)

I am just worried that the number of python libraries will increase that use html-objects deep down. Surely there can be a way to capture this in the stack and handle it better than enforcing a call on another display method. I am sure this needs to be coordinated with the frontend developers of the databricks UI and the backend devs doing the Python-engine.

Is it possible to add such a configuration for a specific function of a library instead?

https://github.com/databrickslabs/jupyterlab-integration/blob/753882c37ead89013f302863d1548eef27e0ba...