Closed
Bug 913357
Opened 11 years ago
Closed 11 years ago
[SMS]back button's out of range tap
Categories
(Firefox OS Graveyard :: Gaia::SMS, defect)
Firefox OS Graveyard
Gaia::SMS
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 821673
People
(Reporter: mu-ota, Unassigned)
Details
Attachments
(1 file)
10.97 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Windows NT 5.1; rv:23.0) Gecko/20100101 Firefox/23.0 (Beta/Release) Build ID: 20130814063812 Steps to reproduce: 1. Launch SMS app. 2. tap message thread. 3. tap back button out of range(right area in header plef near back button) Actual results: back action works. Expected results: back action doesn't work.
Reporter | ||
Comment 1•11 years ago
|
||
Yet user taps buck button out of range, buck action works. gaia/shared/style/headers.css ====================================== <<< attachment Blue area: >>> section[role="region"] > header:first-child > a .icon width: 2rem; <<< attachment Red area: >>> section[role="region"] > header:first-child > a width: 5rem; ====================================== So buck button out of range tap is valid for back action.
Reporter | ||
Updated•11 years ago
|
Summary: [SMS]buck button's out of range tap → [SMS]back button's out of range tap
Comment 2•11 years ago
|
||
Hi Kenzo-san, I don't exactly understand: * in comment 0, you're saying it doesn't work * in comment 1, you're saying it works Can you please explain what is the difference between your 2 actions ?
Flags: needinfo?(mu-ota)
Reporter | ||
Comment 3•11 years ago
|
||
Hi Julien-san Thank you for your reply. Sorry my report is not good. Now tap Red area(my attachment) is back action area. I think This area is wide. So Tap Red area shouldn't work.
Flags: needinfo?(mu-ota)
Comment 4•11 years ago
|
||
So, it's actually how the back button was designed, but we agreed this was not good enough and we're currently redesigning it in bug 821673. Thanks !
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•