1175926 - LoadContext and LoadInfo do not match in nsHttpChannel and WebSocketChannel - tests failing

Status: RESOLVED INVALID

(Core :: DOM: Core & HTML, defect)

Description

[Dragana Damjanovic [:dragana]]

There are some tests failing:

1) assert InBrowserElementContext == isInBrowserElementLoadInfo fails, 
nBrowserElementContext is true - isInBrowserElementLoadInfo is false:

caps/tests/mochitest/test_app_principal_equality.html 
dom/events/test/test_bug1096146.html
dom/permission/tests/test_browser.html
browser/components/sessionstore/test/browser_privatetabs.js
browser/components/privatebrowsing/test/browser/browser_privatebrowsing_concurrent.js
.... and many more :)

2) InBrowserElementContext == isInBrowserElementLoadInfo
appIdContext == 1, appIdLoadingPrincipal == 0:

dom/tests/mochitest/localstorage/test_appIsolation.html
caps/tests/mochitest/test_principal_jarprefix_origin_appid_appstatus.html 
...

Comment 1

[Dragana Damjanovic [:dragana]]

https://treeherder.mozilla.org/#/jobs?repo=try&revision=6191ba6018d3

Comment 2

[Dragana Damjanovic [:dragana]]

Principal is SystemPrincipal frame owner is app.

Comment 3

[Dragana Damjanovic [:dragana]]

typo in the description:

under 2) it should be: "check appIdContext == appIdLoadingPrincipal is failing"

Comment 4

[Jonas Sicking (:sicking) No longer reading bugmail consistently]

Hi Dragana,

Anything I can help with to move this bug forward?

Comment 5

[Dragana Damjanovic [:dragana]]

I am going to close this bug. A fix for this bug will be made in bug 1125916, because both changes need to land at the same time.