Closed Bug 1662222 Opened 5 years ago Closed 5 years ago

Don't spin the event loop in nsPrintJob::DoCommonPrint when called by extensions

Categories

(Core :: Printing: Setup, task, P2)

task

Tracking

()

RESOLVED FIXED
82 Branch
Tracking Status
firefox82 --- fixed

People

(Reporter: jwatt, Assigned: jwatt)

Details

(Whiteboard: [print2020_v82][old-ui-])

Attachments

(1 file)

In https://phabricator.services.mozilla.com/D88703 I'm adding a settingsAreComplete check to avoid spinning the event loop to fetch settings from the parent process when the new print UI is enabled. To reduce risk for Beta uplifts I've added an extra printSilentOnSettings check there so that we do continue to spin the event loop for calls from extensions, in order to avoid changing behavior there. I'm pretty sure that won't cause extensions problems though, and we also need to stop spinning the event loop for them to get rid of that code. We should do that after we've finished churning this code with patches we may want to uplift to Beta 81.

Whiteboard: [print2020_v82][old-ui-]
Attachment #9174805 - Attachment description: Bug 1662222. Don't spin a tested event loop in nsPrintJob::DoCommonPrint when called by extensions. r=emilio → Bug 1662222. Don't spin a nested event loop in nsPrintJob::DoCommonPrint when called by extensions. r=emilio
Pushed by jwatt@jwatt.org: https://hg.mozilla.org/integration/autoland/rev/268968002315 Don't spin a nested event loop in nsPrintJob::DoCommonPrint when called by extensions. r=emilio
Status: NEW → RESOLVED
Closed: 5 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: