[Feature]: Horizontally scrollable output in revealjs

[ute]

Feature Description

When rendering to html, long lines of output don't get wrapped in output windows that are too small to hold them, but can be scrolled horizontally. I think this is a cool feature! 😎
It does not work on revealjs - is this on purpose? Lines get wrapped instead, and this may look somewhat funny.

Update1: I understand it is probably intended because ordinary quarto code cells behave similarly, and maybe presenters do not want to fiddle on their slides but have the whole outcome exposed to the audience.

Update2: Lines that have to be wrapped horizontally can most often be avoided by setting the width option in R.

It could thus be an extra feature:
A tiny change in qwebr-compute-engine.js, line 127 can give horizontal scrolling as in html: returning a <code> element with a simple <span> - this did the job for me.

Sorry I am pestering you with features (procrastinating urgent tasks...) - thank you for your fantastic work 😃

(I am not suggesting to make wraptag a code cell option. If there were such an option, it should be boolean. This was just a quick and dirty solution)

Here is what it looks like as html:

[coatless]

Sorry I am pestering you with features (procrastinating urgent tasks...) - thank you for your fantastic work 😃

@ute no worries; but, I would encourage you to knock out those tasks so we could have more focused design time 😃

A tiny change in qwebr-compute-engine.js, line 127 can give horizontal scrolling as in html: returning a <code> element with a simple <span> - this did the job for me.

On the span tag, I think we can address this without changing the output structure; but, instead, change the CSS being applied. In the early days, this was a concern of a few so we opted to have everything displayed instead of trying to mirror the R output style; but, with the work in font-sizes and other advances, I think that'll work out nicely.

[coatless]

So, I thought about this a bit more... I think the issue here will be resolved better if we change the option(width=) value away from the default of 80.

Default 90 width

cat("Default spacing: ", getOption("width"), fill = TRUE)

a <- 1 + 1
rep(a, 100)

Custom 78 width

options(width=78)
cat("Custom spacing: ", getOption("width"), fill = TRUE)

a <- 1 + 1
rep(a, 100)

Proposed step

So, if during webR's initialization, what if we set the width option to 78? I think this would give a better resolution potentially.

Thoughts?