UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 Safari/537.36

Steps to reproduce the problem:
1. Open the attached html doc in chrome.
2. Press third button (Set Cursor to End).
3. Press third button (Set Cursor to End) again.
4. Press first button (Set Cursor to Begin). 
5. Press first button (Set Cursor to Begin) again.
6. Press fourth button (Set Cursor to End and refocus).

What is the expected behavior?
The expected behavior of steps 2 and 4 are:
2. After pressing the third button (Set Cursor to End) – DomRef.selectionStart/DomRef.selectionEnd (cursor) gets set to the end of the text and the textArea should scroll to the end.
4. After pressing the first button (Set Cursor to Begin) – DomRef.selectionStart/DomRef.selectionEnd (cursor) gets set to the begin of the text and the textArea should scroll to the beginning.

What went wrong?
The behavior is wrong in the following steps:
2. After pressing the third button (Set Cursor to End) – DomRef.selectionStart/DomRef.selectionEnd (cursor) gets set to the end of the text – but textArea does not scroll accordingly.
4. After pressing the first button (Set Cursor to Begin) – DomRef.selectionStart/DomRef.selectionEnd (cursor) gets set to the begin of the text – but textArea does not scroll accordingly.

Did this work before? Yes 

Chrome version: 50.0.2661.102  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 21.0 r0

Looks like scrolling to current cursor position after setting DomRef.selectionStart/DomRef.selectionEnd takes place only when refocusing the corresponding DomRef … this was different in former chrome versions as well as FF.