Hmmm... this is not what I expected. Again... there maybe something missing in my understanding here?...
I did eventually manage to affect the scrollbars, but NOT by modifying the values of any references to
::-webkit-scrollbar-... that were pre-existing in the skin files. My base skin is Metro M (Classic). There is only one file in the skin that has them:
\skin\skin_scrollbar.less
I went as far as making my changes really obvious with some gaudy color-scheme, e.g....
Code: Select all
@scrollbarSize: @units1_9;
@scrollbarTrackColor: red;// lighten(@secondaryColor, 6%);
@scrollbarHighlightColor: pink;//lighten(@secondaryColor, 20%);
::-webkit-scrollbar {
width: @scrollbarSize;
height: @scrollbarSize;
border: 1px solid @baseColor;
}
/* Track */
::-webkit-scrollbar-track {
background: blue;//@scrollbarTrackColor;
padding: 2px;
}
/* Handle */
::-webkit-scrollbar-thumb {
background: green;//lighten(@baseColor, 10%);
border: 2px solid @scrollbarTrackColor;
min-height: 6.5%;
}
::-webkit-scrollbar-thumb:active{
background: yellow;//@baseColor;
}
::-webkit-scrollbar-corner {
background: transparent;
}
::-webkit-scrollbar-button:single-button {
background-color: orange;//@scrollbarTrackColor;
fill: red;//@baseColor;
width: @scrollbarSize;
height: @scrollbarSize;
background-size: @scrollbarSize + @units0_5;
background-position: center;
transition: background-color@animationTime ease-out;
&:hover{
background-color: @scrollbarHighlightColor;
}
}
::-webkit-scrollbar-button:single-button:vertical:decrement{
background-image: url('/skin/icon/upArrow.svg');
}
::-webkit-scrollbar-button:single-button:vertical:increment{
background-image: url('/skin/icon/downArrow.svg');
}
::-webkit-scrollbar-button:single-button:horizontal:decrement{
background-image: url('/skin/icon/leftArrow.svg');
}
::-webkit-scrollbar-button:single-button:horizontal:increment{
background-image: url('/skin/icon/rightArrow.svg');
}
body
{ /* This is scrollbar fallback for IE and other non-WebKit browsers, where support for skinned scrollbars is limited*/
scrollbar-face-color: red;//@highlightBgColor;
scrollbar-arrow-color: blue;//@textColor;
scrollbar-track-color: green;//@controlColor;
scrollbar-shadow-color: yellow;//@highlightBgColor;
scrollbar-highlight-color: orange;//@highlightBgColor;
scrollbar-3dlight-color: pink;//@highlightBgColor;
scrollbar-darkshadow-color: cyan;//@highlightBgColor;
}
I also made sure I did a soft-refresh of Chromium after every change. I also tried a restart of MM, to no change.
I only managed to get the scrollbars to change once I'd copy/pasted all the code from
\skin\skin_scrollbar.less onto the end of my
\skin\skin_custom.less file! :\
Why don't any mods of
\skin\skin_scrollbar.less have any effect? I've also tried putting the mods into
\skin\skin_scrollbar_add.less , and that also is ineffective.
Here's my mods with some new scrollbar styling...
Tip for the Skinning Manual: For the horizontal scrollbar, the image texture needed to be rotated 90 degrees. Current CSS doesn't support transfomations of the bkd image without transfoming the whole element, or without convoluted "CSS tricks". So I duplicated the vertical image and created a rotated copy. However, to my befuddlement (again!), I couldn't get it to work initially... and no amount of Chromium Skin Refreshing would show the image.
After some experimentation, I discovered that for new images referenced in the
\images\ folder to show up, I needed
a complete restart of MM.

Pete, from Wellington, New Zealand.
Currently evaluating a migration from MM4 (4.1.31.1919 on Win7 SP1/16Gig RAM/intel) to MM2024 (latest Debug version on Win11 24H2/16GB RAM/intel)
**If you're wondering why I'm still on MM4: It still has more useful-to-me plugins; and I prefer the GUI's responsiveness, panes spreadable over multi-monitors flexibility, and predictability (all coz it's more Windows-native). I also hate "flat design" for its visual inefficiency. For me, MM4's benefits are still > MM5, and MM5's downsides < MM4. There still appears to be way less MM5 plugins -- even after all this time. MM5 docs for plugin developers seem very undeveloped to me -- which makes me uninclined to invest into learning how to improve MM5 for my own wants.