Gaia/SMS/Scrum/FxOS-S8: Difference between revisions

Jump to navigation Jump to search
m
Line 159: Line 159:


=== Day 4: 25th September ===
=== Day 4: 25th September ===
====Steve====
* September 28th is national holiday in Taiwan, sorry I forgot to raise it in planning...
* {{Bug|1179628}} - [Messages][NG] Lay out Settings service structure
** Background work.
* {{Bug|1201016}} -  [Messages][NG] Migrate the current Message manager event handling to NGA.
** Migrate event handling workaround to {{Bug|1207094}}.
* {{Bug|1207094}} -  [Messages] Disable appropriate controls when in low storage condition
** Migrate event handling workaround for devicestorage service(shim).
* {{Bug|1206678}} - Outgoing MMS contains subject that was typed by user, but then hidden
** Still waiting for UX replies.
* {{Bug|1203886}} - The back button in sms conversation view does not always work
** Create a patch for review. I tried to implement integration test but the second tap event is slower than panel switch timing. The transition logic runs in server side is much faster and tap event from client could not insert the topanel action in time.
**: (Oleg) Yeah, I've left a proposition with several taps on notification that calls toPanel several times under the hood, you can try this if you have time or just left it to a separate bug :)
**: (Steve) So you already implement the specific several taps action in notification integration test?
**: (Oleg) We have tests and helper methods to create notifications, and have System libs to tap on them I think and we have activities as well - maybe we can wrap up something out of it :) We just need to open activity in test app while in Conversation view, create notification for the right thread, and tap several times on it, then close activity and try to go back to Inbox.
**: (Steve) I wrote the navigation integration test for it already, but the problem is tap action is not fast enough to trigger the problem, even I call conversation.tap();conversation.tap(); continuously without timeout waiting.
**: (Oleg) Right, that is why I thought the trick (and actually the bug QA noticed) with opened activity (while document is hidden we don't change panel, so that we can call toPanel several times) can do the job, but maybe I'm missing something.
**: (Julien) otherwise maybe we can use scriptWith and call "click" twice on the link ?
**: (Oleg) Hmm, maybe it will work as well, I'd try :)
Today:
* Low storage work.
* Working on some blockers if they have any progress.
====Julien====
* continued work on {{Bug|1207093}}: popup for low storage condition, now it works on firefox, but {{Bug|1208113}} is occurring. I tried to convert it to new-style components but I don't think we should do that here. Will continue work on this today.
* gave feedback on blocker {{Bug|1203886}} about the back button that doesn't work
* gave feedback on rishav's patch for {{Bug|1180470}}
Today:
I want to:
* continue handling review/feedback/NI queue
* continue work on the low storage condition
====Oleg====
* {{Bug|1176976}} - [Messages][Drafts] Remove the draft saving/replacing action menu
** No progress (in review).
* {{Bug|1198266}} -  [Messages] Use ConversationService in the application
** Replied to Steve's question (awaiting feedback).
* {{Bug|1179586}} - Intermittent  apps/sms/test/marionette/conversation_test.js | Conversation Panel Tests  General use cases Long SMS thread User can see all messages when  scrolls up
** Investigated and prepared PR that should fix intermittent failures (awaiting feedback).
* {{Bug|1205874}} - [Messages] After starting a  new conversation from previously saved draft, that conversation will be  counted twice when using Select All in Inbox.
** Investigated, figured out the root cause, want to work on fix today (in progress).
Other:
* {{Bug|1206093}} - [Messages][Tests] Leverage "client.switchToShadowRoot" to tap on gaia-header action button
** Still the same, guiding contributor on this issue (in progress).
* {{Bug|1206844}} - Adding Firefox Emoji font support
** Reviewing, have to figure out why it partially works for me even without patch (all emojis are recognized except for the fancy numbers, they're recognized as ordinary numbers without patch), the first guess is that if some symbol can't be found in the default font it falls back to another one and eventually finds the right glyph in Emoji font, but numbers are found in the default font. Will ask Pavel (in progress).
**: (Julien) emojis are complicated stuff: some symbols are in the normal unicode and part of some fonts, some other symbols are part of unicode's astral plane and part of other fonts
**: (Oleg) Ugh, I thought that all emoji's symbols are not normal :) Got it, thanks for the explanation!
**: (Julien) I read a very useful article some days ago about it, I'll try to find it back for you.
**: (Oleg) Thanks!
**: (Julien) http://eev.ee/blog/2015/09/12/dark-corners-of-unicode/
Today:
* Will handle review/feedback/need-info requests;
* Will work on review comments and assigned bugs.
=== Day 5: 28th September ===
=== Day 5: 28th September ===
=== Day 6: 29th September ===
=== Day 6: 29th September ===
Confirmed users
383

edits

Navigation menu