Closed Bug 201944 Opened 22 years ago Closed 22 years ago

In page keyboard navigtaion doesn't work in embedded apps

Categories

(Core Graveyard :: Embedding: GTK Widget, defect)

x86
Linux
defect
Not set
major

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: lwillis, Assigned: blizzard)

References

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4b) Gecko/20030404
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4b) Gecko/20030404

Visiting any page which can be scrolled, neither the cursors, nor PageUp/PageDown will actually scroll the page. Additionally the cursor keys/Home/End etc. do not work when entering text in <textarea> sections of web forms

Reproducible: Always

Steps to Reproduce:
1. Open an embedded app based on current Mozilla CVS (Epiphany or TestGtkEmbed can be used to reproduce this
2. Visit a page that requires vertical scrolling, and wait for it to load
3. Try to scroll up or down using Up/Down cursor keys or Page Up/Page Down keys
4. Now visit a page with a web form, start writing text into any text box. Try to move around in the text using left/right cursors, Home/End etc.

Actual Results:  
After point 3 the page did not scroll
After point 4 the cursor was not moved within the text box in line with the keys pressed.

Expected Results:  
At point 3 the page should have scrolled
At point 4 the cursor should have moved.

Reproduced with latest Mozilla CVS as of 13/04/2003 (Can't get any later since anonymous CVS mirror is currently down)
Hmm.  I wonder if the XIM patch busted something.
Blocks: gtk2
I just tested this in my trunk build and it's working in TestGtkEmbed.
This is affecting Camino as well. I saw it yesterday on a build I pulled in the afternoon. Last night I pulled and built again and it's still there.
Not being seen today on
<Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.4b) Gecko/20030418
Chimera/0.7+>, but was present a few days ago. Perhaps it has been fixed.
I believe it has. My most recent build did not have this problem.
Marking WORKSFORME based on comments.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
For reference I also see the problem as being resolved in recent builds.
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.