Jetpack/Weekly Meeting/2014-05-13: Difference between revisions
< Jetpack | Weekly Meeting
Jump to navigation
Jump to search
(→Agenda) |
(→Agenda) |
||
| Line 21: | Line 21: | ||
*** afaict, the original assumption when designing jetpack APIs was that a DOM window was going to be a barrier between Parent and Child processes (not true) | *** afaict, the original assumption when designing jetpack APIs was that a DOM window was going to be a barrier between Parent and Child processes (not true) | ||
*** different code paths for xul:iframes not inside tabs? (they are not remote) | *** different code paths for xul:iframes not inside tabs? (they are not remote) | ||
*** i'm in maze of twisty little nsIInterfaces all alike | *** i'm in a maze of twisty little nsIInterfaces, all alike | ||
* Roundtable | * Roundtable | ||
Latest revision as of 16:25, 13 May 2014
Agenda
- Introductions
- Zombie
- Connor
- High Priority Work
- SDK
- Blockers?
- E10S (zombie)
- questions from last week
- E10S stuff should not break Fennec (modulo my mistakes)
- Frame Scripts run with chrome Principal, but we have Components/Sandbox
- first e10s (smoke) test running on CI (and passing ;)
- the more i learn about E10S, the less i'm sure in my first proposed approach
- (was: attach small Frame Script that forwards messages across boundaries)
- afaict, the original assumption when designing jetpack APIs was that a DOM window was going to be a barrier between Parent and Child processes (not true)
- different code paths for xul:iframes not inside tabs? (they are not remote)
- i'm in a maze of twisty little nsIInterfaces, all alike
- questions from last week
- Roundtable
Bugs
Triage Followups
No results.
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);
Open Bugs
Bugzilla query error
Invalid type (count) and display (table) combination1