Firefox OS/Comms/Dialer/Sprint/v2.1-S7/20141020-StandupNotes
From MozillaWiki
< Firefox OS | Comms | Dialer | Sprint | v2.1-S7
Contents
Blockers
- 2.1+ bug 1081854 - GAIA follow-up to bug 978639 (for GCF case 31.4.2.1.3)
- Assigned to Tamara.
- Depends on bug 978639, which has landed. This is ready to go.
- 2.1+ bug 1079810 - Empty sound writes into speaker, cause serious power consumption
- Assigned to Doug.
- 2.1- bug 1082876 - TypeError: context is null at: app://callscreen.gaiamobile.org/gaia_build_defer_index.js line: 84
- Assigned to Gabriele.
- In reality is basically a blocker, since it’s blocking a partner’s testing, even if there are no STR.
- Cause unknown, possibly something in shared/js/dialer/tone_player.js
- 2.1+ bug 1082139 - JavascriptException: JavascriptException: TypeError: window.getComputedStyle(...) is null at: app://callscreen.gaiamobile.org/gaia_build_defer_index.js line: 146
- Assigned to Germán.
- We are trying to reproduce the scenario mentioned by Anshul in Telefónica creating an integration test. I have not received the results from our QA team yet. Anyhow, I hope Anshul can provide us with further information about the tests he is running.
- It could be related to bug 548397 - window.getComputedStyle() returns null inside an iframe with display: none
- Germán has posted a patch for this. We don’t know if it fixes the issue or not.
- 2.1+ bug 1075699 - Calling voicemail by long-pressing the 1 button displays an error and then calls
- Assigned to Tamara.
- Ready to land a fix, but waiting for vendor to reply to a needinfo.
- Moved to RIL component, but we should still watch this.
drs
- Admin:
- Nothing new.
- Next steps:
- MVC proposal.
- This is getting a lot further. I should have it ready in a few days. It has evolved in a “design guidelines” document that includes many things, including MVC, code styling, suggested refactors, etc.
- MVC proposal.
- Patches:
- bug 1079810 - Empty sound writes into speaker, cause serious power consumption
- Looked into this a bit. I’m thinking we’re going to have to change the AudioContext initialization in the Callscreen.
- bug 1079810 - Empty sound writes into speaker, cause serious power consumption
- Reviews:
- bug 1069835 - [ partner confidential ]
- r?
- bug 834530 - Emergency dialer DTMF tones aren't regulated by the volume button (and are different volume from Dialer App's DTMF tones)
- r-, new r?
- Also investigated a couple of problems with this and posted my findings in the bug thread.
- bug 1082139 - JavascriptException: JavascriptException: TypeError: window.getComputedStyle(...) is null at: app://callscreen.gaiamobile.org/gaia_build_defer_index.js line: 146
- r?, punted to Tamara. I set myself as f?.
- bug 1068093 - Remove legacy transition code from the callscreen
- r-
- bug 1080771 - Remove phone number highlighting code
- r+
- bug 977588 - [Dialer] The Active call screen does not have the option to place calls on hold.
- r-
- bug 1069835 - [ partner confidential ]
- Other:
- In a discussion with a guy from Intel about the Telephony API.
- bug 977056 - [Dialer] Visual discrepancies: Call ended view under conference call participants list
- Investigated `groupchanged` callback. We’re now discussing this with the RIL team.
thills
- bug 1075699 - T-Mobile Voicemail Bug. Still no reply from partner. Francisco is going to help with this.
- bug 1079143 - BlueTooth Bug - Posted my findings on this. Still have an NI on me for this, but prioritizing this after the blocker
- bug 1068093 - Removed legacy call screen transitions - Need to make the changes based on latest review from drs.
- bug 1081854 - I “integrated” the patch that was put up for review on this on Friday. I tested out the API and this seems to work. I need to do a bit of work/investigation/refreshing on the promise part of this, but I believe I should be able to post a feedback today and maybe a review tomorrow.
- bug 1083402 - “X has left the call does not show up”. Etienne and Carrie confirm this is a regression. Do we need to prioritize this?
jlorenzo
- The manual test run is over. No changes in the number since Friday.
- I cleaned up the test to catch bug 1074379 (see bug 1083731). I asked QA in the US to run the test with AT&T and T-Mobile.
- I've set up a flashing station for Tako. I can put the base image but I still need to figure out how to properly flash gecko and gaia.
Manual test run status for Dialer: Total: 348 => http://mzl.la/fxos-dialer-2-1-moztrap-active-test-cases Passed: 336 Failed: 8 => http://mzl.la/fxos-dialer-2-1-moztrap-test-run-3-non-passed Invalidated: 1 => http://mzl.la/fxos-dialer-2-1-moztrap-test-run-3-non-passed Not done: 1 => https://moztrap.mozilla.org/manage/case/13733/
gtorodelvalle
- Absent/no report