Bug 137800 - accessibility: not always possible to scroll page by keyboard
Summary: accessibility: not always possible to scroll page by keyboard
Status: RESOLVED UNMAINTAINED
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: 3.5
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
: 140236 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-11-24 03:08 UTC by Sami Liedes
Modified: 2012-06-18 14:04 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sami Liedes 2006-11-24 03:08:11 UTC
Version:            (using KDE KDE 3.5.5)
Installed from:    Debian testing/unstable Packages
OS:                Linux

The "Application selection" page of the new bug wizard is an example of a page that cannot be scrolled by keyboard without first clicking somewhere on the page by mouse. Fortunately such pages are rare.

In this case, I don't know where the focus is after entering the page (but it cannot be scrolled; this is common and occurs with other web pages). Tab moves the focus in this order:

1. URL bar
2. Google search bar
3. The Application list field (where arrow keys and PgUp/PgDn move the selection)
(#4 = #1)

In none of these is it possible to scroll the page by keyboard.
Comment 1 Stefan Monov 2006-12-09 01:48:39 UTC
Tab #4 allows me to scroll the page by keyboard (KDE 3.5.5, SUSE Linux 10.1).
Comment 2 Wolfram R. Sieber 2007-02-06 03:55:01 UTC
I've got a similar problem with the same distro, Debian Etch, KDE 3.5.5, up to date.

The Bug Entry Form of http://bugs.kde.org/wizard.cgi is another example of a page which cannot be navigated by keyboard at once. (I am working on a box that cannot attach any mouse (or any other pointing device), caused by missing physical space.)

To become able to navigate the page, me too have to hit the Tab key several times to get the focus to the browser. -- No idea, where it rests before entering the location bar, but the browser area, for sure, it's not.


A similar bug report I filed somewhere else, in the 141,000s, iirc. I'll look it up. Maybe it's a dublicate of this one here.
Comment 3 Wolfram R. Sieber 2007-02-06 03:58:01 UTC
Is bug #140236 a duplicate of the one described by Sami?
Comment 4 Marius 2007-02-16 20:39:58 UTC
I can confirm this in 3.5.6. It seems to only happen if you click on a button (not regular link) to go to a new page.... (or maybe its the fact that its a new page but with the same url?)

If you alt+tab to another app and then back it works again.

Ironically http://bugs.kde.org/wizard.cgi  is the best example if this bug. Click continue there and then hit ctrl, no access key boxes appear.
Comment 5 Marius 2007-02-16 20:42:55 UTC
Oh yea, i was just focusing on the ctrl (access keys) shortcut key not working, but it seems to apply to all keyboard navigation aswell.

This reminds me alot of a simular bug i filed for kpdf.
http://bugs.kde.org/show_bug.cgi?id=136702
Comment 6 lexual 2007-05-17 04:35:57 UTC
*** Bug 140236 has been marked as a duplicate of this bug. ***
Comment 7 Henrik Skov Midtiby 2008-05-21 11:00:56 UTC
Works for me.
I tried to reproduce this bug on Ubuntu 8.04 with KDE 4.0.3.

Method used:
* Started konqueror
* Entered http://bugs.kde.org/wizard.cgi in the address bar and pushed enter
* I am able to scroll the webpage up and down using the <up> and <down> buttons.
Comment 8 Rui G. 2008-06-04 02:06:08 UTC
I confirm this bug in 3.5.9 . And with trunk r816330 , in the application selection page, instead of getting stuck in application list, it gets stuck in the application list filter button.

 From that point on, I can't only resume focus through alt+f ( or similar) and using tab again to focus on the page and being careful to not use tab if I want to scroll further down with keyboard.
Comment 9 Myriam Schweingruber 2012-06-18 14:04:08 UTC
Message from the Bugsquad and Konqueror teams:
This bug is closed as outdated, as we do not have the manpower to maintain the KDE3 version anymore.
If you still can reproduce this issue with Konqueror 4.8.4 or later, please open a new report.
Thank you for your understanding.