Hi there,

Chrome OS has recently made a change to how scrollbars look and behave. The scrollbars are still there and should appear when you scroll the page using two-finger scrolling or the mouse wheel. See this link for some tips: https://productforums.google.com/forum/#!topic/chromebook-central/KLMQVJ8MrA8;context-place=forum/chromebook-central. The should also appear when you hover your mouse briefly near the window edge. Note, the scrollbars are now quite thin until you move the mouse nearby.

Does this address your issue or are you describing a bug that's broken in this functionality? (e.g. the scrollbar doesn't appear even when you scroll with the mouse wheel).

The ultra-thin vertical scrollbar appears but doesn't function on my Chromebook. Same experience on larger Chromebooks on display at BestBuy,so this is not a "screen size" issue. Can this be addressed? Thanks.

Could you elaborate on what you mean by "doesn't function"? Does it expand when you move the mouse near it? Are you able to click-and-drag the scrollbar to scroll?

The new scrollbar set up is awful, it doesn't always appear when you hover over it, it is also really hard to see where the scrollbar actually is on certain websites because of the colour and because its so thin. Nobody needs "tips" on how to use a scrollbar i have been using them for 20 years and its pretty basic stuff. Your new scrollbar is terrible its not a user issue just sort it out, why replace something that has always worked  

I'm not entirely certain this is the same issue as mine. Two of the web sites I use all the time suddenly, in the last two days, no longer show vertical scroll bars on <iframe>s I don't mind scroll bars hiding when the body content of the iframe is smaller than the iframe's screen real estate. But when it's pages and pages tall and the scroll bar is invisible (still functions "correctly" when dragged with the mouse), but when I can't *see* to select line scroll buttons, the page scroll areas, or the viewport slider, 'correct mouse function' is close to useless.

I'm sorry, clarification with my specs:

Chrome Version       : Version 60.0.3112.113 (Developer Build) 
OS Version: Built on Ubuntu , running on LinuxMint 17.3 (64-bit)
URLs (if applicable) : fanfiction.net, billpay.captialone360.com
Other browsers tested:
  Add OK or FAIL after other browsers where you have tested this issue:
     Safari 5: Don't have.
  Firefox 4.x: With the firefox I have: OK, same functionality as two days ago. (Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0)
     IE 7/8/9: Don't have.

What steps will reproduce the problem?
1.
2.
3.

What is the expected result?
Functional scroll bar showing on right of iframe area.

What happens instead of that?
-Fanfiction.net RTF-edit iframe doesn't show vertical scroll bar. but responds to mouse actions as if the scroll bar is there.

-captialone360.com bill pay iframe doesn't show vertical scroll bar. does not respond to mouse actions as if scroll bar is there.


Please provide any additional information below. Attach a screenshot if
possible.

UserAgentString: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/60.0.3112.113 Chrome/60.0.3112.113 Safari/537.36

hbregalad@, that's definitely a different issue since you're using Linux. Please create a new bug at crbug.com/new and we can follow up there.

Only the knob is functional, the rest of the trough (85%) is not. Scroll by
tapping is impossible. Click-and-drag larger documents is a carpal tunnel
grind.

The bottom scrollbar for my Asus chromebook completely disappeared after the update. The vertical one appears if I hover in just the right spot, which is a giant pain in the butt. I use them CONSTANTLY because with poor vision I keep the screen at 125 or 150%. To see an entire page, I scroll. 

The NextAction date has arrived: 2017-09-21

The scrollbar wasn't broken and it doesn't need to be fixed. EVERYONE here at work has been complaining about their inability to find the scrollbar and how it is slowing down their work. I just spent an hour scouring the internet until I found a site that told me how to disable the new scrollbar configuration and since then people have been carrying me around on their shoulders yelling "Huzzah." PLEASE do not permanently implement this change to the scrollbar function. The amount of "real estate" obscured by the scrollbar is minimal compared to the time lost trying to find the scrollbar and hang on to it with your cursor to make it work.  

I'd appreciate the URL for that site. The new scrollbar configuration is
infuriating.

 Issue 761644  has been merged into this issue.

Animated/Hidden scrollbars do not work correctly on HP Chromebook 14.  They simply are erradic and do not appear. I spend WAY TOO MUCH time trying to find the scrollbar and get it to appear. IT IS SLOWING MY WORK DOWN.  Some 3rd party extensions I use also do not work now.  EXAMPLE:  Use a text editor.  Scrollbars do not appear at all.

ALSO.

The ALWAYS ON scroll-bars serve another important purpose.  They are a visual indicator of WHERE YOU ARE on a large page.  Top / bottom / middle.  Etc...

By hiding the scrollbars you take away my orientation to where I am in a large document.

This is an unnecessary feature for most of us doing work on a real computer with a large screen.

"Minute" Screen Real-Estate is  an issue for tablet and phone users.

Issue 770552 has been merged into this issue.

I couldn't agree with comments 5, 9, 10, 12, 13 and 16 more. I work all day on a Chromebox and the advent of these semi-hidden scrollbars is driving me bananas and cutting my productivity. 

