nsSVGForeignObjectFrame::mRect should include its x/y offset

RESOLVED FIXED in mozilla15

Status

()

Core
SVG
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: jwatt, Assigned: jwatt)

Tracking

(Depends on: 1 bug)

Trunk
mozilla15
Points:
---
Bug Flags:
in-testsuite -

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

5 years ago
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

5 years ago
Summary: nsSVGForeignObjectFrame::mRect should include the x/y offset → nsSVGForeignObjectFrame::mRect should include its x/y offset
(Assignee)

Comment 1

5 years ago
Created attachment 623832 [details] [diff] [review]
patch
Attachment #623832 - Flags: review?(longsonr)

Updated

5 years ago
Attachment #623832 - Flags: review?(longsonr) → review+
(Assignee)

Comment 2

5 years ago
Pushed https://hg.mozilla.org/integration/mozilla-inbound/rev/d5356ca73466
https://hg.mozilla.org/mozilla-central/rev/d5356ca73466
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Flags: in-testsuite-
Resolution: --- → FIXED
Target Milestone: --- → mozilla15

Updated

5 years ago
Depends on: 824464
You need to log in before you can comment on or make changes to this bug.