UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.181 Safari/537.36

Steps to reproduce the problem:
1. Build and launch this Google codelab https://github.com/googlecodelabs/optimized-for-chromeos
2. Drag the "Drag me" text view
3. Do a configuration change (rotation in tablet mode for instance)
4. Drag the "Drag me" text view

What is the expected behavior?
Position of the "Drag me" text view follows the touch position

What went wrong?
Position of the "Drag me" has a huge (kind of unpredictable) offset both in x & y coordinates after configuration change.
Once the issue occurs, it's always the case, doesn't seem the case the very first time.

Did this work before? N/A 

Chrome version: 67.0.3396.99  Channel: stable
OS Version: OS X 10.12.6
Flash Version: 

I've initially opened a bug on the Android library tracker but they closed it telling me it's a ChromeOS issue and that I should open a bug here.
The question asked doesn't seem to indicate I can detail detailed Android (on ChromeOS) development details, this tracker being more Chrome Browser / Web developer oriented it seems.

I copy the details of my initial bug here:

Using the sample code provided, triggering a drag and drop using Activity.startDragAndDrop works properly except the DragShadowBuilder position being wrong sometimes. It can happen that it's ok but after a configuration change (rotation, screen resize…), there is an (huge) offset between finger position (DragEvent x, y in DRAG_LOCATION) and the display of the drag shadow.
The x, y position of the DragEvent are correct, only the shadow is wrong.
Works perfectly on Android on phones and tablets, only issues on ChromeOS (M67 (67.0.3396.99 / stable) or M69 (69.0.3473.0 / dev)) on Pixelbook or Samsung Chromebook PLUS or PRO.

I already implemented a drag and drop solution in my own app without using this Codelab with slight different approach and custom drag shadow builder implementation and had the same issue.
I tried this code lab to check if the issue was on my side or not. Apparently, not.