Red Hat Bugzilla – Bug 820393
extra input screen depending on if "enter" was pressed or a UI button clicked
Last modified: 2013-01-29 10:41:55 EST
Description of problem:
when launching an AppForm at the following screen:
If you click the icon "launch" you are taken to this screen:
However, if you hit "enter", instead you are taken to this:
Which asks for additional input. After clicking "next" or hitting "enter" you are then taken to:
James, I am not seeing this... if I hit enter using Firefox 12.0, nothing happens on this screen. Different browser?
We this using the Firefox included in RHEL 6.2. I believe it was 3.6.24, but I could be wrong. Can you test using Firefox in RHEL 6.2 or the lowest supported version of Firefox supported for CF 1.0?
James I am not seeing this using RHEL 6.2's firefox v3.6.24. Could you retest and provide more information please.
I'm u sing Firefox 12.0 on Mac, and this behavior occurs. I also tested with Google Chrome 19.0.1084.46 and Safari 5.1.7 on Mac; Firefox 12.0 on Linux and Internet Explorer 9 on Windows. This still occurs with all of the browsers. However, I discovered while using Internet Explorer that pressing "enter" is actually highlighting and activating the "back" button.
I believe this is why it was odd to me. Here is the original procedure I used when reporting this behavior to James:
Administer -> Content -> Choose Catalog -> Choose Blueprint -> Launch
At this point, giving a name and pressing "enter" on any of the browsers mentioned above will actually go "back" to the "Application Details" screen (which by following this workflow has not been seen yet, which is why it is odd).
However, if you launch an application via this method, it makes a bit more sense:
Monitor -> New Application -> Fill in Application details -> Next
At this point we are at the same screen, but hitting "enter" goes back to the "Application Details" screen, instead of activating "Launch" which seems to be the most intuitive result of pressing "enter".
I think changing the default action when hitting "enter" to "Launch" instead of "Back" might help.
Let's throw this back on the pile to re-test.