From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050922 Fedora/1.0.7-1.1.fc4 Firefox/1.0.7 Description of problem: The search field provided to users in the "report bug" form on bugzilla.redhat.com is missing a handler for the return key. If the user enters some search terms and presses return, the search will fail with the error: "Unknown Keyword" . If they click "search", the search completes fine (in a new window - grr - and middle click doesn't work). The full error with the suggested example search (which is evidently well aged, being a search for "netscape crash java" sans quotes) is: "Unknown Keyword "netscape crash java is not a known keyword. The legal keyword names are listed here. "Please press Back and try again." The front page search is just fine, it only seems to be the search in the "new bug" form. Perhaps the "new bug" form should also use onSubmit= instead of onClick= ? The sample search, by the way, finds a bug so prehistoric that it looks like it should be in a museum. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Log in to bugzilla 2. Visit https://bugzilla.redhat.com/bugzilla/easy_enter_bug.cgi 3. Type some search terms into the search form 4. Press <return> or <enter> to submit the search Actual Results: Bugzilla complains that the keywords provided were invalid. Expected Results: A page loading with the bugzilla search results. Additional info: Firefox 1.0.7, FC4
I concur. It seems the backend is attempting to look in the keyword field within the database rather than in the summary. (or the summary text needs to be changed to keyword). Hence, when user enters non-legit keywords the search always fails. Pretty important to fix this as this is the way in generating a bug report, and if search fails to find bugs that should have been shown, there is likely to be duplicates entered.
Looks like the page is not causing form submission generated by enter to go through: function SearchForBugs( words, searchRadio ) This has another side affect: if no search term is entered, then a search begun by the enter key, it takes a couple of minutes of 5 step standby.gif scrolling through, before I cancelled the web page load. Hopefully it's not doing bad things to the bz db server (dos-ish).
Red Hat Bugzilla is now using version 3.2 of the Bugzilla codebase and therefore this bug will need to be re-verified against the new release. With the updated code this bug may no longer be relevant or may have been fixed in the new code. Updating bug version to 3.2.