The Chrome implementation will (until we fix it) not support adding an id again after removing an id. I plan to separate the existing testRemoveIDFailureCases to avoid doing that, and add a test that explicitly tests adding ids after a remove (we will fail that test for while).
Created attachment 146922 [details] Patch
Comment on attachment 146922 [details] Patch Attachment 146922 [details] did not pass chromium-ews (chromium-xvfb): Output: http://queues.webkit.org/results/12945405 New failing tests: http/tests/media/media-source/video-media-source-add-and-remove-ids.html
Created attachment 146980 [details] Archive of layout-test-results from ec2-cr-linux-03 The attached test failures were seen while running run-webkit-tests on the chromium-ews. Bot: ec2-cr-linux-03 Port: <class 'webkitpy.common.config.ports.ChromiumXVFBPort'> Platform: Linux-2.6.35-28-virtual-x86_64-with-Ubuntu-10.10-maverick
I should have added that these changes will not pass until the chromium changes land (which is pending these changes).
Created attachment 147035 [details] with test expectations added
Comment on attachment 147035 [details] with test expectations added rs=me
Comment on attachment 147035 [details] with test expectations added Thanks Eric!
Comment on attachment 147035 [details] with test expectations added Clearing flags on attachment: 147035 Committed r120097: <http://trac.webkit.org/changeset/120097>
All reviewed patches have been landed. Closing bug.