#8222 closed bug (wontfix)
Double Asset Request for Video Tag
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | low | Milestone: | 1.next |
Component: | manipulation | Version: | 1.5 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
I've only tested this in Chrome 9, but here are the steps to reproduce:
- create an empty HTML document, embedding jQuery (I've tried this with 1.4.3 and 1.5
- create a video tag string, wrap it with jQuery (ex: var vidtag = $('<video controls="true"><source src="myvideo.mp4"></video>');)
- open the networking tools to see the files that chrome is requesting. myvideo.mp4 is requested twice.
Chrome is already relatively unstable when it comes to HTTPStreaming, this seems to be the straw that broke the camel's back. Doing a double request like this seems to lock up Chrome more often than not for me in my situation.
This problem seems unique to jQuery - setting the innerHTML of a div to the video tag without jQuery doesn't perform a double request, and of course neither does just having a video tag already on the page
Change History (4)
comment:1 Changed 12 years ago by
Owner: | set to [email protected]… |
---|---|
Status: | new → pending |
comment:2 Changed 12 years ago by
JSFiddle (hope I did this right, I've never used it) http://jsfiddle.net/NYNCF/2/
comment:3 Changed 12 years ago by
Component: | unfiled → manipulation |
---|---|
Priority: | undecided → low |
Resolution: | → wontfix |
Status: | pending → closed |
Try this: http://jsfiddle.net/rwaldron/fssD9/2/
comment:4 Changed 12 years ago by
Thanks very much - that worked great. I'm newish to jQuery, so if that's the correct usage to instantiate a tag like this, awesome.
Unfortunately, the code instantiation code isn't mine, but is from the HTML5 branch of the Open Video Player project.
I'll see if I can make a similar bug report to them.
Thanks for taking the time to contribute to the jQuery project by writing a bug report.
Please submit a reduced test case, which reproduces the issue you are experiencing, on http://jsfiddle.net. So that we can investigate this issue further. Also make sure to read the link given below, in order to provide a most useful bug report.
How to report bugs