Jetpack/e10s: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 1: Line 1:
= e10s updates from zombie =
= E10S updates from zombie =
* will be doing these updates every weekly meeting, 1-2 minutes max
* questions from last week
** read-only this week, trying to get on Vidyo proper (halp?)
** E10S stuff should not break Fennec (modulo my mistakes)
* [https://bugzilla.mozilla.org/show_bug.cgi?id=1004745 e10s, the sequel - back from the dead]
** Frame Scripts run with chrome Principal, but we have Components/Sandbox
** this is my e10s tracking bug. there are many like it, but this one is mine.
* first e10s (smoke) test running on CI (and passing ;)
* [https://bugzilla.mozilla.org/show_bug.cgi?id=1004833 resurect cfx --e10s and add a package.json flag]
** [https://bugzilla.mozilla.org/show_bug.cgi?id=1004833 resurect cfx --e10s and add a package.json flag]
** patch submitted, waiting for review
* the more i learn about E10S, the less i'm sure in my first proposed approach
* what to do with all the old e10s bugs?
** (attach small Frame Script that forwards messages across boundaries)
** gozala: mass close? most are probably not applicable/relevant..
** 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)
* gabor: content script security with e10s?
** different code paths for xul:iframes not inside tabs? (they are not remote)
** do you know the the story with frame scripts?
** can frame scripts be loaded with different principals? (i didn't find any mention)
** if not now, can you investigate/ask around, probably faster/better than me..
 
blah <span id=abc> </span>


= previous weeks =
= previous weeks =

Revision as of 03:27, 13 May 2014

E10S updates from 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
    • (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)

previous weeks

jetpack weekly meeting notes

Retrieved from "https://wiki.allizom.org/index.php?title=Jetpack/e10s&oldid=976222"