| Summary | Changes link sometime shows diff to self |
| Queue | Chora |
| Queue Version | HEAD |
| Type | Bug |
| State | Resolved |
| Priority | 2. Medium |
| Owners | |
| Requester | slusarz (at) horde (dot) org |
| Created | 05/24/2006 (7004 days ago) |
| Due | |
| Updated | 05/24/2006 (7004 days ago) |
| Assigned | 05/24/2006 (7004 days ago) |
| Resolved | 05/24/2006 (7004 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Resolved
... and back to real work now.
it should _always_ show diffs to the previous revision anyway? Or
State ⇒ Feedback
So not a bug, but perhaps a UI issue.
Do folks think that if you click the diff icon on the selected row, it
should _always_ show diffs to the previous revision anyway? Or perhaps
just not do anything?
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ Change link sometime shows diff to self
Queue ⇒ Chora
State ⇒ Unconfirmed
Steps to reproduce last time:
1. Browser has not visited chora yet since being opened, and hasn't
visited today (just in case this is a cookie problem)
2. Directly access a file entry. i.e.
http://cvs.horde.org/framework/IMAP/IMAP/Search.php
3. Click on the changes icon for any entry.
4. The diff page tries to diff that version to itself - so obviously,
there are no changes.
I noticed in step 3 that the r1 parameter of the URL was "0". When I
went back to that page the r1 parameter was correctly set to the
previous revision of that branch.