How to add scroll to a text widget?

I am using a text widget that receives some input (actually command outputs) from another system. How can I add scrolling when the number of lines is too big?

The text widget is not multiline scrollable, for now the best solution is to use a html widget, here is a small example session: html_log.json (2.3 KB) (see osc listeners for how to feed the html with osc messages)

I can’t get this to work.

Either I get undefined or the html content
The html content is now ‘OSC{reply}’

I also tried only OSC{} and then /reply in the address
I also tried only OSC{’/reply’} and then nothing (auto) in the address
sometime U get:
(ERROR, CLIENT) Uncaught NotFoundError: Failed to execute ‘removeChild’ on ‘Node’: The node to be removed is no longer a child of this node. Perhaps it was moved in a ‘blur’ event handler?
at nanomorph (node_modules/nanomorph/index.js:1:0)

Richard

The OSC{} syntax does not expect enquoted strings, try this: OSC{/reply} (or OSC{/reply, } to avoid the undefined default value).

It sort of works now (my fault), but the scrolling does not work.
It did work with the fixed text.
BTW, I have the OSC{/reply} now between ‘pre’ and ‘/pre’ tags
See attached image the bottom element is the html

Screenshot from 2020-07-09 17-13-57

Did you set the css property like in the example, that’s what enables scrolling.

I did now, but it does not make a difference…

Does it scroll in the session file attached above ?

Yes, with the fixed text it scrolls.

Could you please upload your session file here ?

Yes, here it is…test.json (6.0 KB)

Looks like a copy-paste issue is breaking the html’s css property, removing the \n will fix it.

I do not understand. The \n in the css property? I removed both, to no avail.
It gives a scroll bar that is maximized, so I cannot scroll
I also removed the last character (\n) from the reply coming from Python, no difference.

I do not understand. The \n in the css property? I removed both, to no avail.

There were 4 "\n" occurences in the css property, removing all of them did fix it here.

Indeed! That was it. Thanks!