Electrolysis/Meetings/2016-02-04

< Electrolysis‎ | Meetings
Revision as of 16:44, 4 February 2016 by Mconley (talk | contribs) (→‎mconley: Add mconley stuff.)


« previous week | index | next week »

mconley

  • M8 bug 1243720 - [e10s] Firefox doesn't respect colors of high contrast mode for web content (Windows)
    • Patch up and waiting on review.
  • P1 bug 1195295 - content-sessionStore.js sends a sync message to the parent in SyncHandler.init
    • This has been driving me up the wall. Posted my findings towards the end - hoping to get mccr8's help.
  • bug 1231422 - Intermittent browser_async_window_flushing.js | We should not have added the window to the closed windows array - Got 1, expected 0
    • Posted a patch, waiting on review.
  • bug 1157404 - [e10s] Possible to end up with two visuallyselected="true" tabs at the same time
    • Patch reviewed, just need to address comments and land.
  • Helping to do UX intern interviewing
  • Reviewing lots of things

bobowen

  • bug 1193861 - We don't get content processes logged on windows - up for review.
  • bug 1219369 - Leak checking does not work in Windows content processes due to being unable to create the bloat log - reviewed, waiting for bug 1193861.
  • bug 1173371 - [e10s] Web page is not shown when launch Firefox from network drive on Windows - landed.
  • bug 1236015 - File menu>Print>Microsoft Print to PDF always results in ERROR - this only seems to happen on Win10 (although I need to check Win8). On Win10 (with 32-bit Firefox) instead of creating a low integrity 64-bit spool helper process the Printer Spooler service creates a medium integrity one, but it still picks up the access token settings from the sandboxed job. This helper then gets used by the main process (and other apps as well) and fails because of the USER_INTERACTIVE settings. I think I just need to get rid of print device access from the content process. Fortunately this doesn't block getting low integrity to Aurora, which I thought it was going to.
  • bug 1245246 - crash in nsPrintEngine::FirePrintingErrorEvent - user had this while testing bug 1236015 for me. Simple null deref - patch landed, will ask for uplift.

gw280

  • bug 1239698 - PScreenManager IPC crash. Spent quite a bit of time looking into this, but didn’t really get anywhere. Ended up asking billm for pointers and he thinks it’s related to the work he’s currently doing, so he took it.
  • bug 1179732 - Tresize. Re-triaged as P2 after the fixes to the addon to bring measurements to almost parity on Windows/OS X. I spent a bit of time trying to work out why the test data shows two trends in the non-e10s case but didn’t get very far. I can’t reproduce it locally.
  • bug 1213432 - currently looking at this, but nothing really to report yet. I have a hunch it might be related to bug 1213429 (d3d9 makes scrolling slower on fb).

felipe