Closed Bug 1659259 Opened 4 years ago Closed 4 years ago

Internal font-list changes should not trigger frame reconstruction for print/preview documents

Categories

(Core :: Layout: Text and Fonts, defect, P2)

defect

Tracking

()

RESOLVED FIXED
82 Branch
Tracking Status
firefox82 --- fixed

People

(Reporter: jfkthame, Assigned: jfkthame)

References

Details

Attachments

(1 file)

If there's a change to the font list, we trigger frame reconstruction here. But in the case of a static-clone document used for printing or print-preview, this is undesirable because the nsPrintJob is holding weak refs to frames that will get blown away unexpectedly by this reconstruction.

Better to have the prescontext for print/preview docs just ignore the font-list update and keep its existing frame tree.

(I'm not sure it makes sense for print/preview docs to pay attention to any of the prefs changes here, really, but that's a wider question; the font-list update frame reconstruction is the most immediate concern because this can cause failures in some of our print reftests, if the post-startup deferred font info loader happens to complete, triggering a font-list refresh, at exactly the wrong moment during the test.)

Assignee: nobody → jfkthame
Status: NEW → ASSIGNED
See Also: → 1659273
Attachment #9170184 - Attachment description: Bug 1659259 - Don't reconstruct frames as a result of font-list refresh if we're in a printing or print-preview context. r=jwatt → Bug 1659259 - Don't reconstruct frames as a result of font-list refresh if we're in a printing or print-preview context. r=emilio
Pushed by jkew@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/ac29f8757e96 Don't reconstruct frames as a result of font-list refresh if we're in a printing or print-preview context. r=emilio
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → 82 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: