Confirmed users
820
edits
Gaia/SMS/Scrum/FxOS-S6: Difference between revisions
Jump to navigation
Jump to search
/* Day 3: 27th August
(Created page with "== List of bugs == <onlyinclude> === SMS issues handled by the SMS subteam (blocks the sprint {{bug|1198259}}) === [https://bugzilla.mozilla.org/buglist.cgi?f1=blocked&o1=subs...") |
(/* Day 3: 27th August) |
||
| Line 79: | Line 79: | ||
=== Day 2: 26th August === | === Day 2: 26th August === | ||
=== Day 3: 27th August === | === Day 3: 27th August === | ||
====Steve==== | |||
* {{Bug|1179628}} - [Messages][NG] Lay out Settings service structure | |||
** Start mozMobileConnections. | |||
* {{Bug|1180592}} - [Messages][NG] mozMobileConnections shim Implementation | |||
** WIP is ready but not fully tested yet. Will request feedback if everything works fine. | |||
* {{Bug|1198658}} - [Flame KK][Message]Press the download button, there is no message indicating that you need to switch data connection | |||
** Found a dataclone problem with DOMError instance. Patch created for review. | |||
**:(Oleg) Wilson told me some time ago, that he should deal with this errors in the bridge (like extract error message or name from Error instance), can we confirm with him why it doesn't work? Or it's not in reject callback? | |||
**:(Steve) For the normal Error instance I think he did extract the message of error instance, and in the reject we will only get message instead of error instance. But seems like DOMError is not considered. Do you think bridge should be able to dealing with the DOMError as well? | |||
**:(Julien) I think it should ! | |||
**:(Oleg) Yeah, I think we'll have ton of cases where such error can occur. | |||
**:(Steve) So, redirect the bug to Wilson, or create another issue for him? | |||
**:(Julien) I would create another issue and still fix our bug with a comment to this issue. Like "We need to clone the DOMError manually until bug XXX is resolved". Unless he can look at it soon, or you can do a PR to the threads.js lib :) | |||
**:(Steve) Got it. | |||
Today: | |||
* Create a bug to disable the message event broadcast | |||
* Layout for mozConnections shim | |||
* Confirm with Etienne about the profiling and make the list layout close to master. | |||
====Julien==== | |||
* worked more on system messages issue: I have a working solution with (I think) no bug for the current apps; I'm doing a test app with split views + event handling that could be even closer to what we'll need in SMS (esp opening a specific conversation when the user taps the notification) to see if this works with this solution. Will continue today. | |||
* spent some time on the "low storage condition" spec; I'll file some bugs later this week, there is small work for us. | |||
* some bug triaging | |||
Today: | |||
I want to: | |||
* do left-over reviews (I left them for some days ;) ) | |||
* work on the system messages issue | |||
If all this moves forward well, I could: | |||
* continue the prototype caching the thread list to a single db (including contacts/drafts/etc). | |||
====Oleg==== | |||
* {{Bug|1155534}} - [Messages][NG] Extract NewMessage view from Conversation view | |||
** No updates (in background). | |||
* {{Bug|1176976}} - [Messages][Drafts] Remove the draft saving/replacing action menu | |||
** Rebased on latest master to re-run integration tests (in review). | |||
* {{Bug|1169576}} - [Messages][NG] Implement Conversation service: method for streaming joined threads and drafts list | |||
** Finally added "checkin-needed" (checkin-needed). | |||
**: (Julien) I think you could add it earlier already :) Sheriffs don't land when the tree is closed ;) | |||
**: (Oleg) Ahhhhh, good to know :) | |||
* {{Bug|1198266}} - [Messages] Use ConversationService in the application | |||
** Analyzing data I've got with WebIDE - will dump first portion to the bug soon (in progress). | |||
**: (Julien) you can share profiles from cleopatra too. You can upload a profile to https://people.mozilla.org/~bgirard/cleopatra/ and share from here. | |||
**: (Oleg) I thought cleopatra kind of replaced with built-in profiler or not yet? I admit I don't remember what type of data cleopatra provides :) | |||
** So far l10n.js and gaia-header are the most time consuming things on the startup. | |||
**: (Julien) more than in normal master ? l10n I'm not surprised but gaia-header should not :/ | |||
**: (Oleg) I think the same as in master, just my statement of disappointment :) gaia-header doesn't look like the main thing in the app, but it consumes a lot of time :) | |||
**: (Julien) I'll look at it, maybe it regressed. Or maybe it's only JS and not Reflow/Repaint and in that case why not. | |||
**: (Oleg) Basically both, initially it spends a lot of time for createShadowRoot (~90ms) and later on it causes huge reflow (~160ms, if I understood it correctly) with sumButtonWidth - I'll comment on the bug. | |||
**: (Julien) OK, this should not happen at all :/ in Inbox, I did work (with title-start/title-end) to avoid reflows at startup, and other panels have "skip-font-fit". So I'll look and file a bug if needed. | |||
**: (Julien) also you should capture Gecko as well (there is an option, I think) | |||
Other: | |||
* Started to look at "{{Bug|1160049}} - [Messages] Attach menu should not dismiss when user cancel the replace attachment request", left on question at github; | |||
* Looked through Bevis's proposal, need some time to digest it first. | |||
Today: | |||
* Will handle review/feedback/need-info requests; | |||
* Will work on review comments and assigned bugs. | |||
=== Day 4: 28th August === | === Day 4: 28th August === | ||
=== Day 5: 31st August === | === Day 5: 31st August === | ||