Bug 7498 – Tapping a half selected bookmark causes that item to jump to the top

Bug 7498 - (int-152939) Tapping a half selected bookmark causes that item to jump to the top

(int-152939)
Summary:	Tapping a half selected bookmark causes that item to jump to the top

Status:	NEW

Product:	Browser
Component:	User interface
Version:	5.0:(10.2010.19-1)
Platform:	All Maemo

Importance:	Low minor with 3 votes (vote)
Target Milestone:	5.0+
Assigned To:	Nagineni Sudarsana Babu
QA Contact:	browser-bugs

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree

Reported:	2009-12-30 18:47 UTC by Johannes Siipola
Modified:	2010-06-15 13:18 UTC (History)
CC List:	2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note

You need to log in before you can comment on or make changes to this bug.

Description Johannes Siipola (reporter) 2009-12-30 18:47:15 UTC

SOFTWARE VERSION:
1.2009.42-11

EXACT STEPS LEADING TO PROBLEM: 
1. Scroll the bookmark view so only a half of the lowest bookmark is selected
it
2. Press or try to scroll from the visible part of the lowest bookmark in the
list

EXPECTED OUTCOME:

The list scrolls a little so the bottom bookmark becomes completely visible,
just like in any other application (for example, Contacts)

ACTUAL OUTCOME:

The list makes a huge jump and so the former bottom bookmark is placed at the
top of the list

REPRODUCIBILITY:
always

EXTRA SOFTWARE INSTALLED:

lots

OTHER COMMENTS:

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2b5)
Gecko/20091204 Firefox/3.6b5

Comment 1 Andre Klapper maemo.org

2010-01-11 18:22:03 UTC

------- Comment #4 from timeless  2010-01-10 02:33 GMT+3 -------
this is inconsistent with file manager. -- which is unfortunate, because if it
were consistent, i could just blame it :(.

Comment 2 maemo 2010-06-12 10:54:19 UTC

This sounds like an easy fix, but the bug is still present in PR1.2.

Comment 3 timeless 2010-06-13 04:17:18 UTC

in fact it was fixed in January but missed the last n boats because no one from
management approved it. But in general, please don't comment about the
difficulty of fixing code. The difficulty of fixing something can be entirely
unrelated to the obvious portion. In this case, it's apparently incredibly
difficult to fix, because even though the engineer has *fixed* it, the
engineering team has been unable to convince management to approve delivery of
the fix.