Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 367675 - Page Down, Home and rest don't work in Browser
Summary: Page Down, Home and rest don't work in Browser
Status: CLOSED DUPLICATE of bug 354745
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.7   Edit
Hardware: PC Windows XP
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-31 01:00 EST by Chavaranis Nikolaos CLA
Modified: 2012-01-04 03:42 EST (History)
5 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 Chavaranis Nikolaos CLA 2011-12-31 01:00:22 EST 
Build Identifier: I20110613-1736

The embedded browser that is used in JDT to display the Java API documentation does not respond to Page Down, Page Up, Home, and End keys. I can only use the context menu on the scroll bar to perform these functions or the Space key which works normally.

I suspect the problem is not JDT-specific since the embedded browser is not a JDT-specific feature.

I am refering to the keybord - not numpad - page navigation keys as I am using a laptop keybord.


Reproducible: Always

Steps to Reproduce:
1. Open a Java class source file in JDT that uses a Java API class.
2. Hover over the Java API class and click on a link in the javadoc that will pop up.
3. Try to use any of the Page Down, Page Up, Home, or End keys.
Comment 1 Markus Keller CLA 2012-01-03 13:44:51 EST 
On Windows 7, these keys work for me in the browser hover in 3.7 (I20110613-1736) and in I20111213-1443.

In 3.7 and 3.7.1, they indeed don't work in the internal web browser editor, which e.g. opens when you select a Java identifier and choose Navigate > Open Attached Javadoc (or click the rightmost button in the Javadoc hover toolbar).

In I20111213-1443, they also work in the web browser editor, so it looks like this has been fixed in the 3.8 stream.
Comment 2 Grant Gayed CLA 2012-01-03 16:22:09 EST 
Yes, this is fixed in the 3.7.2 and 3.8 streams, closing report.

*** This bug has been marked as a duplicate of bug 354745 ***