Closed
Bug 825082
Opened 12 years ago
Closed 2 years ago
Write a test for bug 824177
Categories
(Core :: DOM: Core & HTML, defect, P2)
Tracking
()
RESOLVED
WONTFIX
blocking-basecamp | - |
People
(Reporter: cjones, Unassigned)
References
Details
(Whiteboard: [feedback])
+++ 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•12 years ago
|
||
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•12 years ago
|
||
bb+ came from clone re-nomming because test itself probably doesn't block.
blocking-basecamp: + → ?
Updated•12 years ago
|
Blocks: browser-api
Comment 4•12 years ago
|
||
> 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?
Reporter | ||
Comment 5•12 years ago
|
||
Yes, at the end of bug 824177 comment 10, we would need to ask the opened window what it's containing app ID is.
Reporter | ||
Comment 6•12 years ago
|
||
*its
Updated•12 years ago
|
Whiteboard: [feedback] → [feedback][apps-automation]
Updated•12 years ago
|
Component: DOM: Apps → DOM
Whiteboard: [feedback][apps-automation] → [feedback]
Updated•7 years ago
|
Severity: normal → major
Priority: P1 → P2
Assignee | ||
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
Comment 7•2 years ago
|
||
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.
Severity: major → --
Updated•2 years ago
|
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•