Created attachment 53894 [details] screenshot - upper half of window Tried using the Bug Submission Assistant, using Debian Iceweasel version 3.5.16 (a rebranded version of Mozilla Firefox 3.5.16). After answering all questions, I'm stuck on step 5. I've chosen component, subcomponent, and version. I've entered a subject and a long description. I've opened (in new tab or window) a few "Related bug reports" to check for duplicates. But I see no "submit" button or similar.
Created attachment 53895 [details] screenshot - lower half of window
Not a bug, it's a feature, but really worrying. The Submit button appears after you have typed at least 10 (?) characters into the Summary pane and THEN click something into the "Long description" (and have at least done a 1 character edit in "Long description". I believe the idea was to prevent the reporter from accidently submitting before having finished. Indeed that might be annoying because reporter wastes time searching for the 'Submit' button instead of simply completing the report. Suggestion for a solution: 1. Fields with missing contents should be marked light red background, red border or similar (samd for 'Version' field if still 2choose one" and reporter is astonished why not 'Summary' or 'Long description' field appears) 2. The condition "Click into "Long description" after Summary is complete should be removed 3. Help should be completed, no input should be without help
(In reply to comment #2) > Not a bug, it's a feature, but really worrying. The Submit button appears after > you have typed at least 10 (?) characters into the Summary pane And I had typed only three characters, OK. > Suggestion for a solution: > 1. Fields with missing contents should be marked light red background, > red border or similar (samd for 'Version' field if still 2choose one" > and reporter is astonished why not 'Summary' or 'Long description' > field appears) > 2. The condition "Click into "Long description" after Summary is complete > should be removed Rather than remove this condition completely I'd say: Instead of "no submit button", have a greyed-out inoperative submit button *and* right next/under/before/... it, a text that says: IF short description is too short THEN say "Subject: Please enter a short one-line summary of problem" ELSE IF long description has not been edited THEN say "Long Description: Please explain your problem in detail and how to reproduce it" ELSE enable submit button If that's too hard to code, then the standard "submit button is there but does alert(error_message) if conditions not fulfilled" would be OK, too, and still better than the current.
See http://wiki.documentfoundation.org/Bug_Submission_Assistant#Installation_and_maintainance where to start debugging.
In the time the requirements are changed: - minimal of 4 characters in subject - long description needs to be changed Also the box that isn't ok will be turned red. So I think the problem is solved. Please reopen if you want more to change
Migrating Whiteboard tags to Keywords: (ProposedEasyHack -> needsDevEval, SkillJavaScript TopicWeb TopicQA ) [NinjaEdit]