99786 - Report all validation errors to user (not just one)

Status: RESOLVED DUPLICATE of bug 95923

(Bugzilla :: Creating/Changing Bugs, defect, P3)

Description

[Alex Vincent [:WeirdAl]]

On unrelated bug 64765, I attempted to change three pieces of information I did
not have had access to.  I attempted changing the Summary, the OS, and the
Severity.  Bugzilla rejected me, naturally, but its dialog to me only explained
one of the three reasons my changes to the bug could not be valid.  So I dropped
the Severity change, only for it to tell me again I could not submit because of
the OS change I was not authorized to make.  So I dropped that change as well,
and I still could not submit; Bugzilla told me I wasn't allowed to change the
Summary.

Three out of five times I tried to submit essentially the same information;
three times it was invalid.  But only once did Bugzilla tell me all the reasons
it was invalid.  Also, each time I used the Back button from the error page, I
found everything I had changed (including the Additional Comments section) reset
to normal.  (My "additional comments" were gone.  That is a data loss, which for
this bug is irrelevant.)

Steps to reproduce:
(1) Attempt to change the OS, Severity, and Summary of this bug, using an
"unprivileged" Bugzilla account.  (That is, Bugzilla must not allow you to
change these values.)

(2) Click the "Submit" button.

Expected Results:  Bugzilla will list three reasons your changes could not be
processed.

Actual Results:  Bugzilla will list only one reason your changes could not be
processed.

I would suggest Bugzilla not end its validation attempts until all the fields
have been checked, and then report everything which would block submission.

Comment 1

[Dave Miller [:justdave]]

Losing the data when you click back is a bug in your browser.  Report it to the
vendor of the web browser you're using (or in the Browser product here if you're
using Mozilla)

The rest of this here is valid though.  I'm pretty sure there's already a bug on
it, but it's not coming to mind right away.  I'll post the number here when I
find it.

Comment 2

[Alex Vincent [:WeirdAl]]

Heaven protect me from duplicates!  :)  There weren't any in this component 
(which I thought to look in), but glancing at a larger list, maybe we have a 
couple.

bug 95923 is similar, but probably not a duplicate.  
bug 40896 would be very valuable.

This isn't an exhaustive search, by the way.  I looked over the summaries of 
all open bugs against Bugzilla.  Only about five caught my eye as possibles, 
and of those five, the two above came closest.

As far as the data loss, that was Moz0.9.4, but I think that one's been filed 
before.

Comment 3

[Myk Melez [:myk] [@mykmelez]]

Bug 76714 is a Bugzilla bug that was causing form data to disappear when
clicking back.  Mozilla bug 74639 exacerbated the problem, but that bug has
apparently been fixed.

Comment 4

[Alex Vincent [:WeirdAl]]

Based on your comments, I think this bug and bug #65164 block bug #47251.

Comment 5

[Alex Vincent [:WeirdAl]]

I'm sorry, I mean bug #76714 and bug #65164.

Comment 6

[Alex Vincent [:WeirdAl]]

Ironically, now that I'm "privileged", I find it difficult to test this bug.

Comment 7

[Joel Peshkin]

Unloved bugs targetted for 2.18 but untouched since 9-15-2003 are being
retargeted to 2.20
If you plan to act on one immediately, go ahead and pull it back to 2.18.

Comment 8

[Max Kanat-Alexander]

This bug has not been touched by its owner in over six months, even though it is
targeted to 2.20, for which the freeze is 10 days away. Unsetting the target
milestone, on the assumption that nobody is actually working on it or has any
plans to soon.

If you are the owner, and you plan to work on the bug, please give it a real
target milestone. If you are the owner, and you do *not* plan to work on it,
please reassign it to [e-mail] or a .bugs component owner. If you are
*anybody*, and you get this comment, and *you* plan to work on the bug, please
reassign it to yourself if you have the ability.

Comment 9

[Frédéric Buclin]

This is actually a dupe of bug 95923, and this problem has been fixed for 3 years now.