[dev-servo] 9/23 meeting - leaks, crashes, reflow performance, demos
https://github.com/mozilla/servo/wiki/Meeting-2013-09-23 If people familiar with layout could read over Patrick's assumptions about Gecko layout and confirm/deny, that would be great. ___ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
Re: [dev-servo] 9/23 meeting - leaks, crashes, reflow performance, demos
On 9/23/13 1:44 PM, Josh Matthews wrote: https://github.com/mozilla/servo/wiki/Meeting-2013-09-23 Fwiw, lots of proxies (e.g. document.forms) are definitely long-lived I realize that's more of a long-term concern, and we need trace hooks for proxies a If people familiar with layout could read over Patrick's assumptions about Gecko layout and confirm/deny, that would be great. > believe that page is large, partway through parsing it starts reflow, > then reflows rest later. That can definitely happen. Even for non-large pages, depending on scripts and stuff. > seems accurate way to measure reflow is to sum time of both. It really depends on what you're measuring. There's reflowing during pageload (which involves heuristics for when to do it and nondeterminism), which obviously affects pageload performance. There's reflowing in response to scripted changes, whether due to a layout flush from script or not. It's hard to say more here without seeing the actual testcase being measured. -Boris ___ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
Re: [dev-servo] 9/23 meeting - leaks, crashes, reflow performance, demos
Le 23/09/2013 19:44, Josh Matthews a écrit : https://github.com/mozilla/servo/wiki/Meeting-2013-09-23 jack: strange loop seemed really impressed that we had anything to show at all. general impression seems to be vapourware. That's quite an unfortunate impression :-s kmc: did you show acid1? jack: no. we should at summit. I don't know what works and what doesn't now, but it could be nice to have some high-profile websites working, like Facebook, Twitter, Google Search, etc. I've read something about Wikipedia in the notes. What about the Servo meeting notes on Github? A website using the default Twitter Bootstrap theme? mozilla.org? At least the manifesto page? I understand the importance of the acid1/2/3 milestones, but I think people will be more impressed when they see real-life pages display correctly (regardless of how hard and how many features compose the page). I think this is what will move the perception from "research project" to something people can actually connect with (in the emotional sense, not the HTTP sense). Note that high-profile websites might be easy to do as they probably still target IE6/7 (which don't even pass acid2!). Mobile versions of high-profile websites might use less CSS/JS features than desktop versions. David ___ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
Re: [dev-servo] 9/23 meeting - leaks, crashes, reflow performance, demos
nsBlockReflow, and most layout code, is indeed inefficient. Some amount of that is because we support a lot of features and we've fixed a lot of bugs. Fixing bugs tends to add code, and even if you try to keep things off commonly taken paths, even not-taken conditionals add up. I guess I'm saying that you really want to be quite a bit faster than Gecko because over time you'll gradually slow down as you are able to handle more of the Web. Although, since we have better specs and better understanding of their implementation than we did as Gecko evolved, there's some hope Servo will end up less crufty. Rob -- Jtehsauts tshaei dS,o n" Wohfy Mdaon yhoaus eanuttehrotraiitny eovni le atrhtohu gthot sf oirng iyvoeu rs ihnesa.r"t sS?o Whhei csha iids teoa stiheer :p atroa lsyazye,d 'mYaonu,r "sGients uapr,e tfaokreg iyvoeunr, 'm aotr atnod sgaoy ,h o'mGee.t" uTph eann dt hwea lmka'n? gBoutt uIp waanndt wyeonut thoo mken.o w * * ___ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
