Bug 60844

Summary: Use test from ietestcenter fails
Product: WebKit Reporter: Rob Buis <rwlbuis>
Component: SVGAssignee: Rob Buis <rwlbuis>
Status: RESOLVED FIXED    
Severity: Normal CC: dglazkov, webkit.review.bot, zimmermann
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
URL: http://samples.msdn.microsoft.com/ietestcenter/svg112/svg/svg/chapter_05.12.svg
Attachments:
Description Flags
Patch
krit: review+, webkit.review.bot: commit-queue-
Archive of layout-test-results from ec2-cr-linux-02 none

Rob Buis
Reported 2011-05-14 12:59:23 PDT
This test is based on struct-use-14-f.svg from SVG 1.1SE testsuite. The <use> is not updated when the id changes on the element. Both FF and Opera pass this one.
Attachments
Patch (25.72 KB, patch)
2011-05-14 13:13 PDT, Rob Buis 		krit: review+
webkit.review.bot: commit-queue-
DetailsFormatted DiffDiff
Archive of layout-test-results from ec2-cr-linux-02 (1.16 MB, application/zip)
2011-05-14 13:37 PDT, WebKit Review Bot 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Rob Buis
Comment 1 2011-05-14 13:13:07 PDT
Created attachment 93563 [details] Patch
WebKit Review Bot
Comment 2 2011-05-14 13:37:46 PDT
Comment on attachment 93563 [details] Patch Attachment 93563 [details] did not pass chromium-ews (chromium-xvfb): Output: http://queues.webkit.org/results/8696530 New failing tests: svg/W3C-SVG-1.1-SE/struct-use-14-f.svg
WebKit Review Bot
Comment 3 2011-05-14 13:37:50 PDT
Created attachment 93566 [details] Archive of layout-test-results from ec2-cr-linux-02 The attached test failures were seen while running run-webkit-tests on the chromium-ews. Bot: ec2-cr-linux-02 Port: Chromium Platform: Linux-2.6.35-28-virtual-x86_64-with-Ubuntu-10.10-maverick
Dirk Schulze
Comment 4 2011-05-20 12:01:58 PDT
Comment on attachment 93563 [details] Patch r=me. Please make sure why cr bot fails before landing.
Rob Buis
Comment 5 2011-05-20 12:53:36 PDT
Committed r86978: <http://trac.webkit.org/changeset/86978>
Note You need to log in before you can comment on or make changes to this bug.