-
Notifications
You must be signed in to change notification settings - Fork 315
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Custom scrollbar #3355
Comments
Adding as an issue for ease of finding in the future. (All PRs really should start from an issue, fwiw) |
The base CSS change has been applied and merged now. Making note of this exchange about having the scrollbar auto-hide, so it doesn't get lost:
|
I know this is merged already, and there was an opportunity to comment before it was, so this is sort of pissing in the wind--- but I'm not a huge fan of this change.
.CodeMirror-sizer {
padding-right: 0 !important; So instead of this: ![]()
The thumb bit only shows a 15 x 15 square, but it is actually the same width as the thumb in the original. Which means that I can only move the visible part of the thumb a fraction of the width of the page. This made me think it was broken until I took a few closer looks. The furthest right I can move the thumb: ![]()
|
All adressed in #3388 |
For clarifying, i don't think we want to auto-hide the scrollbar at all, it is less accessible. But if you Really want it, i will implement it. |
The reason for the gradient on itself is to visually separate the scrollbar from the window border, that is the only CSS way i have found to do so. I love your idea for the js scrollbar to incorporate pageinfo, looks cool, but don't think i have the time to make it. Also that might just be our lowest priority. About the corner, am i the only one who prefers scrollbars without tracks? when the track is obviously the page entire size, it looks very antiquated to me. If it were up to me, i would leave it as overlay without tracks. |
I personally just like the normal scrollbars because they are so common and basically 'disappear' from my vision even if they don't actually disappear. Anything that draws my attention to them is bad. So my first preference is to leave them untouched. I do like a track, as it provides a hard edge for the document (since I also don't like to have my scrollbar overlapping what i'm reading/writing). And I prefer a narrow scrollbar rather than wider, for screen real estate reasons-- but honestly it's likely the "what I am used to" factor too. In short, I don't think any change to the scrollbars is necessary or desired. But I also am just one person and don't want to squash dreams. Mostly I'm just raising these points so that there is some record of possible objections, rather than just a "no one commented, so it must be good" process. |
It seems like it might be possible to get a shorter scrollbar that only spans a fraction of the scrolled element, but I'm still researching it. There are webkit-only solutions (like most of the scrollbar styling options), as seen in this fiddle, but it's not perfect and i hesitate to reach for chrome-only things when it comes to simple UI choices. |
It's a scrollbar, not a dream. We could revert to the original and forget about this headache. |
John? you asked for this specifically a few weeks ago #3355 (comment) |
Yeah I suppose in a way I did, but I don't think this is exactly a reversal of my earlier position, just an addendum. A solid spanning decoration like the page break line highlight seems odd if it stops just short of the "visual edge" of the editor. I know earlier that I didn't want to have a scrollbar overlapping my text content but I think this is something different than "my content". Covering my written text, which I may be actively reading or even editing, is visually intrusive. Covering an editor decoration, on the other hand, doesn't seem as big of a problem. Regarding covering the page number text...eh, not in love with it, but I still think stretching the page line break to the "visual edge" is higher priority. So my preference would be:
Native scrollbars achieve both-- nothing covers content, and the visible track edges provide a different "visual edge" to the editor to which the full width line highlights can span and connect to. Native scrollbars are obviously my preference, but in the interest of being open to different options, maybe the below will help with the current implementation: Change the line highlight for the page breaks to have a width of 110% or similar. ![]() It'd be here: https://github.com/NaturalCrit/homebrewery/blob/master/client/homebrew/editor/editor.less#L8 |
Your idea:
5e-Cleric writes..
The text was updated successfully, but these errors were encountered: