UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.119 Safari/537.36

Steps to reproduce the problem:
If you have a page with a content editable div and the content contains more than one object (either it was initialized that way, or user has edited it).

e.g.

<div class="edit" contentEditable="true">one<b>two</b>three</div>

The IAccessible2 tree would report this as 4 objects:
(div) section - state=editable
static text - one
static text - two
static text - three

If the caret is within segment one and you start selecting text to the right, everything works. You get IA2_EVENT_TEXT_CARET_MOVED events that start in "one" and then the events move to "two" and then "three" as you expand the selection. get_selection on each child node also returns the correct selection as the section is expanded.

However, if you start with the caret in "three" and start selecting to the left, it works until the caret reaches "two". After this point, caret events are still sent to node three and get_selection() does not return correct values for nodes one and two. 

What is the expected behavior?
get_selection should work regardless of whether text is selected forwards or backwards through a document.

Also, IA2_EVENT_TEXT_CARET_MOVED should be sent to the node that contains the end of the selection that is moving. This could be to the left or right of the starting point.

What went wrong?
see above

Did this work before? No 

Chrome version: 66.0.3336.0  Channel: canary
OS Version: 10.0
Flash Version: Shockwave Flash 28.0 r0

It doesn't matter if you select text using the keyboard or mouse.

component:UI>Accessibility>Compatibility