2763: Review description lost in version 1.6.11

Chris******@actia***** (Google Code) (Is this you? Claim this profile.)
Dec. 24, 2012
2442
What version are you running?

1.6.11

What's the URL of the page containing the problem?

servername/r/number

What steps will reproduce the problem?

1. bring up a review to edit, e.g. a new one (without a diff)
2. Add some text to the clipboard.
3. Left click in the Description entry field to activate it and then right click and choose paste.
4. Use the mouse to click OK

The text will be lost. This used to work in 1.5.x. It looks like the field is considered unchanged.

Using CTRL-S appears to work around this problem.

The other way to see this problem is to:

1. bring up a review to edit, e.g. a new one (without a diff)
2. Add some Description entry field that contains a simple spelling mistake, click OK (or ctrl-S to save)
3. In a browser that supports spell check (Firefox/Chrome) Left click in the Description entry field to activate it and again then find the misspelled word right click and choose correct spelling.
4. Use the mouse to click OK

Old misspelled word remains.

What is the expected output? Expect the new/updated text to be saved. What do you see instead? Old text (which may be empty).


What operating system are you using? What browser?

Wind32/64 browser with IE and Firefox
chipx86
#1 chipx86
I've done this so many times and still can't reproduce it.

I'd really need to see the JavaScript console logs.
  • +NeedInfo
#2 Chris******@actia***** (Google Code) (Is this you? Claim this profile.)
I can definitely reproduce this 100% of the time. I'm not seeing anything in the javascript console in Firefox's Web Developer, I suspect you want a debug step though session? I'm not sure how to create one of those. If you can run me through the steps I can try and get any logs you need. I could even share my desktop over webex if the logs don't work out.
#3 Chris******@actia***** (Google Code) (Is this you? Claim this profile.)
Emailed privately and nothing shows up in debug log.

I've also reproduced this using the 1.7 beta 3 release at http://reviews.reviewboard.org/r/3447/ (I've not published this review).