Here are some ideas we've been talking about on my team: - Figure out CSS WG reftest integration. Right now, there's a python/mercurial build process that turns XHTML files into HTML to run them and it's not clear how to either integrate that without a giant mess (even by servo build standards!) or upstream work we do. I'd like to sort this out so we can have a test experience for layout tests that's similar to that of the DOM / WPT tests, especially for E-Easy bugs.
- Perf testing for some basic scenarios along with reporting. Anything we make an explicit perf goal for this quarter (such as the interactions/gestures/network/graphics you mention below) I'd like to have some sort of test for (unless it's just for a one-off demo). Rust upgrades tend to regress our performance work otherwise. - Emulator-based testing for Android & Gonk Just a basic page load to ensure there aren't things like the OpenSSL library loading bugs, especially now that there's an Android nightly APK up there :-) - Critical features blocking many pages Need that flexbox. There were some scheduling snafus with it this quarter, but I think we need to be working on it in Q2 just to be able to build or view more pages, even if much of the team is working on perf/bugfixing. html5ever is going to need document.write for many pages to work. - SM Upgrade I'd also like to do whatever we can to support jdm with his pending SpiderMonkey upgrade, maybe even treating it like a rustup. - Lars On Mar 18, 2015, at 12:15 PM, Jack Moffitt <j...@metajack.im> wrote: It's about time to start planning and setting goals for Q2, and as I mentioned in this week's meeting, I think focusing on usability and performance tasks would be appropriate. I assume that a few people will keep pushing features forward this quarter, especially as there are several multi-quarter projects in flight, but the idea is that most of our effort will be directed to usability and performance. Here is an (unordered) list of possible projects: - Implement CSS 3D transforms and make the CSS FPS (http://keithclark.co.uk/labs/css-fps/) run at full speed. This could be a compelling demo since other browsers fare poorly. Another example of this is - Get jQuery's test suite passing in Servo - Get React working in Servo - Find and fix bugs relating to extra reflows and incremental layout - Get multiple resource loading working well enough that page load times are competitive - Implement the Timeline debugging protocol so that we can get timeline reports from Firefox debug tools for Servo - Get basic interactions and gestures polished: scroll performance on Linux, OS X, and Android; pinch zoom; interactive window resizing; etc - Create compelling demos that benefit from Servo performance or tech and satisfy real user needs. Example: Patrick has been working on a text-zoom demo that very fast in Servo and not great elsewhere; it is a solve real user problems on mobile devices. - Tune performance in networking and graphics. - Polish the new HTML-based browser shell (landing soon) and get it working well on all platforms - Find slow interaction patterns and make them fast. Examples: Twitter infinite scroll is janky in other browsers; an isolated demo of this would make a good first dynamic test suite addition. Make them smooth in Servo. There are probably some layout and other bugs that need addressing too. The iframe and constellation refactoring that happened in Q1 is a good example of that kind of work. I'd love to hear what other ideas people have as well. jack. _______________________________________________ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo _______________________________________________ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
