820982 - notification bar very difficult to pull down (and push back up)

Status: RESOLVED DUPLICATE of bug 937101

(Firefox OS Graveyard :: Gaia::System, defect, P3)

Description

[Dietrich Ayala (:dietrich)]

Most times that I try to pull down the notification bar, it either:

1) doesn't respond at all
2) opens an app just below it
3) takes me to the homescreen to the right
4) slides down a tiny bit and pops back up

Comment 1

[Dietrich Ayala (:dietrich)]

Unagi 12/12 build

Asking blocking because I hit this *so* often, and it so rarely works as expected.

Comment 2

[Joe Cheng [:jcheng] (please needinfo)]

Triage: BB+, P3 - usability issue worth improving

Comment 3

[Vivien Nicolas (:vingtetun) (:21) - (NOT reading bugmails, needinfo? please)]

I have heard the extract contrary of this bug from a contributor last friday. blocking-basecamp?

Comment 4

[Dylan Oliver [:doliver]]

blocking- for now, tagging for the UX team to weigh in on current usability.

Comment 5

[Chris Jones [:cjones] inactive; ni?/f?/r? if you need me]

(In reply to Vivien Nicolas (:vingtetun) from comment #3)
> I have heard the extract contrary of this bug from a contributor last
> friday. blocking-basecamp?

ORLY?  The usability is extremely bad on my otoro ...

Any more information you can supply?

Comment 6

[Josh Carpenter [:jcarpenter]]

Hmm... also on the Unagi 12/12 build and this seems to be working okay. The animation is choppy, but it consistently responds to my swipes. I'm not seeing any of the four behaviors you've described, Dietrich.

I _would_ like to improve the choppyness. I pull down, there's a tiny delay, and then the tray pops into existence about 1/3 down the page before it animates the rest of the way. Feels a bit cheap and unpleasant as a result.

Comment 7

[Josh Carpenter [:jcarpenter]]

Marking this UX-P3 for the notification pull down perf issue.

Comment 8

[abhinav.srivstva]

The pull down is still responsive for me in v1.2.0.0 prerelease but the push back is impossible. I have to use home buttom to exit notification drawer.

So push back in unresponsive in v1.2.0.0 prerelease

Comment 9

[edujoseg]

I'm experimenting similar issue with b2g 1.2  and 1.3 latest nightly builds on zte open.

Comment 10

[znmeb]

I'll join the chorus here. I have a ZTE Open (eBay US model). It shipped with 1.0.1 of B2G and the pull-down worked flawlessly. After I flashed it with B2G 1.2 built from source, it shows the same symptoms as the original poster describes. The only way I can get it to pull down at all is:

1. Start the Wikipedia app
2. Rotate the device to landscape
3. Repeatedly press the pull down area until it triggers. Sometimes a rapid tap will do it, sometimes rubbing cross-wise.

The key is that it worked with the 1.0.1 build the device shipped with, but doesn't work with 1.2. Overall 1.2 responds to tapping *faster* that 1.0.1 did, so I'm guessing there's some kind of timing tweak that is in play here.

Comment 11

[znmeb]

After playing with it a bit further I'm thinking the user interface needs to change. The area devoted to the pull-down at the top of the screen is too narrow, and the areas below it are live right to the edge. Even with a pinky it's hard to hit the active zone, and I also think it's less sensitive with 1.2 than it was with 1.0.1

So I'd make the pull-down strip wider and the area beneath it shorter, or even replace the pull-down "strip" with an "industry standard size" button as documented in the numerous mobile human interface guides floating around. Make it big enough to hit with a thumb one-handed!

Comment 12

[znmeb]

I rebuilt B2G last night and reflashed the ZTE and the response seems to have improved remarkably. Now a sharp tap in the top strip brings up the pull-down and if you tap and hold you can pull it down. There have been some visible changes on the home screen as well; the "I'm thinking of" bar is lower, and the default home screen now has some buttons for games, etc. by default.

This may be 1.3 - even though I specified the 1.2 branch when I did the configure / build, the build on the device claims to be Boot2Gecko-1.3.0.0-prerelease. In any event some code's been pushed to the source in the last week or so that appears to have fixed this.

Comment 13

[Jason Smith [:jsmith]]

I think you are talking about the changes that happened in bug 937101.

Comment 14

[znmeb]

(In reply to Jason Smith [:jsmith] from comment #13)
> I think you are talking about the changes that happened in bug 937101.

Yep ... should we close this as a duplicate?

Meanwhile, I rebuilt and reflashed just today ... device is back to 1.2 and the problem is back. So I'll go track that commit from bug 937101 and rebuild-reflash again. Love git ;-)