Meeting 2015 10 05

Agenda items

list of browser.html bugs sorted by priority: https://github.com/mozilla/browser.html/issues/562 (paul)
Starting Q4 planning: https://etherpad-mozilla.org/Servo-Q4-2015 (jack, larsberg)

larsberg, edunham, SimonSapin, pcwalton, Manishearth, jdm, jack, mbrubeck, mrobinson

mbrubeck: The browser.html repo has a tracking issue with the priorities of Servo bugs. It exists and they're updating it regularly. Should we triage the P1 issues to get them addressed?
jack: Can try to go through them quickly to see who's on them. First 4 are stacking issues; pcwalton on them?
pcwalton: I've looked at them, but haven't been working on them. Working on e10s and webrender lately. I can do so.
jack: Stacking, issues, and iframes - probably a mix of pcwalton, gw, and mrobinson. Maybe get these assigned?
pcwalton: I can look at a couple of them today.
jack: Put comments in relevant bugs! Other two are .ico support (us needing to implement one) and transform perspectives, which is probably a bug for gw.
mbrubeck: I was thinking about looking at .ico decoding. Could try to upstream to gecko, too, if it was pure rust.
SimonSapin: CSSWG asked Microsoft to publish a spec for ICO or any kind of docs, but they were unwilling or unable to do so, so we’ll have to rely on random blog posts or reverse engineering
jack: Why is ICO p1?
larsberg: probably favicons in tabs
jdm: I suspect we could do an ICO decoder into a canvas would be straightforward for browser.html.
jack: I think ms2ger was going to revamp navigation. In other words, if you're bored, dig in! Be nice to get further along. Everything on P1 needs to be done by december.
mrobinson: I'm already working on most of the stacking issues today...

jack: This has started! As always, a few days into Q4. Have talked to many of you; need to get those entered. Also, we have an etherpad so that people can see what all of the moz staff are on the hook for. I don't think anybody has them entered in WorkDay yet, but once we do get them filled out, we can do so.
jack: We've added other staff who aren't reporting into research that have deliverables, in order to keep things coordinate.

pcwalton: Since it's working and behind a flag, maybe merge to master?
manish: Yes.
larsberg: Can we run some reftests in webrender mode?
pcwalton: Not all things are implemented, so not the whole thing yet.
jdm: Are there things that are a waste to be modifying in master if webrender is the way forward?
pcwalton: Lots of things related to stacking contexts & iframes. But will need that around for PDF regardless, so it's not clear to me. Webrender removes layerization, tiling, and invalidation. Not clear we can get away with this - may need layerization+tiling with Webrender. We have some preliminary evidence, but it's not rigorous. So... it's complicated. There's a good chance we can simplify the layering, tiling, and invalidation code. But we'll need the vector painting code around for printing.
jack: Probably not worth changing what we're working on right now; midway through the quarter we'll have a better idea.

jack: Next week on Monday, Alan Jeffrey starts! Probably will start on Dromaeo stuff. He'll be in the SF office all week (maybe one day down in MTV). People local - please say hello!