User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0b11pre) Gecko/20110128 Firefox/4.0b11pre Build Identifier: Mozilla/5.0 (X11; Linux x86_64; rv:2.0b11pre) Gecko/20110128 Firefox/4.0b11pre Using Firefox nighties, I'm unable to reload <video> streams after closing then re-opening tabs. I haven't tested other builds or operating systems, but I do want to raise the issue before FF 4.0 officially hits. Reproducible: Always Steps to Reproduce: 1. Visit a web page displaying a live Theora/WebM stream using the <video> tag 2. Close the tab, but not Firefox. 3. Re-open the tab using 'cntl-shift-T' and the video fails to display Actual Results: The video element "loads forever" with the throbber. Expected Results: The video should display in the same fashion when loaded for the first time.

Does that also happen with a fresh profile? See: http://support.mozilla.com/en-US/kb/Managing+profiles

Confirmed: Mozilla/5.0 (Windows NT 5.1; rv:2.0b11pre) Gecko/20110202 Firefox/4.0b11pre ID:20110202030356

Build ID: Mozilla/5.0 (Windows NT 6.1; rv:2.0b11pre) Gecko/20110201 Firefox/4.0b11pre Confirmed for featured webm video link: http://195.10.10.75:8800/live.webm However, WFM with theora movie: http://videos.mozilla.org/firefox4beta/Firefox_4_beta.theora.ogv

Is that a regression in the last betas?

Can someone verify this with a different URL? live.webm used above is known to be broken, see bug 584068 comment 10.

Same behavior on a new profile using the latest nightly. Please try the following: http://live.openvideo.pro/4052-a.ogv Unfortunately, my sole internet connectivity at the moment is through my phone so this stream will come and go throughout the day. Wireshark doesn't show any outgoing packets from Minefield when the <video> tab is re-opened, but refreshing the page works as expected (prior to the tab being closed).

So none of the given videos here are working for me. Does anyone has another resource with a live stream? Otherwise I would have to wait for the next brownbag on air.mozilla.org.

Reproduced this locally, it's a dupe of bug 595551.

Sure this is fixed? Seeing the same behavior on 6.0.2.

(In reply to George Chriss from comment #9) > Sure this is fixed? Seeing the same behavior on 6.0.2. No one ever said it was fixed. This bug has been marked as a duplicate of bug 595551. This issue will be addressed in that bug.

I misread Bugzilla. Apologies for this -- George