Closed Bug 1068093 Opened 10 years ago Closed 10 years ago

Remove legacy transition code from the callscreen


(Firefox OS Graveyard :: Gaia::Dialer, defect)

Not set


(b2g-v2.2 fixed)

2.1 S9 (21Nov)
Tracking Status
b2g-v2.2 --- fixed


(Reporter: drs, Assigned: thills)



(Whiteboard: [planned-sprint c=1])


(1 file, 5 obsolete files)

We have some legacy transition code in the callscreen from after bug 927862 landed, such as this:

We should remove all references to this as the transitions are now handled in the AttentionWindow code in the System app.
Assignee: nobody → thills
Whiteboard: [planned-sprint] → [planned-sprint][in-sprint=v2.1-S5]
Target Milestone: 2.1 S5 (26sep) → 2.1 S6 (10oct)
Whiteboard: [planned-sprint][in-sprint=v2.1-S5] → [planned-sprint c=3][in-sprint=v2.1-S5]
Attached patch 1068093.diff (obsolete) — Splinter Review
Hi Doug,

Looking for feedback.  I removed what Etienne suggested, plus there was some more that became useless after those.

Right now the tests are just "working", but I realize I will need to add some more to replace the ones I removed to account for this change.
Attachment #8503342 - Flags: feedback?(drs+bugzilla)
Comment on attachment 8503342 [details] [diff] [review]

Review of attachment 8503342 [details] [diff] [review]:

Looks reasonable. This can go into review whenever you're ready. I didn't check if you missed anything, but the general approach is good.
Attachment #8503342 - Flags: feedback?(drs+bugzilla) → feedback+
Let's track the in-sprint flag using the meta bug instead to avoid polluting the whiteboard of every sub-bug.
Whiteboard: [planned-sprint c=3][in-sprint=v2.1-S5] → [planned-sprint c=3]
Target Milestone: 2.1 S6 (10oct) → 2.1 S7 (Oct24)
Whiteboard: [planned-sprint c=3] → [planned-sprint c=1]
Attached patch Patch for review (obsolete) — Splinter Review
Attachment #8504938 - Flags: review?(drs.bugzilla)
Posted as a patch since I have no way to comment on this without either a PR or patch posted.
Attachment #8504938 - Attachment is obsolete: true
Attachment #8504938 - Flags: review?(drs+bugzilla)
Attachment #8505081 - Flags: review?(drs+bugzilla)
Comment on attachment 8505081 [details] [diff] [review]
Remove legacy transition code from the callscreen (author: thills)

Review of attachment 8505081 [details] [diff] [review]:

In the future, please post changes as either a PR or patch(es).

::: apps/callscreen/js/call_screen.js
@@ -68,5 @@
> -    self.statusMessage.addEventListener('transitionend', function tend(evt) {
> -      evt.stopPropagation();
> -      self.statusMessage.removeEventListener('transitionend', tend);
> -      setTimeout(function hide() {
> -        self.statusMessage.classList.remove('visible');

I don't think we can safely remove this. Otherwise, we'll be stuck with status messages constantly visible. For example, when a member of a conference call hangs up on the call, we'll see "X has left the call" until a new status message is shown.

@@ +231,4 @@
>    _wallpaperImageHandler: function cs_wallpaperImageHandler(image) {
> = 'url(' +
>        (typeof image === 'string' ? image : URL.createObjectURL(image)) + ')';
> +    setTimeout(this.setCallerContactImage.bind(this));

This is small enough that we should consider refactoring it so that it's part of `setCallerContactImage()`.

@@ +238,4 @@
>      var activeCallForContactImage = CallsHandler.activeCallForContactImage;
>      var blob = activeCallForContactImage &&;
>      this.contactBackground.classList.remove('ready');

I don't think we need this `ready` class anymore. I think the intention here was to flush the style and get the background image to fade to the new one, but this is not accomplishing that.

It's possible, though doubtful, that without this we will get a black screen or something. Please check what happens without it. This is also referred to in oncall.css:869.

::: apps/callscreen/style/oncall.css
@@ -183,5 @@
>      background: black;
>      z-index: 100;
>    }
> -  /* This transition is needed to trigger a transitionend event in */

This change should be made in 'oncall_status_bar.css' as well.

::: apps/callscreen/test/unit/call_screen_test.js
@@ +411,1 @@
>      suite('once the transition is over', function() {

We don't need this suite anymore. We should keep the underlying tests, though.

@@ -776,5 @@
> -          this.sinon.clock.tick(2000);
> -          done();
> -        });
> -        test('should hide the banner', function() {
> -          assert.isFalse(bannerClass.contains('visible'));

We should keep this test and suite. See my comment in call_screen.js about this.
Attachment #8505081 - Flags: review?(drs+bugzilla) → review-
Attached file Changes after review (obsolete) —
Hi Doug,

I put this in PR this time.  Sorry about that.  I also left the changes unsquashed for you... so there are two commits.  

Also, I tried removing the 'ready' class and the picture doesn't show up (we do get the wallpaper though).  So, I believe we need to keep that.

Attachment #8505081 - Attachment is obsolete: true
Attachment #8506142 - Flags: review?(drs.bugzilla)
Comment on attachment 8506142 [details] [review]
Changes after review

There are some issues to iron out here still. See the PR for my comments.
Attachment #8506142 - Flags: review?(drs.bugzilla) → review-
Hi Doug, I commented on your comment on the PR:

If you can have a look, that will be great as need to discuss before we move this forward.

Flags: needinfo?(drs.bugzilla)
Answered on the PR.
Flags: needinfo?(drs.bugzilla)
Attached file Updated PR after last review (obsolete) —
Changes after the last review to fix the spacing and put back the wallpaper function.
Attachment #8503342 - Attachment is obsolete: true
Attachment #8506142 - Attachment is obsolete: true
Attachment #8509771 - Flags: review?(drs.bugzilla)
Comment on attachment 8509771 [details] [review]
Updated PR after last review

I'm getting a black screen when receiving an incoming call from a contact with an image. Please investigate this. I left a couple more comments on the PR.
Attachment #8509771 - Flags: review?(drs.bugzilla) → review-
(In reply to Doug Sherk (:drs) (use needinfo?) from comment #13)
> I'm getting a black screen when receiving an incoming call from a contact
> with an image. Please investigate this.

I originally reproduced this on a Flame-JB build. I tried this again on a Flame-KK v188 build and I was no longer able to repro it. So I think it's safe to say that this isn't a problem.
Hi Doug,

I fixed the one spacing comment on the latest PR.

Regarding the one comment about _wallpaperImageHandler needing a test, I checked and we already have two in this area:

Let me know if there was something else that needed addressing.

Flags: needinfo?(drs.bugzilla)
Comment on attachment 8509771 [details] [review]
Updated PR after last review

Yep, looks good.
Flags: needinfo?(drs.bugzilla)
Attachment #8509771 - Flags: review- → review+
Target Milestone: 2.1 S7 (24Oct) → 2.1 S8 (7Nov)
Attached file Final PR after merge
New PR as I had merge conflicts.
Attachment #8509771 - Attachment is obsolete: true
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: 2.1 S8 (7Nov) → 2.1 S9 (21Nov)
You need to log in before you can comment on or make changes to this bug.