====================================

Good Build:

50.0.2629.0    Base Position: 371142


Bad Build:

50.0.2631.0    Base Position: 371419

=====================================

Able to repro this issue on Windows 7, MAC (10.11.6) & Ubuntu Trusty (14.04) for the Google Chrome Stable Version - 52.0.2743.116	

This is a regression issue broken in M50, below mentioned is the bisect info:

Suspecting Below:

======================================================================================================================================================

BISECT TOOL - CHANGELOG URL: https://chromium.googlesource.com/chromium/src/+log/56f66725674e6e4795e02b16c928372450061129..45f46be8dd032d12b198ca4e81d60b652b27dce6

Suspecting Commit: 45f46be8dd032d12b198ca4e81d60b652b27dce6

Review URL: https://codereview.chromium.org/1625423002

======================================================================================================================================================

MANUAL - CHANGELOG URL: https://chromium.googlesource.com/chromium/src/+log/50.0.2629.0..50.0.2631.0?pretty=fuller&n=10000

Suspecting Commit: be94d60086b4453ea0f3769a9a3e85feb0cfbfe9	

Review URL: https://codereview.chromium.org/1627713002

======================================================================================================================================================

@yosin / thakis: Could you please look into the issue, and if it has nothing to do with your changes and if possible please do assign it to the concerned owner.

Thank you.

Please bump as this issue affects a large number of users using CKEDITOR and possibly other WYSIWYG editors.

This issue is affecting usability of our product, we generally recommend Chrome as the browser of choice for use with our web application but because of this issue and its effect on CKEditor we may have to start recommending firefox. 

https://chromium.googlesource.com/chromium/src/+/be94d60086b4453ea0f3769a9a3e85feb0cfbfe9 says in the CL description that it adds comments. It can't be the cause of this. The regression range has the oilpan switch on it which could arguably cause this (and anything), but to me the bisect range looks wrong.

Could you take a look at this scrollbar bug when you get a chance szager?

Bisect Info:
===========

Good build : 50.0.2629.0,  Revision Range(371142)
Bad build  : 50.0.2631.0,   Revision Range(371419)

After executing the per-revision-bisect script, i got the following CL's between good and bad build versions
===========================================
https://chromium.googlesource.com/chromium/src/+log/56f66725674e6e4795e02b16c928372450061129..b25744bcc43fc02389cb7e5e2a59a050c05a9386

The suspecting Change Log is :
-----------
https://chromium.googlesource.com/chromium/src/+/b25744bcc43fc02389cb7e5e2a59a050c05a9386


Review URL
---------------------------
Review URL: https://codereview.chromium.org/1611303006

haraken@- Could you please look into this issue, if it's related to your change?  if not could you please help us to reassign this issue to the right owner.

Note: The above issue is not seen on Mac OS

And found a possible solution for ckeditor which is that when you close the dropdown will be put in the styles manually with a function the "display: none" when the dropdown is hidden and so the scroll will appear again.
I have the code compiled so I can not solve it I get too tangled Can anyone help saying how to do it?

Deleted: ck.jpg 14.1 KB

	ck.jpg 14.1 KB View Download

Deleted: cke.jpg 26.9 KB

	cke.jpg 26.9 KB View Download

This is occurring with Chrome 56.0.2924.87 on Windows 10 Version 1703 (OS Build 15063.540).

Showing and hiding the iframe with display:block and display:none causes the scollbars to disappear on the second occurrence.

My work-around is to use visibility:visible and visibility:hidden.

No longer reproduces in 60 or later.

Bug reproduce after 60 version again (only destop).

I can confirm I'm seeing this again also.

Version 63.0.3239.108 (64-bit) - Ubuntu.

Need reopened issue.

I can confirm this issue happening in Windows and Linux in Chrome 63. It doesn't happen in MacOS with the "always show scrollbars" setting on.

I confirm too see https://dev.ckeditor.com/ticket/14716.
Why does this issue still have WontFix status ?

Sorry, the correct URL is https://github.com/ckeditor/ckeditor-dev/issues/1390

Reopening as requested. Stefan, would you mind taking a look?

I can reproduce this on linux with chrome version 64.0.3282.71 (beta), but it no longer reproduces for me in chrome version 65.0.3311.3 (dev).

It's not obvious to me what changed between those versions that might have fixed this.

I can confirm I'm no longer able to reproduce this issue on Chrome 65.0.3314.1 (Win10) 🎉

So this issue happened for the first time in Chrome 52, then it started working again in Chrome 60, then it got broken again in Chrome 63, then it got fixed somehow in Chrome 64. Would it be possible to add some kind of automated test for this case? That way the bug would be catch before it lands in stable versions.