| Summary: | Webkit-based Browser doubles characters entered into text fields | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Thorsten Vitt <thorsten.vitt> |
| Component: | SWT | Assignee: | Grant Gayed <grant_gayed> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | eclipse.felipe, jasonho0504, mayank_4042, pwebster |
| Version: | 3.7.1 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux-GTK | ||
| Whiteboard: | |||
|
Description
Thorsten Vitt
Library versions involved:
libwebkit-1.0-2 version 1.2.7-1~mmwkt1
libgtkhtml2-0 version 2.11.1-2ubuntu3
I don't see this problem, and no one else has reported it, so it seems to be something particular to your setup. Are you running with the download of just plain eclipse 3.7.1 (no additional apps installed)? Is there any unusual setup on your machine (eg.- accessibility turned on, etc.)? *** Bug 372261 has been marked as a duplicate of this bug. *** Grant Gayed, I agree with Thorsten Vitt. This issue is analogous to the issue that I am facing too. Brief Intro :- When we use eclipse embedded internal browser and open any html page(having link for PDF file)and then you try to directly “open”(not save) the PDF file and then try to navigate from PDF(by clicking the link for html page from PDF file) to any html page(which is having input text box) causes characters be displayed twice on a single keypress inside the input text box. i.e 'a' is printed as 'aa' on a single key press. I am using SWT 4.1. Is this BUG has been addressed or still in discussion? Is there some work around for this issue available? Thanks, Mayank Just to debug it more, I have added a keyListener to the browser object and noticed that method "public void keyPressed(KeyEvent e)" gets called two times and method "public void keyReleased(KeyEvent e)" is called up one time. Thought that might help. Grant Gayed, Are we going have any update on this issue in the coming future release? Or is it still a topic of further discussion? Issue no longer reproduces in webkit2. Please open if issue perists for you. |