Bug 312846

Summary:	Clicking the "[reply]" link beside the original description will insert text "(in reply to comment #N+1)" where N is the latest comment.
Product:	[Websites] bugs.kde.org	Reporter:	Jekyll Wu <adaptee>
Component:	general	Assignee:	KDE sysadmins <sysadmin>
Status:	RESOLVED UPSTREAM
Severity:	normal	CC:	imalchow
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Linux
URL:	https://bugs.kde.org/show_bug.cgi?id=198199
See Also:	https://bugzilla.mozilla.org/show_bug.cgi?id=827983
Latest Commit:		Version Fixed In:

Description Jekyll Wu 2013-01-07 21:38:17 UTC

Normally, clicking the "[reply]" link beside comment N will insert "(in reply to #N)", and that is exactly the expected behavior. But clicking the "[reply]" link beside the original description (call it comment #0) will insert "(in reply to comment #7)" when the comment #6 is the latest, and so on.

That is confusing, because once that new comment is added, it looks like I am replying to myself while the following quoted text simply does not match .

I think it should insert "(in reply to comment #0)" 



Reproducible: Always

Comment 1 Ingo Malchow 2013-01-07 21:58:10 UTC

(In reply to comment #0)
> Normally, clicking the "[reply]" link beside comment N will insert "(in
> reply to #N)", and that is exactly the expected behavior. But clicking the
> "[reply]" link beside the original description (call it comment #0) will
> insert "(in reply to comment #7)" when the comment #6 is the latest, and so
> on.
> 
> That is confusing, because once that new comment is added, it looks like I
> am replying to myself while the following quoted text simply does not match .
> 
> I think it should insert "(in reply to comment #0)" 
> 
> 
> 
> Reproducible: Always

Can't confirm here (as you can see). Tested on several bugs. Please make sure you have a fresh copy of bugzilla, no cached content, might be some stuck javascript from some cache.
Else, what browser are you using?

Comment 2 Jekyll Wu 2013-01-07 22:19:02 UTC

I use google-chrome when reporting it . Also happens in rekonq .

But I think I have found the key condition now. I'm using "Newest to oldest, but keep original description at the top" as the comment order in preference. If I change to the site default  "oldest to newest", then the reported problem doesn't exist. 

Maybe a upstream problem ?

Comment 3 Ingo Malchow 2013-01-07 23:08:51 UTC

Then it is indeed an upstream problem, yeah. The only things that are touched by our js are theme related, and not function related. Marking as upstream problem then.

Comment 4 Jekyll Wu 2013-01-08 21:11:10 UTC

reported  to upstream at https://bugzilla.mozilla.org/show_bug.cgi?id=827983