State of the Union

• Content processes in Fennec in 4 now working on desktop
• build with special flag to cut out features/code that doesn't work with multiple processes
  • needed place to start and give a build to dev tools and a11y
  • every feature/code that is disabled has a bug filed
  • may have Q4 goal to remove this flag, have startup flag after this
• working on frontend features
• dynamic analysis that produces useful info - can tell where chrome touches content in a negative way - good for frontend team
• bunch of people on frontend team working on big ticket items
• backend tasks remain that affect desktop
  • plugins - chris jones
  • a11y - dave bolter, basic a11y works, mvda works, some bugs with other screen readers isimpledom, bugs that are less important but will be more important when we get to sandboxing, high priority bugs for user experience that will block release in a sandbox situation, these are all p2s remaining
    • we do care about responsiveness, no bugs that fit within this theme
    • just unblocked in terms of proper qa
    • need to fix the other screen readers before we can release
    • haven't tested atypical users, robots and extensions that use our api
    • blocked by bug 693644
• dev tools
  • web console e10s being worked on with message manager, progressing well, hoping to land for 10
  • highlighter hasn't started but looking into it (essentially everything else), linked browser support, don't expect to take too long, probably this quarter, maybe next
  • debugger script debugger will get turned on in aurora next quarter
  • firebug evaluating different options, looking at throwing all of firebug into linked browser (open iframe to run in same process as that process over there and give access to that shell), already runs in an iframe, doesn't know how long will take to get to this point
    • there are extensions to firebug, do you know if any of those are being looked at? will need to follow up next time dave? speaks with him.
    • firebug may be a single process add-on, 2.5 million adus for firebug from amo
    • if we have to eol support for firebug we need to achieve product parity, extraordinarily important to protect this user base, need a path for firebug users
    • would be helpful for dev tools team to know how much work we need to put into firebug
• extensions
  • dave herman, static analysis
    • research intern build static analysis engine, only knew JS, adapted this past summer to get more including DOM, spidermonkey js extensions, ...
    • frontend work mostly done
    • starting to stabilize, still 1000-2000 add-ons that crash analysis
    • add-ons that use e4x can't be analyzed - some big ones including ad block plus use this
    • hoping to get to all add-ons within next couple of weeks.
    • need to ask how accurate and how useful the numbers are
    • spot check of a sample of static analysis to see how accurate it is
    • need big picture and rough estimate (blizard)
    • dave will get back with us in a couple of weeks to see how we're doing and whether there are analytical issues
    • think about how to productize these tools, companion to current add-on compat tools
  • compatiblity shim is an extension issue that will need some lead time (jp), implies that we still need to support a single process mode (blizard)
  • likely at least 3-12 months to support single process mode
    • could release ff with content processes once most of our users can use it, ex most popular add-ons working, turn content processes off for rest, don't know scope of the problem, how many add-ons we need to be compatible

• fxe10s for bug tracking
• bliz spoke with clint about responsiveness, want to make sure work on e10s will improve responsiveness, can tell how long browser is unresponsive, did the browser become unresponsive while running a test, how do we test in real world scenarios,

• Lawrence to pay attention to jetpack sdk (dave mason) related to e10s, if it is going to compeltely change direction to be compatible with java fennec it may mean that they are not focused on current multi process which may affect desktop firefox