+++ 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 :/.
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).
bb+ came from clone re-nomming because test itself probably doesn't block.
blocking-basecamp: + → ?
Yeah my b.
blocking-basecamp: ? → -
> 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?
Yes, at the end of bug 824177 comment 10, we would need to ask the opened window what it's containing app ID is.
Component: DOM: Apps → DOM
Whiteboard: [feedback][apps-automation] → [feedback]
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.