Re: Issue 98058 in chromium: new Audio('somefile').currentTime is read-only

[chro...@googlecode.com]

Updates:
Status: WontFix

Comment #2 on issue 98058 by imas...@chromium.org: new
Audio('somefile').currentTime is read-only
http://code.google.com/p/chromium/issues/detail?id=98058

I cannot repro the issue with 17.0.947.0 canary on Mac.

This is what I did:

> var mysound=new
> Audio('http://www.nicolasmorin.com/blog/audio/tindi_abalessa.mp3')
undefined
> mysound.currentTime
0
> mysound.duration
35.263126373291016
> mysound.play();
undefined
> mysound.currentTime
9.006351470947266
> mysound.currentTime=0;
0
> mysound.currentTime // IT IS CHANGED.
5.432991027832031
> mysound.play(); // it starts playing
undefined

I cannot repro on 17.0.947.0 on Linux either.

Closing as WONTFIX. If you can repro the issue. Please reopen this if you
can still repro this issue.

[chro...@googlecode.com]

Comment #3 on issue 98058 by solstic...@gmail.com: new

Audio('somefile').currentTime is read-only
http://code.google.com/p/chromium/issues/detail?id=98058

The bug has been filled against chromium 14 !

This is working in chromium 15. But the sound is played as soon as
currentTime is set to 0 whereas autoplay is false

[chro...@googlecode.com]

Comment #4 on issue 98058 by imas...@chromium.org: new

Audio('somefile').currentTime is read-only
http://code.google.com/p/chromium/issues/detail?id=98058

We are sorry for the delay in reply. This bug has been around for a while
without getting our attention. We are improving the bug triage process to
prevent this happen.

Thank you for understanding.

As for your comments about the sound, I think it works as intended.