Skip to main content

Search and Top Navigation

#5240 closed bug (wontfix)

Opened March 01, 2010 06:40AM UTC

Closed April 03, 2013 04:17PM UTC

Arrow keys don't work on datepicker field in Opera 9.64+

Reported by: Eyeless Owned by: Eyeless
Priority: minor Milestone: 1.11.0
Component: ui.datepicker Version: 1.7.2
Keywords: Cc:
Blocked by: Blocking:

Pressing arrow keys on field with attached datepicker does nothing. Ctrl+arrow combinations still work.

Appears in every Opera version from 9.6, including 10.50 beta.

All other major browsers work properly.

Attachments (0)
Change History (10)

Changed March 10, 2010 05:11PM UTC by scottgonzalez comment:1

milestone: TBD1.8

Changed March 04, 2011 12:40PM UTC by vadim.keller comment:2

_doKeyPress event handler filters out keys with codes 35,36,37,39 (END,HOME,LEFT,RIGHT). In Opera it prevents default action.

Changed May 06, 2011 10:31PM UTC by kzys comment:3

Changed November 11, 2011 09:52AM UTC by kAlvaro comment:4

The issue is more than cosmetic since some other keys are affected, including DEL or F5.

Test case:

Changed February 27, 2012 03:13PM UTC by jzaefferer comment:5

status: newopen

Still valid. That pull request did not help.

Changed July 12, 2012 09:12AM UTC by mrozik comment:6

tested in Opera 12.00 and kzys's pull request solved the problem (Ctrl + ArrowKeys, ArrowKeys works). Yet, Opera still filters AltKey + ArrowKeys, and doesn't even fire any of key events...

Changed October 11, 2012 02:43PM UTC by scottgonzalez comment:7


Changed April 03, 2013 03:24PM UTC by scottgonzalez comment:8

owner: → Eyeless
status: openpending

I updated the test case to use actual version numbers:

The ticket was filed against 1.7.2, but the test case used 1.8.13 (and latest core + latest theme).

I'm not seeing any problems in current Opera (12.14). Is this just no longer a problem or is the test case or bug description not adequate?

Changed April 03, 2013 04:15PM UTC by Eyeless comment:9

status: pendingnew

Tried the test case with latest Opera, looks like it is working now and issue is no longer actual.

Should there be any actions from me according to the issue lifecycle?

Changed April 03, 2013 04:17PM UTC by scottgonzalez comment:10

resolution: → wontfix
status: newclosed

Nope, thanks for confirming. I'll close as wontfix since it now applies only to browser we no longer support.