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
if I grab the drag handler between TOC and content parts to get some space for the content itself w/o the need to scroll horizontally, the handler sticks to the mouse and can no longer be released: click, dblclick, esc -- all do nothing.
That's on Chrome 95 for Win10 with a vanilla mouse.
I have to reload the page and face a screen-estate wasting TOC panel and scroll the content part. Yes, I don't have a HD monitor :-)
May I suggest to reduce the overall width of the left TOC anyway? It's way to large for the short lines present in the TOC wasting alot of horizontal space.
Thanks.
The text was updated successfully, but these errors were encountered:
/* the container which oddly enough has no id nor is it <main> */div.flex {
--toc:20vw;
--gap:10px;
}
.gutter-horizontal {
flex-basis:calc(var(--gap) *2)
}
#split-left {
flex-basis:calc(var(--toc) -var(--gap))
}
#split-right {
flex-basis:calc(100vw-var(--toc) -var(--gap))
}
then your slit-dragging script could just change the --toc variable and let the browser do its job.
The documentation is generated by documentation.js so that's probably the place to raise this. I'd accept a PR that does some post-generation hackery to implement the above though.
Hello,
if I grab the drag handler between TOC and content parts to get some space for the content itself w/o the need to scroll horizontally, the handler sticks to the mouse and can no longer be released: click, dblclick, esc -- all do nothing.
That's on Chrome 95 for Win10 with a vanilla mouse.
I have to reload the page and face a screen-estate wasting TOC panel and scroll the content part. Yes, I don't have a HD monitor :-)
May I suggest to reduce the overall width of the left TOC anyway? It's way to large for the short lines present in the TOC wasting alot of horizontal space.
Thanks.
The text was updated successfully, but these errors were encountered: