Issue 106870 - [CWS printerpullpages] Ignore ENTER when entering print preview page numbers
Summary: [CWS printerpullpages] Ignore ENTER when entering print preview page numbers
Status: CLOSED WONT_FIX
Alias: None
Product: General
Classification: Code
Component: ui (show other issues)
Version: DEV300m61
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: philipp.lohmann
QA Contact: issues@framework
URL:
Keywords: usability
Depends on:
Blocks:
 
Reported: 2009-11-12 22:23 UTC by christoph
Modified: 2010-02-23 15:40 UTC (History)
3 users (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description christoph 2009-11-12 22:23:29 UTC
In the new printer dialog, the user is able to enter page numbers for the print
preview (e.g. entering 25 directly shows the 25th page of the printout).

Issue: Some people might use Return or Enter to confirm the entered number, but
this does not change the print preview, it directly executes printing. This
should be avoided, since the likeliness of mistakes is high.

Rationale: This is different to other elements in the print dialog, e.g. the
manual print ranges definition. Since the print preview might be used to look
what pages to print, pressing Enter is - from the user's point-of-view - a
disaster, because print jobs (especially large ones) cannot be sufficiently
aborted (think of network printers in businesses). It is also costly, so our
product may get blamed...

Proposal: Ignore Return/Enter when the focus is in the number field of the print
preview.

@es: Is that okay from the accessibility point-of-view?
Comment 1 eric.savary 2009-11-13 10:09:09 UTC
+2! :)
I completely agree.
Comment 2 philipp.lohmann 2009-11-13 10:21:50 UTC
That's a IMHO bad idea. Enter confirms every dialog, so it should do here. If
the user "accidentally" hits Enter, well, he won't anymore after the third time.
Comment 3 philipp.lohmann 2009-11-13 10:33:07 UTC
confirm
Comment 4 christoph 2009-11-22 16:04:56 UTC
Added keyword
Comment 5 philipp.lohmann 2010-02-12 13:26:29 UTC
Is anybody able to convince me why this would be a good idea ? I'd like to close
it else.
Comment 6 philipp.lohmann 2010-02-23 15:39:08 UTC
It seems not.
Comment 7 philipp.lohmann 2010-02-23 15:40:00 UTC
closing