Policies: override or disable update page

VERIFIED FIXED in Firefox 60

Status

()

defect
P1
normal
VERIFIED FIXED
a year ago
a year ago

People

(Reporter: Felipe, Assigned: Felipe)

Tracking

Trunk
Firefox 61
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox59 unaffected, firefox60+ verified, firefox61 verified)

Details

Attachments

(1 attachment)

(Assignee)

Description

a year ago
There's a policy request to display a custom page (or no page) on the "what's new" page that is defined through the update XML.

There's a pref to provide a default fallback if the update XML didn't provide it, but it won't be used if one was provided.

Adding this policy will be relatively straightforward here: https://searchfox.org/mozilla-central/rev/30ead7d1ae5bf95b8bc0fd67b950cd46ca05e32c/browser/components/nsBrowserContentHandler.js#142
(Assignee)

Updated

a year ago
Depends on: 1436377
Assignee: nobody → ksteuber
It looks like this bug is not a priority at the moment, so I am going to work on other bugs that are. Hopefully I will be able to come back to this one afterwards.
Assignee: ksteuber → nobody
(Assignee)

Updated

a year ago
No longer blocks: policies-mvp
(Assignee)

Updated

a year ago
Assignee: nobody → felipc
Blocks: policies-mvp
Status: NEW → ASSIGNED
Comment hidden (mozreview-request)

Comment 3

a year ago
mozreview-review
Comment on attachment 8964147 [details]
Bug 1429122 - Policy: Override or disable post-update (what's new) page.

https://reviewboard.mozilla.org/r/232910/#review238468

::: browser/components/enterprisepolicies/tests/browser/browser.ini:46
(Diff revision 1)
>  [browser_policy_disable_shield.js]
>  [browser_policy_disable_telemetry.js]
>  [browser_policy_display_bookmarks.js]
>  [browser_policy_display_menu.js]
>  [browser_policy_extensions.js]
> +[browser_policy_override_postupdatepage.js]

This new test file doesn't seem to have made it into the patch.
Comment hidden (mozreview-request)

Comment 5

a year ago
mozreview-review
Comment on attachment 8964147 [details]
Bug 1429122 - Policy: Override or disable post-update (what's new) page.

https://reviewboard.mozilla.org/r/232910/#review238880
Attachment #8964147 - Flags: review?(mhowell) → review+

Comment 6

a year ago
Pushed by felipc@gmail.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/812669a17937
Policy: Override or disable post-update (what's new) page. r=mhowell
(Assignee)

Comment 7

a year ago
[Tracking Requested - why for this release]:
Enterprise Policies

Comment 8

a year ago
bugherder
https://hg.mozilla.org/mozilla-central/rev/812669a17937
Status: ASSIGNED → RESOLVED
Last Resolved: a year ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 61
We tested this on Nightly with JSON policy format and it is verified as fixed.

Using this policy, "what's new" page can be set to a website or no page.

It will also be tested with adm formats when ready.
Test cases and runs are here- https://testrail.stage.mozaws.net/index.php?/plans/view/8760
(Assignee)

Comment 10

a year ago
Comment on attachment 8964147 [details]
Bug 1429122 - Policy: Override or disable post-update (what's new) page.

Approval Request Comment
[Feature/Bug causing the regression]: Enterprise Policies
[User impact if declined]: Policy to choose or disable the "What's New" page when Firefox updates
[Is this code covered by automated tests?]: yes
[Has the fix been verified in Nightly?]: yes
[Needs manual test from QE? If yes, steps to reproduce]: -
[List of other uplifts needed for the feature/fix]: none
[Is the change risky?]: no
[Why is the change risky/not risky?]: limited to this policy being used, simple pref config
[String changes made/needed]: none
Attachment #8964147 - Flags: approval-mozilla-beta?
Comment on attachment 8964147 [details]
Bug 1429122 - Policy: Override or disable post-update (what's new) page.

enterprise policy for 60, approved for 60.0b11
Attachment #8964147 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
We retested this on beta builds with ADM and JSON policy formats and it is verified as fixed.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.