Closed Bug 475463 Opened 16 years ago Closed 16 years ago

Dragging thumb to zero position the video stop playing, and start/pause control stop responding.

Categories

(Core :: Audio/Video, defect)

defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 476973

People

(Reporter: BijuMailList, Unassigned)

References

Details

Bug 462113 implemented progress bar / scrubber for video controls But many times when I drag the "thumb" of a playing video to zero position the video stop playing, and start/pause control stop responding. Something similar to bug 475292, but happens on buffered area also.
Severity: enhancement → normal
OS: All → Windows XP
Hardware: All → x86
Are you sure this isn't because it's taking an enormously long time to seek? I just tested it and got the symptoms you described because it was still seeking. When the seek completed it started playing. One way to check for this is to see if the seeking attribute on the video element is true. If it is, the seek is still in progress.
(In reply to comment #1) > Are you sure this isn't because it's taking an enormously long time to seek? Yes, that is why I feel it is different from bug 475292 > When the seek completed it started playing. It never started again after many minutes. Here is the simple steps to reproduce it 1. Download a simple ogg file to your local drive, like the one from http://commons.wikimedia.org/wiki/File:Fraser_island_australia_sand_track.ogg 2. open the ogg file from the local drive in firefox (Minefield/3.2a1pre). 3. click play button on the video UI control 4. wait 10 sec 5. with mouse drag the "thump" to zero 6. wait 10 sec 7. repeat from step 5 many times Result: After few times the video gets stuck. I get this on my old computer by around 5 times, on other faster computer may be on 10 or 15th time.
also this is not same as Bug 471220 ie, once stuck we can change URL and then play thru javascript
OS: Windows XP → All
Hardware: x86 → All
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.