Closed
Bug 799503
Opened 13 years ago
Closed 13 years ago
b2g's shell.js tries to read a remote iframe's contentWindow (in a number of places)
Categories
(Firefox OS Graveyard :: General, defect)
Firefox OS Graveyard
General
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: justin.lebar+bug, Unassigned)
References
Details
See bug 798580 comment 10 and 11. b2g's shell.js is extremely incorrect in this respect.
| Reporter | ||
Updated•13 years ago
|
blocking-basecamp: --- → ?
| Reporter | ||
Comment 1•13 years ago
|
||
Tim, can you take this bug? I can help explain more what assumptions you need to revert in this code, if you need me to.
Comment 2•13 years ago
|
||
Justin, shell.js only loads the system app, which does not run OOP.
https://mxr.mozilla.org/mozilla-central/source/b2g/chrome/content/shell.js#173 is unfortunately misleading, along with other variables names homescreenXXX (legacy from when we had only one app for system + homescreen)
| Reporter | ||
Comment 3•13 years ago
|
||
Oh, by "homescreen", we don't mean "homescreen"?
I see. :)
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID
Comment 4•13 years ago
|
||
Yep... and I doubt we can basecamp+ a bug about "clean up variables names that confuse jlebar" :P
Updated•13 years ago
|
blocking-basecamp: ? → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•