and persist that state in metadata.
When user toggles the scroll state,
the choice is remembered and persisted.
There are three states:
- 'auto' (default, only state in master)
- true (always scroll if above minimum_scroll_threshold)
- false (never scroll)
true or false is persisted in cell.metadata.scrolled.
"auto" may be persisted, but isn't currently because it's the default state.
No need to reload session (I doubt creating a new folder create a
session), and does it once the creation drive promise return which make
the new directory appear in the listing for slow remote-backend (like
google drive)
Mitigate 7486, could probably be improved, but
treat text as pure text, but assume that when received a dome
element it actually come from a secure source.
Sanitizing all we get, including Dom Element break json-metadata editor
and a few others.
fixes#7355
Also limit the number of query "jump", and use variables.
In particular there was a container width discontinuity at 768 pixel
where below 768 container width is 100% and "only" 720px on wider
screen, making a jump.
So now Css media query have 3 breakpoints:
- <540 px with (aka -no name-)
- colapsed menubar
- vbox for prompt
- 100% width container
- 540 -> 767 (aka -xs- )
- expand menubar
- hbox fro prompt
- 767 -> 991 (aka -sm-)
- show save widget
- fix width (768px)
- 991+ (aka -md-)
- extra save widget info (date time)
- fix with of 991 px.
- 1200+ (aka -lg-)
- widht of 1200px.
of course we've set soem variable wrongly so this is still kinda-a-hack
as we shoudl have pushed the xs-sm limit lower instead of pushing the
nothing-xs limit up but I don't want to "fix it" now.
Min RK
Brian E. Granger
Jonathan Frederic
Jessica B. Hamrick
Thomas Kluyver
Bussonnier Matthias
Jonathan Frederic
Juergen Hasch
Juergen Hasch