Closed
Bug 310273
Opened 20 years ago
Closed 20 years ago
No collision warning when adding to CC list on a bug whose blockers have changed (as a result of a new bug filing) since the bug was loaded
Categories
(Bugzilla :: Creating/Changing Bugs, defect)
Bugzilla
Creating/Changing Bugs
Tracking
()
People
(Reporter: Waldo, Unassigned)
References
()
Details
Specifically, I reproduced this in the following manner:
1. Open bug 287571 in a browser.
2. Open a new browser window and file bug 310271, adding bug 287571 to the list
of bugs upon which it depends. This changes "OtherBugsDependingOnThis" in bug
287571 to "310271"; it previously was empty.
3. Wait for followup page to load completely, signalling that all emailing of
interested parties has happened.
4. Switch back to the browser containing bug 287571, whose displayed "blocks:"
list is now out-of-date.
5. Add an email address to the CC list for the bug and submit the changes.
What happens next is that the change to the "blocks" list in bug 287571 is
overwritten with the value on the out-of-date version of the page: "". The bug
CC list is updated and the blocking list is reset. What *should* happen is that
I'm warned about a mid-air collision with myself so that I don't accidentally
set the bug 310271 dependency list to nil.
The recorded tracks from this are available at the URL specified in the bug report.
Comment 1•20 years ago
|
||
I'm fairly sure we have a bug for this somewhere... yes, I do believe that the
dependson/blocks fields are not correctly covered by the mid-air collision code.
![]() |
||
Comment 2•20 years ago
|
||
I cannot reproduce the problem. A mid-air collision is reported, as expected.
Looking at the code, this has been fixed by bug 73502.
*** This bug has been marked as a duplicate of 73502 ***
Status: NEW → RESOLVED
Closed: 20 years ago
Keywords: qawanted
Resolution: --- → DUPLICATE
Target Milestone: Bugzilla 2.22 → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•