https://www.w3.org/TR/html5/embedded-content-0.html#getting-media-metadata:

10. If either the media resource or the address of the current media resource indicate a particular start time, then set the initial playback position to that time and, if jumped is still false, seek to that time and let jumped be true.


https://www.w3.org/TR/html5/embedded-content-0.html#dom-media-currenttime:

The currentTime attribute must, on getting, return the media element's default playback start position, unless that is zero, in which case it must return the element's official playback position. The returned value must be expressed in seconds.


As default playback start position and initial playback position are different things, it seems* like Safari is doing the right thing there.
Do you mind folks double-checking there?

Would you mind providing a sample testcase for the TE to reproduce?

Go to https://beaufortfrancois.github.io/sandbox/media/loadedmetadata.html

In Chrome:
  [loadedmetadata] currentTime: 113

In Safari for Mac:
  [loadedmetadata] currentTime: 113

In Safari for iOS:
  [loadedmetadata] currentTime: 0

Thank you for providing more feedback. Adding requester "rbasuvula@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

fbeaufort@, that looks a lot like a Safari iOS bug: the currentTime is set to 113 from the URL and Firefox, Safari macOS and Chrome all return 113 for the currenttime when metadata is loaded.

Unable to reproduce the issue on windows 7, Ubuntu 14.04 and Mac 10.12.3 using chrome version 58.0.3029.33 and canary 59.0.3051.3.Able to see the 
  [loadedmetadata] currentTime: 113

fbeaufort@ Could you please confirm on the expected behaviour to triage the issue.

Thanks,

Re: Comment 7, this is expected indeed.

Re: Comment 6, is this what you expect when reading html spec? If so, I'll go file a bug on Safari iOS.

Thank you for providing more feedback. Adding requester "kavvaru@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

fbeaufort@ This might not chrome related issue as the issue not seen on chorme.Please file a bug on Safari iOS.
Please confirm on the thread so the we will close this issue.

Thanks,

Due to lack of user feedback closing this issue.

fbeaufort@ Please feel free to raise a new issue if you face any issue on chrome.

Thanks,