Closed Bug 288648 Opened 20 years ago Closed 19 years ago

IE browser posts comments multiple times

Categories

(Bugzilla :: Creating/Changing Bugs, defect)

Product:
Bugzilla
Component:
Creating/Changing Bugs
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: judevries, Unassigned)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041109 Firefox/1.0
Build Identifier: 

While a customer was using IE to work in our Bugzilla system, they noticed the
following behavior:

IE does not DEBOUNCE the SUBMIT button.

Reproducible: Always

Steps to Reproduce:
1. Open a bug in Bugzilla.

2. Add some comments. (This also occurs with attachments as well.)

3. Quickly hit the SUBMIT button several times.

4. Return to the bug and look at the comments.
Actual Results:  
When you return to the bug you will notice that the comment that you made was
posted multiple times. (Or the attachment if you were adding an attachment.)

Expected Results:  
The comment or attachement should only be posted once if the SUBMIT buttion is
press muptiple times.

This problem only appears in IE. I have tested it in other browsers.
This comment was posted using IE and then click the Commit button several 
times. Example of what occurs.
I got a MID-AIR collision when trying to duplicate this issue. We do not get 
that error on our system. I wonder if that is something in 2.19.1 that is 
different than in 2.18? Any ideas?
I got a MID-AIR collision when trying to duplicate this issue. We do not get 
that error on our system. I wonder if that is something in 2.19.1 that is 
different than in 2.18? Any ideas?
One more time to make verify that behaior.
One more time to make verify that behaior.
Sounds like (at least for you), bugzilla is somehow getting out of sync with 
the database...

The comment should only be posted (rather than going to the midair page) if the 
last changed date is still the same as you observed it when loading the bug 
page, and by the time it checks this, surely the tables should already be 
locked and lastchanged will have been updated by the time they're unlocked? 
Your observed behaviour suggests that the midair checking is not quite right.

Let's try and do the same thing here while I'm at it...
I just got the midair page.
I have tested this bug again and received the MID-AIR collision, which is the behavior that I would expect. Closing.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.