35088 2010-02-18 03:47:11 -0800 Setting src on <source> shouldn't restart the resource selection algorithm 2012-02-01 12:16:38 -0800 1 1 1 Unclassified WebKit Media 528+ (Nightly build) PC OS X 10.5 RESOLVED WORKSFORME P2 Normal --- 0 zcorpan webkit-unassigned arun.patole eric.carlson oldest_to_newest 191519 0 zcorpan 2010-02-18 03:47:11 -0800 URLs (if applicable) : Other browsers tested: Add OK or FAIL after other browsers where you have tested this issue: Chrome: FAIL Firefox 3.x: has different bugs IE 7: N/A IE 8: N/A Opera 10.50 beta: OK What steps will reproduce the problem? 1. Consider: <video><source></video> <script> onload = function(){ document.body.firstChild.firstChild.src = 'test.mp4'; } </script> What is the expected result? This should not load anything, because the resource selection algorithm should have been started during parsing and have discarded the <source> element (so that "pointer" is between the <source> and the end of the list). What happens instead? Safari happily loads the video. The author should be required to explicitly call load() per spec. 191520 1 zcorpan 2010-02-18 03:47:39 -0800 http://code.google.com/p/chromium/issues/detail?id=36120 191834 2 zcorpan 2010-02-18 23:18:58 -0800 If I run the script when clicking a button instead of onload, Safari still fails but Chrome passes (though I might have an older webkit for Safari). 546908 3 arun.patole 2012-02-01 01:44:14 -0800 I couldn't reproduce this issue with the latest webkit code. Also the related chromium issue mentioned in Comment #1 is already closed.