Confirm
471
edits
Changes
→Minutes
*** also good to learn how E10S impacts our APIs, so we don't need to break too many APIs. In particular, content-manipulating APIs are the most sensitive to E10S effects.
*** how much confidence can we have around not breaking the APIs we ship in 0.5?
*** two separate goals: E10S proof-of-concept, API subsetting (creating an E10S-compliant subset of each API)
*** API subsetting: Brian can help each API owner to change them to be E10S-compliant. Brian is nominal owner.
*** proof-of-concept is a project goal, not a release goal for 0.5
** marking chrome-auth packages
*** at-risk, atul says pre-E10S world is feasible, needs separate principals, may not be appropriate for 0.5. This week brian will figure out how much work is involved, decide whether to aim for 0.5 or to punt for later
** pagemods (nickolay): he's been active, not sure how much progress has been made
** single UI element (dietrich): boriss will have UI designs by this friday. First cut is a statusbar-like thing.
= Followups =
