Closed Bug 877029 Opened 11 years ago Closed 11 years ago

add a crashtest to ensure UpdateGlyphPositioning aForceGlobalTransform is being used correctly

Categories

(Core :: SVG, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla24

People

(Reporter: heycam, Assigned: heycam)

Details

Attachments

(1 file)

One use of nsSVGTextFrame(2)::UpdateGlyphPositioning's aForceGlobalTransform argument is to ensure we don't call GetCanvasTM() on a <marker> ancestor of a <text>, which would crash if we are not currently painting the marker (due to the marker frame having mMarkedFrame == nullptr).  I couldn't find a crashtest for this, so let's add one.
Attached patch patchSplinter Review
Assignee: nobody → cam
Status: NEW → ASSIGNED
Attachment #755144 - Flags: review?
Attachment #755144 - Flags: review? → review?(longsonr)
bug 847139 seems to do the same thing doesn't it?
Oh, hmm.  So FindCloserFrameForSelection grew an early return if the frame is non-display, so the test in that bug doesn't crash any more (if we incorrectly passed in true) since we wouldn't get to the UpdateGlyphPositioning call.

Do you think it is still worth adding this test?
Although given in bug 877035 aForceGlobalTransform will disappear...
Comment on attachment 755144 [details] [diff] [review]
patch

I guess so in that case.
Attachment #755144 - Flags: review?(longsonr) → review+
https://hg.mozilla.org/mozilla-central/rev/6af9d5797340
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Flags: in-testsuite+
Resolution: --- → FIXED
Target Milestone: --- → mozilla24
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: