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

Steps to reproduce the problem:
NA

What is the expected behavior?

What went wrong?
In https://developer.chrome.com/extensions/tabs

move
chrome.tabs.move(integer or array of integer tabIds, object moveProperties, function callback)

for the second parameter moveProperties

integer	index	
The position to move the window to. -1 will place the tab at the end of the window.

Shouldn't it be "The position (in the window) to move the tab(s) to"? Also specify what happens when there are multiple tabs to move. My guess is the target indices of the tabs moved are successively incremented by one. Basically, on move([tab1, ..., tabn], targetIndex), the result would be tab1 at targetIndex, tab2 at targetIndex+1, ..., tabn at targetIndex+n-1, right?

Did this work before? N/A 

Does this work in other browsers? N/A

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