Closed
Bug 482982
Opened 16 years ago
Closed 12 years ago
Finding the revision that introduced a change is well-nigh impossible
Categories
(developer.mozilla.org Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bzbarsky, Unassigned)
References
Details
STEPS TO REPRODUCE:
1) Load https://developer.mozilla.org/En/NsIAutoCompleteSearch
2) See the text that says "Can be null" in bold under previousResult.
3) Decide you want to figure out who added that text and what else they changed
in that edit.
4) Curse the lack of an annotation functionality.
5) Click history.
6) Decide to do a binary search on revisions to see when the text first
appeared.
7) Select the oldest version and the third-oldest one (the latter at 16:23 on
2008-05-12) and compare.
8) See that the text is not there.
9) Hit the browser back button.
ACTUAL RESULTS: You discover that the compare radio buttons are no longer in the state you set them to, so you lose your place in the search. Cry and give up.
EXPECTED RESULTS: Not reset your radio buttons, so that you can keep searching through the list without losing your place until you find what you want.
| Assignee | ||
Updated•13 years ago
|
Component: Deki Infrastructure → Other
Comment 1•12 years ago
|
||
Fixed in Kuma. I think your point about making it easier to find who introduced a change is a great idea. In fact, we are thinking about doing just that in bug 770706.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•5 years ago
|
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•