Bug 2769 – RSS Reader: Shift-space does not scroll up (inconsistent with Browser)

Bug 2769 - (int-110122) RSS Reader: Shift-space does not scroll up (inconsistent with Browser)

(int-110122)
Summary:	RSS Reader: Shift-space does not scroll up (inconsistent with Browser)

Status:	RESOLVED FIXED

Product:	UI Specification
Component:	General
Version:	5.0-beta
Platform:	All Maemo

Importance:	Low minor (vote)
Target Milestone:	5.0 (1.2009.41-10)
Assigned To:	Mikko Nurmi
QA Contact:	ui-specification-bugs

URL:
Keywords:

Depends on:	int-88381
Blocks:
	Show dependency tree

Reported:	2008-01-13 15:37 UTC by Jussi Kukkonen
Modified:	2009-05-15 14:33 UTC (History)
CC List:	2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note

You need to log in before you can comment on or make changes to this bug.

Description Jussi Kukkonen (reporter) 2008-01-13 15:37:21 UTC

STEPS TO REPRODUCE THE PROBLEM:
press shift-space when focus is in the feed contents on the right.

EXPECTED OUTCOME:
page should scroll up about one page height, just like the browser does.

RSS reader does support pressing shift to scroll down.

ACTUAL OUTCOME:
Page scrolls down.

REPRODUCIBILITY:
always

OTHER COMMENTS:
This combined with bug 2598 makes the RSS reader difficult to use with keyboard
only.

Comment 1 Andre Klapper maemo.org

2008-10-20 14:48:37 UTC

Pressing Shift already results in focus setting in the text entry field at the
bottom, also see bug 3322.
Browser works as described, yes.

Comment 2 Andre Klapper maemo.org

2009-04-02 13:05:54 UTC

Most probably not important enough to fix for Diablo (hence WONTFIX), but would
be nice to have this consistent for Fremantle.

Comment 3 Quim Gil nokia

2009-04-07 00:26:19 UTC

In Fremantle w14 pressing both space and shift-space make the news scroll down.

Comment 4 Andre Klapper maemo.org

2009-04-07 15:32:36 UTC

Currently no shortcut for anything related to the "Space" key is listed as
global or browser/RSS application specific in the Fremantle Shortcuts UI
specification, hence a UI spec issue.

Comment 5 Andre Klapper maemo.org

2009-05-15 14:33:11 UTC

This has been fixed in the Specification now.