821609 - [Clock] Clicking position shifts when deleting the alarm.

Status: RESOLVED WORKSFORME

(Firefox OS Graveyard :: General, defect, P2)

Description

[Gene Lian (I already quit Mozilla)]

STR:
====================
  0. 2012/12/14 mozilla-central build.
  1. Add a new alarm and save it.
  2. Reset that alarm and go into the time picker page.
  3. Scroll the page to show the "Delete" button below.
  4. Tap the "Delete" button.

Actual:
====================
  We cannot delete the alarm because the position you touched at step #3 will be focused instead of the position of "Delete" button.

Expected:
====================
  We should be able to delete the alarm.

Comment 1

[Gene Lian (I already quit Mozilla)]

This is also a regression due to the recent scroll event change.

Also, nominate for bb+ since we cannot correctly delete the added alarm.

Comment 2

[Andrew Overholt [:overholt]]

Is this a dupe of bug 821600?

Comment 3

[Gene Lian (I already quit Mozilla)]

(In reply to Andrew Overholt [:overholt] from comment #2)
> Is this a dupe of bug 821600?

No. This issue is even worse. The "delete" button has no reaction when tapping it, because the touching position is located at other positions that you touched before for scrolling. This doesn't only occur in the timepicker for alarm setting, but also in other pages that needs to be scrolled, which is a general issue.

Comment 4

[[e-mail], [e-mail]]

We can reproduce it in UI Tests APP.
STR:
====================
1. Launch UT Tests APP.
2. Scroll the menus of list.
3. Click any option.

Actual:
====================
  We cannot go into the option which is clicked by user.

Expected:
====================
  We should be able to go into the option.

Should the general issue be fixed by platform?

Hi schien,
Could you provide the referenced patch for the regression?

Comment 5

[Shih-Chiang Chien [:schien] (UTC+8) (use ni? plz)]

This is a regression caused by bug 814252. Preventing default action on touch move event will make gecko unable to update active element correctly.
I'll take this bug and fix it in gecko.

Comment 6

[Gene Lian (I already quit Mozilla)]

Another regression due to bug 814252.

Comment 7

[Shih-Chiang Chien [:schien] (UTC+8) (use ni? plz)]

I cannot reproduce this issue after bug 814252 been backout.