(In reply to Ciprian Muresan [:cmuresan], Ecosystem QA from comment #4) > @jwatt, could you please take a look at this issue? Is there anything in bug 1667953 that could have caused this? Thanks for doing the bisect. Yes, given what we know now, it makes perfect sense that bug 1667953 would cause this. The issue that is when `print_printer` hasn't been set (the user hasn't printed before) we **implicitly** save the print settings **unprefixed** when saving them in order to pass settings to the content process. Since https://phabricator.services.mozilla.com/D91819 made us ignore most unprefixed prefs in nsPrintSettingsService::InitPrintSettingsFromPrefs, we now fail to pick up those "passed settings" in the content process.
Bug 1669187 Comment 5 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Ciprian Muresan [:cmuresan], Ecosystem QA from comment #4) > @jwatt, could you please take a look at this issue? Is there anything in bug 1667953 that could have caused this? Thanks for doing the bisect. Yes, given what we know now, it makes perfect sense that bug 1667953 would cause this. The issue is that when `print_printer` hasn't been set (the user hasn't printed before) we **implicitly** save the print settings **unprefixed** when saving them in order to pass settings to the content process. Since https://phabricator.services.mozilla.com/D91819 made us ignore most unprefixed prefs in nsPrintSettingsService::InitPrintSettingsFromPrefs, we now fail to pick up those "passed settings" in the content process.