825082 - Write a test for bug 824177

Status: RESOLVED WONTFIX

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

Description

[Chris Jones [:cjones] inactive; ni?/f?/r? if you need me]

+++ This bug was initially created as a clone of Bug #824177 +++

I asked around and it sounds like writing a direct test of bug 824177 (checking containing app IDs) is rocket science.

So we'd need to write the indirect test of making an HTTP request from an opened browser window, but the HTTP checks are disabled for dom/browser-element.

So I'm not sure how to do this :/.

Comment 1

[Josh Matthews [:jdm]]

The checks are disabled because the necko folks haven't audited necko to ensure that the app-less browser is properly supported. Once that work happens they can be turned on again (and presumably the abort necessitating their disabling removed).

Comment 2

[JP Rosevear [:jpr]]

bb+ came from clone re-nomming because test itself probably doesn't block.

Comment 3

[Chris Jones [:cjones] inactive; ni?/f?/r? if you need me]

Yeah my b.

Comment 4

[Justin Lebar (not reading bugmail)]

> I asked around and it sounds like writing a direct test of bug 824177 (checking 
> containing app IDs) is rocket science.

To repeat my comment from bug 824177, I'm pretty sure we have existing tests which allow content to read its own app-id.

Is the issue that we need to read the /containing/ app-id from content?

Comment 5

[Chris Jones [:cjones] inactive; ni?/f?/r? if you need me]

Yes, at the end of bug 824177 comment 10, we would need to ask the opened window what it's containing app ID is.

Comment 6

[Chris Jones [:cjones] inactive; ni?/f?/r? if you need me]

*its

Comment 7

[BugBot [:suhaib / :marco/ :calixte]]

In the process of migrating remaining bugs to the new severity system, the severity for this bug cannot be automatically determined. Please retriage this bug using the new severity system.