Bug 1844609 - Stop browser_linkHandler.js attempting to contact an outside server. r=freaktechnik

I'm not sure why upgrading a request from http://example.org:8000/favicon.ico to https://example.org:8000/favicon.ico
triggers the external load assertion (surely it resolves to the same place regardless of the request type) but it does.

Differential Revision: https://phabricator.services.mozilla.com/D184540

--HG--
extra : rebase_source : 6c4377874cb98556648634f90dd4f8a77d381326
extra : amend_source : d35770417ef98b28ff87354b6862b62d90e5ece6
This commit is contained in:
Geoff Lankow 2023-07-25 13:00:37 +12:00
Родитель 1e09a00d26
Коммит e8e2d952cd
1 изменённых файлов: 12 добавлений и 0 удалений

Просмотреть файл

@ -128,6 +128,14 @@ let mockExternalProtocolServiceCID = MockRegistrar.register(
mockExternalProtocolService
);
// This test deliberately loads content from http:// URLs. For some reason
// upgrading the icon URL to https:// causes it to attempt loading from an
// external server and this makes the test crash.
Services.prefs.setBoolPref(
"security.mixed_content.upgrade_display_content",
false
);
registerCleanupFunction(() => {
let tabmail = document.getElementById("tabmail");
Assert.equal(tabmail.tabInfo.length, 1);
@ -137,6 +145,10 @@ registerCleanupFunction(() => {
}
MockRegistrar.unregister(mockExternalProtocolServiceCID);
Services.prefs.clearUserPref(
"security.mixed_content.upgrade_display_content"
);
});
async function clickOnLink(