I'm experiencing an issue where the priority of Object Relations is not being saved correctly when autosaved with the TrackUserInput setting enabled.

I suspect the issue is to do with Object Relations resetting to 1, 2, 3, 4 when focus shifts to the next field, without changing the visible order of related objects names on the client-side (well, that's the only explanation I can think of).

Steps to reproduce

1. Using eZ Publish 4.7 and latest ezautosave from GitHub, create a new node from a content class which has Object Relations as a field.
2. Add 4 object relations and prioritise
3. Click "Send for publishing"
4. Edit the node and re-order the object relations
5. Click "Send for publishing"
6. Check the output (or re-edit)

*Expected result:* Object relations are saved in the correct order
*Actual result:* Object relations order (priority) is not saved correctly