Closed Bug 97348 Opened 23 years ago Closed 23 years ago

RFE: Bugzilla preference for onFocus for INPUT to change radio button

Categories

(Bugzilla :: Creating/Changing Bugs, enhancement)

2.13
enhancement
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: alex, Assigned: myk)

References

()

Details

[This section from bug 96990]

The above url is just an example. But, suppose that you wanted to mark is as a
dupe. To review, the steps to mark a dupe:

1. Load bug (obviously)
2. Click on INPUT for "Resolve bug, mark it as duplicate of bug"
3. Enter a bug number there.
4. Click the radio button that corresponds with "Resolve bug..."
5. Commit bug.

However, through JavaScript, it  would be possible to have the radio button
automagically select itself whenever the user puts his/her cursor on the INPUT
box, through using the onFocus function of INPUT. 

Of course, this functionality for set-as-duplicate is just an example. For
instance, it could also be applied to the "Reassign bug to..." and "Change
resolution to" fields.

[End of excerpt from bug 969990]
And, in that bug, Myk Melez made a good point that using onFocus could cause Bad
Things for those who exclusively use a keyboard (such tabbing around to go
between form fields).

But, I still think there are benefits to onFocus. So, I request
onFocus-vs-onChange as a Bugzilla preference. That way, everyone can be happy :-).
Using "onFocus" creates a confusing, illogical user interface, and the benefits
are very limited, so I am not inclined to make this a settable parameter just as
I am not inclined to implement it for everyone.  Marking WONTFIX, but keep in
mind two options:

1. Bugzilla is scheduled to be templatized, after which installations will be
much more easily able to make these kinds of changes.

2. Consider reopening the original bug and change the functionality from
"onfocus" to "onkeypress if there is text in the field".
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WONTFIX
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.