Closed
Bug 523989
Opened 16 years ago
Closed 16 years ago
Chrome buttons are not sensitive enough
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(fennec1.0-)
VERIFIED
WORKSFORME
| Tracking | Status | |
|---|---|---|
| fennec | 1.0- | --- |
People
(Reporter: aakashd, Unassigned)
Details
Build Id:
Mozilla/5.0 (X11; U; Linux armv7l; en-US; rv:1.9.2b1pre) Gecko/20091022
Fennec/1.0b5pre
and
Mozilla/5.0 (X11; U; Linux armv6l; en-US; rv:1.9.3a1pre) Gecko/20091022
Fennec/1.0b5pre
Steps to Reproduce:
1. Go to a page that take awhile to load like litmus.mozilla.org
2. Try multiple degrees of pressing down to click on the stop button until it does stop.
3. Try to do the same with the reload button
Actual Results:
The chrome buttons need to be a little more sensitive as they're going to a pressed down state, but are not performing the desired action.
Expected Results: Any time the button is in a pressed state should mean the desired action should be performed
| Reporter | ||
Updated•16 years ago
|
tracking-fennec: --- → ?
Comment 1•16 years ago
|
||
This is highly dependent on the task being performed and the systems ability to interrupt that task. Many task must yield and see if they are being stopped.
For example, I can start loading planet.mozilla.org on my Mac. Pressing "stop" 3 times has no visible affect. the page does stop when the system takes the time to see if something is trying to interrupt the operation.
Electrolysis will hopefully help this situation.
Updated•16 years ago
|
tracking-fennec: ? → 1.0-
| Reporter | ||
Comment 2•16 years ago
|
||
Fennec buttons are really responsive now, this WFM on builds:
Mozilla/5.0 (X11; U; Linux armv7l; Nokia N900; en-US; rv:1.9.2.5pre) Gecko/20100503 Namoroka/3.6.5pre Fennec/1.1b2pre
and
Mozilla/5.0 (X11; U; Linux armv71; Nokia N900; en-US; rv:1.9.3a5pre) Gecko/20100503 Namoroka/3.7a5pre Fennec/1.1b2pre
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
| Reporter | ||
Updated•16 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•