Closed
Bug 1104400
Opened 10 years ago
Closed 10 years ago
[AccessFu] content-script.js does not get loaded into app frames in Mulet
Categories
(Core :: Disability Access APIs, defect)
Core
Disability Access APIs
Tracking
()
RESOLVED
FIXED
mozilla36
People
(Reporter: eeejay, Assigned: eeejay)
Details
Attachments
(1 file, 1 obsolete file)
|
2.66 KB,
patch
|
yzen
:
review+
|
Details | Diff | Splinter Review |
This is because there is another layer of embedding. The shell chrome document is loaded as a content document in the browser, and every iframe is one level deeper.
In other words, before it was
- xul browser tab
- system app
- app frame
- app frame
- ...
Now it is
- xul browser tab
- shell.html chrome
- system app frame
- app frame
- app frame
- ...
| Assignee | ||
Comment 1•10 years ago
|
||
Attachment #8528059 -
Flags: review?(yzenevich)
Comment 2•10 years ago
|
||
Comment on attachment 8528059 [details] [diff] [review]
Get all message managers in Mulet setup.
Review of attachment 8528059 [details] [diff] [review]:
-----------------------------------------------------------------
I tried running the tests and they seem to stopped working. In particular try test_alive one. I am getting:
Error this.win.content.shell is undefined resource://gre/modules/accessibility/Utils.jsm:183
Attachment #8528059 -
Flags: review?(yzenevich)
| Assignee | ||
Comment 3•10 years ago
|
||
Oops, indeed. Mulet doesn't support a11y mochitests yet.
Attachment #8528059 -
Attachment is obsolete: true
Attachment #8528495 -
Flags: review?(yzenevich)
Comment 4•10 years ago
|
||
Comment on attachment 8528495 [details] [diff] [review]
Get all message managers in Mulet setup.
Review of attachment 8528495 [details] [diff] [review]:
-----------------------------------------------------------------
r=me thanks!
Attachment #8528495 -
Flags: review?(yzenevich) → review+
| Assignee | ||
Comment 5•10 years ago
|
||
Comment 6•10 years ago
|
||
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla36
You need to log in
before you can comment on or make changes to this bug.
Description
•