Closed Bug 594792 Opened 14 years ago Closed 14 years ago

How do I stop loading of tabcandy_howto.webm?

Categories

(Firefox Graveyard :: Panorama, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: kdevel, Unassigned)

References

Details

User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0b6pre) Gecko/20100909 Firefox/4.0b6pre Build Identifier: Mozilla/5.0 (X11; Linux x86_64; rv:2.0b6pre) Gecko/20100909 Firefox/4.0b6pre FF/MF continues to load tabcandy_howto.webm even if the video area has been closed. Reproducible: Always Steps to Reproduce: 1. Open a new browser window (Ctrl-N). 2. Press the tab candy button. 3. A video object titled "How to organize your tabs" appears. 4. close that video area with (X) 5. observe with some network tool, that the loading of the video continues. Actual Results: Loading of the video continues until finished or the new browser window is closed. Expected Results: Loading of the video terminates as soon as the video-area is closed.
Stefan, we are currently planning to change the firstrun experience so that the video is actually loaded in its own tab, at which point this bug will no longer apply.
Which notion/interpretation of "first" does apply here? The thing is that the webm video start every time I create a new browser window.
(In reply to comment #2) > Which notion/interpretation of "first" does apply here? The thing is that the > webm video start every time I create a new browser window. Bug 593157 will fix the behavior of "first".
Depends on: 593157
This bug will no longer apply soon as we are removing the first-run video item and instead opening a new tab on startup with a welcome page (bug 596075).
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → WONTFIX
Is anybody working on the audio/video object leak?
Stefan, what leak are you referring to? If you mean the video loading issue which is this bug, it will no longer be an issue once bug 596075 lands.
Product: Firefox → Firefox Graveyard
You need to log in before you can comment on or make changes to this bug.