Closed
Bug 755056
Opened 12 years ago
Closed 12 years ago
nsSVGForeignObjectFrame::mRect should include its x/y offset
Categories
(Core :: SVG, defect)
Core
SVG
Tracking
()
RESOLVED
FIXED
mozilla15
People
(Reporter: jwatt, Assigned: jwatt)
References
(Depends on 1 open bug)
Details
Attachments
(1 file)
|
2.13 KB,
patch
|
longsonr
:
review+
|
Details | Diff | Splinter Review |
nsSVGForeignObjectFrame::mRect should include the offset due to the x/y attributes. The only reason that we currently get away with this bug is because setting mRect's x/y to zero means that nsSVGForeignObjectFrame::InvalidateDirtyRect does the right thing.
|
Assignee | |
Updated•12 years ago
|
Summary: nsSVGForeignObjectFrame::mRect should include the x/y offset → nsSVGForeignObjectFrame::mRect should include its x/y offset
|
|
Assignee | |
Comment 1•12 years ago
|
||
Attachment #623832 -
Flags: review?(longsonr)
|
||
Updated•12 years ago
|
Attachment #623832 -
Flags: review?(longsonr) → review+
|
|
Assignee | |
Comment 2•12 years ago
|
||
Pushed https://hg.mozilla.org/integration/mozilla-inbound/rev/d5356ca73466
|
||
Comment 3•12 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/d5356ca73466
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Flags: in-testsuite-
Resolution: --- → FIXED
Target Milestone: --- → mozilla15
You need to log in
before you can comment on or make changes to this bug.
Description
•