I would just like to say my current chromebook has been acting up so I have
been using my older chromebook that didn't have this horrific update. It is
so much easier to deal with webpages (especially my work pages but also
facebook) with the old system and I was able to work significantly faster
even though my old chromebook doesn't have a down arrow. But my old
chromebook froze and when I restarted it, it updated automatically to
hidden scrollbar nightmare. I am so sad.

The scroll bar on drop down menus often disappears for me and I have to close and re-open drop downs several times for the bar to appear and stay there. The bar also appears and disappears randomly on main pages, e.g. easyjet's website when trying to select what date I want to fly. I use a Toshiba CB30-B-104 Chromebook, Intel Celeron.

Hi katheather89, I just checked easyjet.com home page and the date selector. The behavior works as expectation. Scrolling or move mouse near scrollbar area will show the scrollbar.

I use both a Chromebox and a Chromebook. Of course, when I use the Chromebox it is with an external keyboard and mouse. Also, a significant amount of the time I am using the Chromebook, it is with an external keyboard and mouse (and monitor.) 

I can always get the overlay scrollbar to appear. I can always see it. My issue is that I cannot drag it, nor can I click to get it to scroll. I have to hover in the area of the scroll and use the arrow keys to make it work.

I have just disabled the overlay scrollbars, and everything is working as expected now.

If they would work when clicked on, I would not mind the auto-hiding scroll bars. Fix that and all will be well.

Only tried this in Chrome on a Chrome box.
Works fine in Chrome on my windows pc at home.
Having issue with hidden scrollbars being inclickable.
They unhide themselves properly, but click and dragging just results in trying to drag the whole element instead of scrolling.

the scroll behavior changes have caused problems with many websites.  For example on many websites where checkboxes appear, once you click one to mark something say on a form to select an answer, the screens scroll resets and brings you back to the very top of the page.  Multiple users are having this issue.  As some one with processing disabilities this is anew extreme problem that results in filling things out wrong or doing things wrong on websites within the chrome browser and also within the chrome settings interface, such as when deleting an individual cookie or site setting.  As someone with disabilities this is a major problem.  In fact, area schools here are not allowing students to use them for the time being until this issue is fixed because it has caused severe issues for many students with disabilities.  I say issue but I know it's a new design, however impact on those with disabilities needs to be your first question, because otherwise you're not creating a platform for everyone, and in reality, discriminating unintentionally in your design of new interfaces.  Hope to see this design tweaked sooner rather than later.  While not at liberty to say who, I just watched Google lose a pretty decent Chromebook contract opportunity with a big nonprofit because of this issue which would make it a problem for employees with disabilities and those without.  The managers were considering options for anew office wide upgrade for their laptops since they're moving to a cloud service.  The managers went and purchased a new Samsung Chromebook plus, tried using the company software which looked great on it, but the issue with too small a scroll bar, randomly misbehaving scroll bars and scroll function where it resets to the very top of a page when executing certain taps or clicks to execute a function or selection killed their idea of switching t0 chrome.  They ultimately gave their business to dell and stayed with a PC interface.  That's over 200 Chromebooks that could have been sold if the interface behaved properly, plus the potential of the company buying into g suite and Google cloud servives.  But they went with alternatives because of how big an issue this actually is.  It might not seem like a big deal, but in reality it is a huge issue that is actually resulting in large losses for yout financially.  It's unfortunate with the number of complaints about this too that the mentality is t0 just ignore the complaints as if it were just people resisting changes.  It's not at all what is going on here.  People including myself really love the polished new interface look, but this major functionality flaw overthrows those likes.  It's nice to have something that looks pretty, but if it's not functional, it becomes obsolete to the user, and then when they go out and talk about the product it does irreparable damage to the brand and company image.

 Being tax season, this has also been an issue with tax software interfaces when interacting on the new scroll behaviors. 

I say this all not to be rude, but to show you the very real impacts that are happening behind the scenes of what you actually may be seeing numbers wise or otherwise where you're at.  It's deterring business unfortunately and costing you money.   200 laptops times about 500 a piece brings you to a total loss of 100,000.00. Not to mention the money that could have been earned by the sales of gsuite and other corporate software, plus ads.  All because of a misbehaving scroll design.

please see discussion under another bug for more information and a connection to this issue. Comment 13 sounds dead on and read through my steps to reproduce the issue as well as a theory as to why and how this happens.  

Deleted: Screenshot 2018-04-13 at 4.05.54 AM.png 596 KB

	Screenshot 2018-04-13 at 4.05.54 AM.png 596 KB View Download

We have a few apps where our 200+ Chrome OS users are struggling because of this.  I'd prefer having the scrollbars hide if a mouse IS NOT plugged in (touch interface), but show normally if a mouse is present. At a minimum, I think it would be appropriate to have a setting to allow users to control scrollbar auto-hide behavior.

There is a bug with this feature that breaks mouse-wheel scrolling in the latest release of Chrome OS. Scrolling with the wheel simply stops working, however other tabs in Chrome are able to scoll, and keyboard scrolling still works.

You can disable the flag but I have around 40 devices managed in G Suite, is there any way I can change the flag for their OU through the Google Admin Conosle?

carter.rohan.wilson@: Hi, that's unexpected. Can you please file a new bug (cc me if you can) with detailed instructions on how to reproduce the issue. That sounds like a severe bug we need to look into.