Description of problem: Pressing return during writing 'Summary' is dangerous thing and could happen by accident. I'd suggest to add at least option configurable by bz user - to query Yes/No for submitting bug in this case - thus I'd not create nearly empty bugzilla entries... Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Press Enter/Return - implicit Submit Bug happens Expected results: Configurable option for user login to query before bugsubmition (preferably not in case I would hit SubmitBug with mouse) Additional info:
I encountered this today; I was typing in the subject of my bug, used the mouse scroll wheel to scroll in a terminal window to find the precise error message I was reporting, pressed enter (which I thought was going to the terminal window but instead went to firefox), and my bugzilla bug submitted itself with half of a subject line and everything else blank. I copied the text from the bug description window to the 'additional comment' window and filled it in, but that's a suboptimal workaround. Zdenek Kabelac suggested at least making it a configurable option, but I don't see a situation where anyone would want a shortcut to submit just a summary line. The current behaviour is a bug. Thanks for looking into this!
As part of the recent Bugzilla 2.4 upgrade the Bugzilla team are cleaning up bugs opened against old versions of Bugzilla. This bug has been flagged as an old bug and will be CLOSED WONTFIX in 7 days time. If you believe this bug is an issue in the latest Bugzilla version please comment on this bug within 7 days. Doing so will ensure this bug is not closed automatically. Thanks, the Bugzilla team.
As part of the recent Bugzilla 4.2 upgrade the Bugzilla team are cleaning up bugs opened against old versions of Bugzilla. This bug has been flagged as an old bug and will be CLOSED WONTFIX in 7 days time. If you believe this bug is an issue in the latest Bugzilla version please comment on this bug within 7 days. Doing so will ensure this bug is not closed automatically. Thanks, the Bugzilla team.
Since I've easily entered bugzilla again (Bug 826668) - bug is still present. Maybe devel may at least try to test reported bugs (especially when it's so easy)
*** Bug 826658 has been marked as a duplicate of this bug. ***
It's not easy when there are hundreds of bugs opened. This isn't worth doing.
*** Bug 519251 has been marked as a duplicate of this bug. ***
Not worth doing? <input id="txt" type="text" onKeyPress="if (event.which == 13) return false;"></input> And suddenly the hundreds of bogus half-done bug entries drops to nothing...? (Code copied from http://stackoverflow.com/questions/1567644/submit-form-problem-enter-key )
*** Bug 677601 has been marked as a duplicate of this bug. ***
(In reply to comment #6) > It's not easy when there are hundreds of bugs opened. > > This isn't worth doing. You mean it's not worth to recheck opened bugzillas - or to fix this BZ ? Do you want to open new BZ or would you please try to apply at least comment 8 ?
We will not be doing this.(In reply to comment #10) > (In reply to comment #6) > > It's not easy when there are hundreds of bugs opened. > > > > This isn't worth doing. > > You mean it's not worth to recheck opened bugzillas - or to fix this BZ ? We will not be doing this. > Do you want to open new BZ or would you please try to apply at least comment > 8 ? No. That would generate one million hate mails, and it's not worth our time to make this optional.
(In reply to comment #11) > > > Do you want to open new BZ or would you please try to apply at least comment > > 8 ? > > No. That would generate one million hate mails, and it's not worth our time > to make this optional. I do not get it - what is so hard to implement comment 8? It must be also fairly easy to compare if the new bugzilla is unmodified/empty and avoid submitting such bugreport. Compare this amount of time with the time of many other developers that get pointless empty bug reports which some have to manage (read/close) (Not to mentioning the time we've already spent with this bugzilla)
(In reply to comment #12) > (In reply to comment #11) > > > > > > Do you want to open new BZ or would you please try to apply at least comment > > > 8 ? > > > > No. That would generate one million hate mails, and it's not worth our time > > to make this optional. > > > I do not get it - what is so hard to implement comment 8? I didn't say the change in #8 was hard, I said it would offend the vast majority of users and generate a lot of hate mail. Doing it _properly_ would involves making it optional and defaulting it off, and this is not worth our time. > It must be also fairly easy to compare if the new bugzilla is > unmodified/empty and avoid submitting such bugreport. > > Compare this amount of time with the time of many other developers that get > pointless empty bug reports which some have to manage (read/close) > (Not to mentioning the time we've already spent with this bugzilla) You can feel free to make up numbers and make straw-man arguments out of them, and even to waste my time. I just won't allow this kind of thing to distract our 1 Bugzilla developer. If you really want it added take it upstream.
(In reply to comment #13) > (In reply to comment #12) > > (In reply to comment #11) > > > > > > > > > Do you want to open new BZ or would you please try to apply at least comment > > > > 8 ? > > > > > > No. That would generate one million hate mails, and it's not worth our time > > > to make this optional. > > > > > > I do not get it - what is so hard to implement comment 8? > > I didn't say the change in #8 was hard, I said it would offend the vast > majority of users and generate a lot of hate mail. > Maybe I'm getting lost here - so it IS actually a 'feature' and not a bug, that pressing Enter key while typing Bugzilla title and having an unmodified rest of Bugzilla page is the behavior users would miss and you are afraid you would get tons of hate mails because the user cannot report empty Bugzilla ?? Do you have some statics how often this is useful?
This is the behaviour as supplied by upstream, any affects of this are not sufficient enough for us to spend time on it. If you don't like the behaviour, take it upstream.
*** Bug 975194 has been marked as a duplicate of this bug. ***
It looks like a perfect application for a greasemonkey script that triggers on all bugzilla pages and inserts code from https://bugzilla.redhat.com/show_bug.cgi?id=637163#c8
I still think this is a bug; it trips me up with some regularity ("experience is recognizing your mistake when you make it again"). To work around this issue I started NOT FILLING OUT the mandatory fields (bug title/subject and component name) until I am done with the Description pane. This way, even if I accidentally press Enter the incomplete bug is not submitted. I would like the maintainers and/or upstream to reconsider this issue. What would be the best procedure to raise this issue---reopening this bug here? direct contact with upstream? and if so, by what channel?
(In reply to Przemek Klosowski from comment #18) > I would like the maintainers and/or upstream to reconsider this issue. What > would be the best procedure to raise this issue---reopening this bug here? No, we are unlikely to make a change unless upstream do. > direct contact with upstream? and if so, by what channel? The best thing to do is file a bug in the upstream Bugzilla at https://bugzilla.mozilla.org, product: Bugzilla, component: User Interface.