Closed
Bug 3249
Opened 26 years ago
Closed 25 years ago
[PP] second non-text key doesn't get through
Categories
(Core :: DOM: UI Events & Focus Handling, defect, P2)
Tracking
()
VERIFIED
FIXED
M6
People
(Reporter: akkzilla, Assigned: ramiro)
Details
Start viewer (no need to be in editor mode). Click somewhere in the middle of
some text to set the selection point. Hit right-arrow; notice that the cursor
moves right one character. Hit right-arrow again, notice that nothing happens.
The second key event apparently isn't getting through. Strangely, on the first
right-arrow, I see on stdout:
debug vk right
debug vk up
I don't know where the vk up is coming from, but that might be the problem.
Another instance of probably the same bug: hit scroll down; see the doc scroll.
Hit scroll down a second time; nothing happens.
I don't know whether this is XP or Linux only.
Reporter | ||
Updated•26 years ago
|
Summary: second non-text key doesn't get through → [PP] second non-text key doesn't get through
Target Milestone: M4
Reporter | ||
Comment 1•26 years ago
|
||
Marking M4 (really should have been M3) since this will seriously hurt usability
of the editor. Adding PP since it seems to be Linux only.
Updated•26 years ago
|
Assignee: joki → ramiro
Comment 2•26 years ago
|
||
This appears to be happening from inside gtkwindow.c in
gtk_window_key_press_event. Passing to ramiro for debugging inside gtk.
Assignee | ||
Updated•26 years ago
|
Status: NEW → ASSIGNED
I have a fix for this in my tree.
The problem was that the gtk signal was propagating up to the parent.
fix committed.
to verify:
run viewer
select menu item Tools->Editor Mode
hit left/right keys
the cursor should move back and forth
Assignee | ||
Updated•26 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Reporter | ||
Updated•25 years ago
|
Status: RESOLVED → REOPENED
Target Milestone: M4 → M6
Reporter | ||
Comment 6•25 years ago
|
||
This bug has recently come back -- I see it in the 5/19 build.
Reporter | ||
Updated•25 years ago
|
Status: REOPENED → RESOLVED
Closed: 26 years ago → 25 years ago
Reporter | ||
Comment 7•25 years ago
|
||
Now it's fixed again ... Not sure what happened, maybe it got affected by
something else that was going on in the widget or events stuff?
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
Comment 8•25 years ago
|
||
Using 6/16 Viewer on Linux platform, verified bug fixed.
Updated•6 years ago
|
Component: Event Handling → User events and focus handling
You need to log in
before you can comment on or make changes to this bug.
Description
•