Closed Bug 796491 Opened 12 years ago Closed 12 years ago

Hard to activate "show password" checkbox

Categories

(Firefox OS Graveyard :: Gaia, defect)

defect
Not set
normal

Tracking

(blocking-basecamp:-)

VERIFIED FIXED
blocking-basecamp -

People

(Reporter: ghtobz, Assigned: kaze)

Details

(Whiteboard: [label:settings][label:needsGeckoSupport][label:polish][label:softBlocker])

[GitHub issue by dhylands on 2012-08-17T18:11:14Z, https://github.com/mozilla-b2g/gaia/issues/3550]
Once you've selected an AP in the Wifi settings, you get presented a dialog to enter the password. On my otoro, I have to touch the "show password"  many times before I can get it to check or uncheck.

It's easy to press and get the "show password" line to highlight in blue, but that doesn't change the checkbox (I think it should).

It seems that I have to actually touch within the small little box itself (because the box shows a blue border whenever it does change.
[GitHub comment by nhirata on 2012-08-21T21:06:42Z]
ya.  I agree with @dhylands ... that checkbox is hard to mark.
[GitHub comment by vingtetun on 2012-09-05T15:47:00Z]
Assigning @fabi1cazenave !
[GitHub comment by autonome on 2012-09-05T15:51:42Z]
Would take a fix, but not holding the release on this.
[GitHub comment by cleemoz on 2012-09-05T15:52:10Z]
Valid bug!  But agree not a blocker, but annoying for users.
[GitHub comment by nhirata on 2012-09-05T17:37:57Z]
Marking as a softblocker.
[GitHub comment by fabi1cazenave on 2012-09-10T13:44:23Z]
Platform issue: https://bugzilla.mozilla.org/show_bug.cgi?id=789918
[GitHub comment by fabi1cazenave on 2012-09-14T21:25:57Z]
My bad, it wasn’t a platform issue. That’s the most shameful fix I ever did. :-s
fixed: https://github.com/mozilla-b2g/gaia/issues/4750
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Verified as resolved on Unagi Build ID:20121231070201
Unable to verify on Otoro, only have Unagi
I verified that it works properly on my otoro (using gaia hash 05b802ed09f3459899fd2210e3472c9afbd1a07b - from around Dec 27)
This issue is fixed for  device Unagi; build #20130112070202v.1 verifying bug shows verified on both otoro and unagi
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.