You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can see benefits to matching the nbviewer rendering as closely as possible to what an author sees in the notebook editing environment. I can also see people used to the current behavior being surprised if it changes suddenly. At any rate, I think the change would need to be proposed and discussed in the nbconvert repo to affect nbviewer. GitHub's implementation is private and may or may not be impacted by changes in nbviewer.
The only workaround I can think of in the meantime is to include a cell in your notebook like:
%%html
<style>
.nbviewer div.output_area {
overflow-y: auto;
max-height: 500px; /* or value of your choosing */
}
</style>
to make all outputs past a certain length scrollable.
I am checking in notebooks that show output scrolling in windows. On GitHub and in nbviewer, the scrollable windows are lost.
For example, this has scrollable windows in Jupyter, but not in nbviewer.
https://github.com/biblicalhumanities/greek-new-testament/blob/master/labnotes/dative-direct-objects.ipynb
http://nbviewer.jupyter.org/github/biblicalhumanities/greek-new-testament/blob/master/labnotes/dative-direct-objects.ipynb
I can fix this by converting to HTML and modifying the CSS for div.output_area, but I would love it if this would Just Work. Any suggestions?
The text was updated successfully, but these errors were encountered: