...

...

...

...

"TP" == Tim Peters writes:

TP> The first time I submitted a bug, I backed up to the entry TP> page and hit Refresh to get the category counts updated (never TP> saw Jitterbug before, so must play!). IE5 whined about TP> something-or-other being out of date, and would I like to TP> "repost the data"? I said sure. This makes perfect sense, and explains exactly what's going on. Let's call it "poor design"[1] instead of "user error". A quick scan last night of the Jitterbug site shows no signs of fixes or workarounds. What would Jitterbug have to do to avoid these kinds of problems? Maybe keep a checksum of the current submission and check it against the next one to make sure it's not a re-submit. Maybe a big warning sign reading "Do not repost this form!" Hmm. I think I'll complain on the Jitterbug mailing list. -Barry [1] In the midst of re-reading D. Norman's "The Design of Everyday Things", otherwise I would have said you guys were just incompetent Webweenies :)

That's be good -- alternatively, insert a 'safe' CGI script after the validation -- "Thanks for submitting the bug. Click here to go back to the home page".

That makes a lot of sense! I'm now quite sure that I had the same "Repost form data?" experience, and just didn't realized that mattered, because I was staring at the part of the form that was showing the various folders. The Jitterbug software is nice for tracking bugs, but its user interface *SUCKS*. I wish I had the time to redseign that part -- unfortunately it's probably totally integrated with the rest of the code... --Guido van Rossum (home page: http://www.python.org/~guido/)

TP> The first time I submitted a bug, I backed up to the entry page and TP> hit Refresh to get the category counts updated (never saw Jitterbug TP> before, so must play!). IE5 whined about something-or-other being TP> out of date, and would I like to "repost the data"? I said sure. Barry> This makes perfect sense, and explains exactly what's going on. Barry> Let's call it "poor design"[1] instead of "user error". A quick Barry> scan last night of the Jitterbug site shows no signs of fixes or Barry> workarounds. What would Jitterbug have to do to avoid these Barry> kinds of problems? If the submission form uses METHOD=GET instead of METHOD=POST, the backup problem should go away. Skip (finally hobbling through my email after the move to Illinois...)