Mobile/Notes/28-Jul-2010: Difference between revisions

 
(8 intermediate revisions by 4 users not shown)
Line 37: Line 37:
* {{bug|573635}} has two ways to resolve it, and we have patches for both. Neither is perfect but a perfect solution requires fundamental work on IPC networking. So for now, just need to decide which of the 2 patches to go with.
* {{bug|573635}} has two ways to resolve it, and we have patches for both. Neither is perfect but a perfect solution requires fundamental work on IPC networking. So for now, just need to decide which of the 2 patches to go with.
* place bugs getting closer to land.
* place bugs getting closer to land.
* necko e10s reviews going faster. (12 patches in review state, 1 ready to push)
* removing real widgets soon in the child process
* window.crypto
* lots of warnings+errors in startup


== General Platform ==
== General Platform ==
Line 85: Line 89:


== QA ==
== QA ==
* Client
=== Manual ===
* bugs [http://bit.ly/9o15HO filed] on the Fennec product over the past week
* Fx Input is mobile ready and will be pushed live tomorrow.
* working on triaging broken/unclear/failed test reports on litmus
* ahoza will be working on Find in page functionality testing
* Dates/Times related to Alpha 1?
* bug notes
** {{bug|579349}} - is still a blocker for testing
** {{bug|581532}} - Pages now load again with browser.tabs.remote=true, so testing again with that enabled. I'm getting crashes when closing tabs, in that case, though.
** (mw22) Found {{bug|582242}} crasher. It seemed to be Windows only, though.


* Automation
=== Automation ===
** Android
** Android
*** Landed everything for mochitest/reftest on m-c
*** Landed everything for mochitest/reftest on m-c
Line 95: Line 108:


** Browser-Chrome {{bug|553474}}
** Browser-Chrome {{bug|553474}}
*** tons of fixes to get tests working in e10s
*** handful of fixes to get tests working in e10s (thanks mfinkle, vingtetun)
*** lots of progress on new tests
*** lots of progress on new tests
*** still have an issue with 'too much recursion' causing all the tests to timeout
*** still have an issue with 'too much recursion' causing all the tests to timeout
Confirmed users
6,361

edits