Bug 64917

Summary: load() does not reset the resource selection algorithm
Product: WebKit Reporter: Eric Carlson <eric.carlson>
Component: MediaAssignee: Eric Carlson <eric.carlson>
Status: RESOLVED FIXED    
Severity: Normal CC: webkit-bug-importer, webkit.review.bot
Priority: P2 Keywords: InRadar
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Proposed patch.
none
Proposed patch.
none
Updated patch darin: review+

Eric Carlson
Reported 2011-07-20 19:24:40 PDT
Calling the load() method on a media element should reset state so the resource selection algorithm starts over, but <source> element selection is not reset.
Attachments
Proposed patch. (9.73 KB, patch)
2011-07-20 20:06 PDT, Eric Carlson 		no flags
DetailsFormatted DiffDiff
Proposed patch. (9.16 KB, patch)
2011-07-20 20:09 PDT, Eric Carlson 		no flags
DetailsFormatted DiffDiff
Updated patch (9.21 KB, patch)
2011-09-01 14:11 PDT, Eric Carlson 		darin: review+
DetailsFormatted DiffDiff
Show Obsolete (2) View All Add attachment proposed patch, testcase, etc.
Eric Carlson
Comment 1 2011-07-20 19:25:01 PDT
<rdar://9712909>
Eric Carlson
Comment 2 2011-07-20 20:06:33 PDT
Created attachment 101549 [details] Proposed patch.
WebKit Review Bot
Comment 3 2011-07-20 20:08:43 PDT
Attachment 101549 [details] did not pass style-queue: Failed to run "['Tools/Scripts/check-webkit-style', '--diff-files', u'LayoutTests/ChangeLog', u'LayoutTests/medi..." exit_code: 1 Source/WebCore/platform/graphics/MediaPlayer.cpp:197: Should have a space between // and comment [whitespace/comments] [4] Total errors found: 1 in 6 files If any of these errors are false positives, please file a bug against check-webkit-style.
Eric Carlson
Comment 4 2011-07-20 20:09:50 PDT
Created attachment 101550 [details] Proposed patch.
Eric Carlson
Comment 5 2011-09-01 14:11:37 PDT
Created attachment 106027 [details] Updated patch Update results slightly
Eric Carlson
Comment 6 2011-09-06 11:49:26 PDT
http://trac.webkit.org/changeset/94584
Note You need to log in before you can comment on or make changes to this bug.