Use SetParsedAttr in nsSVGElement::DidChangeXxx instead of SetAttr

RESOLVED FIXED in mozilla2.0

Status

()

defect
RESOLVED FIXED
9 years ago
9 years ago

People

(Reporter: jwatt, Assigned: jwatt)

Tracking

({perf})

unspecified
mozilla2.0
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

We should use SetParsedAttr in nsSVGElement::DidChangeXxx instead of SetAttr to avoid a serialize-reparse cycle.
Posted patch patchSplinter Review
This depends on bug 610990. Essentially it just changes the serialize-parse loop to just the serialize. Should be very safe.
Assignee: nobody → jwatt
Status: NEW → ASSIGNED
Attachment #508303 - Flags: review?(roc)
Attachment #508303 - Flags: approval2.0?
Attachment #508303 - Flags: review?(roc)
Attachment #508303 - Flags: review+
Attachment #508303 - Flags: approval2.0?
Attachment #508303 - Flags: approval2.0+
http://hg.mozilla.org/mozilla-central/rev/7aa71efbb69c
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla2.0
You need to log in before you can comment on or make changes to this bug.