146.60 KB, image/png
1.18 KB, patch
|Details | Diff | Splinter Review|
In Firefox 42.0 and 43.0 there are no longer any options to make Firefox the default browser and to check if Firefox is the default browser in the General panel of the Preferences. I also couldn't find them anywhere else. I observed this in the Linux64 versions of Firefox, running on Xubuntu 15.04. This may or may not affect other platforms too. There was a conversation on Twitter about this issue prior to me filing this bug report: https://twitter.com/mpopp75/status/631595763437584384
[Tracking Requested - why for this release]: Unable to make default browser, regression since Firefox42
Pushlog: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=1ee54e043b9b&tochange=939320b957c5 Regressed by: 939320b957c5 Mike Hommey — Bug 1186003 - Switch automated builds to Gtk+3. r=mshal
This is the trivial fix for this.
Attachment #8653839 - Flags: review?(karlt)
Comment on attachment 8653839 [details] [diff] [review] Set HAVE_SHELL_SERVICE when preprocessing in-content prefs on Gtk+3 builds There was I assuming we'd finally fixed the nagging :)
Attachment #8653839 - Flags: review?(karlt) → review+
Comment on attachment 8653839 [details] [diff] [review] Set HAVE_SHELL_SERVICE when preprocessing in-content prefs on Gtk+3 builds Approval Request Comment [Feature/regressing bug #]: Regression from the combination of bug 879760 and bug 1186003. [User impact if declined]: In-content preferences don't have the items to set Firefox as default browser (non in-content prefs do, however, but they're not enabled by default) [Risks and why]: Very low. The patch is a simple thing that was forgotten in bug 879760. browser/components/preferences/moz.build had this change done for non in-content prefs, which is why it still works. This makes in-content prefs on-par with that. [String/UUID change made/needed]: None
Attachment #8653839 - Flags: approval-mozilla-aurora?
Attachment #8653839 - Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
You need to log in before you can comment on or make changes to this bug.