New issue
Advanced search Search tips

Issue 98391 link

Starred by 3 users

Issue metadata

Status: Fixed
Owner: ----
Closed: Feb 2012
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug

  • Only users with EditIssue permission may comment.

Sign in to add a comment

Moving SVG elements on the page doesn't always erase element at the old position

Reported by, Sep 28 2011

Issue description

Chrome Version       : 15.0.874.21 (other versions tested)
OS Version: Windows and Linux
URLs (if applicable) :
Other browsers tested:
     Safari 5: FAIL
  Firefox 4.x: OK
IE 7/8/9:

What steps will reproduce the problem?
1. Move SVG elements on the page via the DOM (see 'Move textbox down' button on Bug #1 of test page above)

What is the expected result?
Clean redraw of element in new position, erase of element at old position

What happens instead?
On some moves, part of the old element is not erased and leaves artifacts on the screen

Please provide any additional information below. Attach a screenshot if

Tested on Linux (Chromium) and Windows (Chrome) since version 7, still present in v15. Presumably a webkit issue....

UserAgentString: Mozilla/5.0 (X11; Linux i686) AppleWebKit/535.2 (KHTML, like Gecko) Chrome/15.0.874.21 Safari/535.2

4.6 KB View Download
Labels: -Area-Undefined Area-WebKit
Status: Untriaged
I'm able to reproduce the issue in Chrome 16.0.894.0 (Official Build 103082)/Win7

Comment 2 by, Sep 29 2011

Labels: WebKit-SVG

Comment 3 by, Oct 4 2011

Labels: Mstone-16

Comment 4 by, Oct 24 2011

Labels: -Mstone-16 MovedFrom-16 Mstone-17

Comment 5 by, Dec 6 2011

Labels: -Mstone-17 MovedFrom-17
Removing milestone from all untriaged M17 bugs.

Comment 6 by, Dec 9 2011

Cross posted to webkit as
Fix reported committed as of
Labels: Mstone-17 Merge-Requested
This is a one-line fix that affects incorrect redraw when moving SVG elements. It landed right after the M17 branch point unfortunately, but it shouldn't affect stability and it's a really silly bug to have. Is there any chance this change can still make it into M17?

Comment 9 by, Feb 6 2012

Status: Fixed
Sorry, we're basically done.

Comment 10 by, Feb 6 2012

Labels: -Merge-Requested Merge-Rejected

Comment 11 by, Feb 14 2012

I realise this missed the M17 branch, but testing in v18.0.1025.11 beta (google-chrome ebuild on gentoo) it appears to be fixed although this bug report doesn't reflect that yet (perhaps fixed as a side effect of other changes).
Thanks to whoever merged the fix anyway...
Project Member

Comment 12 by, Oct 13 2012

Labels: Restrict-AddIssueComment-Commit
This issue has been closed for some time. No one will pay attention to new comments.
If you are seeing this bug or have new data, please click New Issue to start a new bug.
Project Member

Comment 13 by, Mar 10 2013

Labels: -Area-WebKit -WebKit-SVG -Mstone-17 Cr-Content Cr-Content-SVG M-17
Project Member

Comment 14 by, Mar 13 2013

Labels: -Restrict-AddIssueComment-Commit Restrict-AddIssueComment-EditIssue
Project Member

Comment 15 by, Apr 6 2013

Labels: -Cr-Content Cr-Blink
Project Member

Comment 16 by, Apr 6 2013

Labels: -Cr-Content-SVG Cr-Blink-SVG

Sign in to add a comment