Vlad Lucaci, Desktop QA (:vlucaci) Reporter
	Description • 6 years ago

[Affected versions]:
-60 ESR
-61.0a1 Nightly
-60b16 

[Affected platforms]:
-Windows 10x64

[Steps to reproduce]:
1.Create a "distribution" folder in the Firefox folder.
2.Copy the contents of the Preconditions of T463278 in a json file and name it "policies" inside the "distribution folder"
3.Set the "BlockAboutConfig" in the json file to True and restart browser.
4.Go to any About: url.


[Expected result]:
-about:config,about:support,about:profiles, about:addons should all be blocked.

[Actual result]:
-It can be noticed that none of the about: pages are blocked.

[Additional notes]:
-I have tried to reproduce this issue on multiple platforms, different hardware configurations and the only one on which this issue can be reproduced is the following:

Win 10x64 Build 16299
Processor: AMD FX 8320 Eight Core Processor 8cpu ~3.5GHz
Memory: 16 gb
DirectX:12
ATI Radeon 3000

On two PC's with the same configuration I have managed to reproduce this issue with 100% repro rate all screens on one, and on the other one, only the About:Config screen is not blocked with 100% repro rate.

	Vlad Lucaci, Desktop QA (:vlucaci) Reporter
	Comment 1 • 6 years ago

Will return with a regression range link ASAP.

	Mike Kaply [:mkaply]
	Comment 2 • 6 years ago

> about:config,about:support,about:profiles, about:addons should all be blocked.

If you DisableAboutConfig, only about:config will be disabled. There are separate policies for the other about:pages.

What should be blocked are the chrome versions of those URLS

chrome://global/content/config.xul
chrome://global/content/aboutProfiles.xhtml
chrome://global/content/aboutTelemetry.xhtml
chrome://browser/content/aboutPrivateBrowsing.xhtml
chrome://global/content/aboutSupport.xhtml

See:

https://bugzilla.mozilla.org/show_bug.cgi?id=1453012

But that will not work on 61.

We are working on a patch for that.

	Mike Kaply [:mkaply]
	Comment 3 • 6 years ago

Are you able to reproduce this still?

	Vlad Lucaci, Desktop QA (:vlucaci) Reporter
	Comment 4 • 6 years ago

Hello  Mike,
Sorry for the delayed answer.

I have attempted to reproduce this issue with the latest Beta (64.0b3) and the latest Nightly 65.0a1 (2018-10-23) without any success. 

I have tried to reproduce it on the machine on which I have firstly encountered the issue, and on another machine with the same hardware configuration.

	:Felipe Gomes (needinfo for replies!)
	Comment 5 • 6 years ago

Thanks for re-checking, looks like things are working as expected.