From owner-freebsd-bugs@FreeBSD.ORG Thu Jun 22 16:00:35 2006 Return-Path: X-Original-To: freebsd-bugs@hub.freebsd.org Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 68DA716A47E for ; Thu, 22 Jun 2006 16:00:35 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 90F3D43D5A for ; Thu, 22 Jun 2006 16:00:34 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k5MG0Ye8076779 for ; Thu, 22 Jun 2006 16:00:34 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k5MG0Yre076777; Thu, 22 Jun 2006 16:00:34 GMT (envelope-from gnats) Resent-Date: Thu, 22 Jun 2006 16:00:34 GMT Resent-Message-Id: <200606221600.k5MG0Yre076777@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Jo Rhett Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 00EA516A47E for ; Thu, 22 Jun 2006 15:54:35 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id CDF8343D64 for ; Thu, 22 Jun 2006 15:54:33 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.13.1/8.13.1) with ESMTP id k5MFsXxv026449 for ; Thu, 22 Jun 2006 15:54:33 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id k5MFsXOi026448; Thu, 22 Jun 2006 15:54:33 GMT (envelope-from nobody) Message-Id: <200606221554.k5MFsXOi026448@www.freebsd.org> Date: Thu, 22 Jun 2006 15:54:33 GMT From: Jo Rhett To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Cc: Subject: misc/99305: send-pr.html is frustrating/broken X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jun 2006 16:00:35 -0000 >Number: 99305 >Category: misc >Synopsis: send-pr.html is frustrating/broken >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jun 22 16:00:34 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Jo Rhett >Release: 6.0 >Organization: svcolo >Environment: doesn't matter >Description: Submitting a PR is an extremely frustrating process, mostly due to the fact that I have to open the form, then cut&paste everything into a second form later. It's pretty clear that the confirmation codes time out in just a few minutes. Which means that entering a detailed problem report is impossible in that timeframe. It's also a killer if you get interrupted by a co-worker and have to come back to it. >How-To-Repeat: 1. Open the send-pr.html form. 2. Fill out the header fields. 3. Fill in the full description and process text fields with patches and examples. *try to do this REALLY FAST to avoid the next ...* 4. Hit submit 5. Read complaint about improperly entering the confirmation code -then- 6. Open a second window to the same form 7. Cut and paste everything from window 1 to window 2 8. Enter the new code and hit submit >Fix: 1. Don't report to the user that they entered the code incorrectly when it's actually a time out. Tell them it's a time out. 2. Don't time out so darn fast! I'm a freakin speed typist, and there have been times that I missed the timeout interval without being interrupted even once! Do you want detailed reports or not? 3. AND/OR make it possible to get a new confirmation code without re-entering all of the information. How about putting the form-supplied data into a new page with a new confirmation code at the bottom? >Release-Note: >Audit-Trail: >Unformatted: