Interviewed by CNN on 14/12/2012 10:43, MCBastos told the world: > I recently ran into this blog post by Nick Cameron: > > <http://featherweightmusings.blogspot.com/2012/12/how-to-win-benchmarks-and-influence.html> > > It's an interesting read about artificial benchmarks, but on checking > the results in my computer one thing sprang out: > I got very good results in Firefox 17, but very poor results in > Seamonkey 2.14. From Cameron's explanation, the difference is related to > whether the browser is using Windows Direct2D or not. > > I thought that (using Direct2D) was a Gecko feature that is shared > between Firefox and Seamonkey. Am I wrong? Or is it a matter of flipping > the appropriate switches in about:config? >
Addendum: apparently it was the about:config option gfx.direct2d.disabled that was set to "true." I reset it to the default value, and it became "false," and the performance in the suspect benchmark improved noticeably. I suppose other rendering will become faster too. Thing is, I don't really remember having tweaked that option. It might have happened one or two years ago and I have forgotten about it, of course. But still... - Does anybody remember if there was ever a legitimate reason for disabling Direct2D? - Was it default in earlier versions of Seamonkey (perhaps some known problems)? - If so and if the issue has since been fixed, shouldn't upgrades flip on Direct2D? -- MCBastos This message has been protected with the 2ROT13 algorithm. Unauthorized use will be prosecuted under the DMCA. -=-=- ... Sent from my PalantÃr. * Added by TagZilla 0.7a1 running on Seamonkey 2.14.1 * Get it at http://xsidebar.mozdev.org/modifiedmailnews.html#tagzilla _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
