Uzbl

Tasklist

FS#171 - problem with events coming in too fast

Attached to Project: Uzbl
Opened by Anonymous Submitter - 2009-12-27 01:30:49 AM
Last edited by Anonymous Submitter - 2010-03-21 03:05:57 PM
Task Type Bug Report
Category other
Status Closed
Assigned To No-one
Operating System All
Severity Medium
Priority Normal
Reported Version Development
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Run something like the following while a form field is focused:
echo "set mode =" > /tmp/uzbl_fifo_14680067 ; echo "set mode = insert" > /tmp/uzbl_fifo_14680067

It will enter insert mode, but typing does not go into the form field. If the commands are run separately then it works fine. Even inserting a 1ms sleep in between works fine.
This task depends upon

Closed by  Anonymous Submitter
2010-03-21 03:05:57 PM
Reason for closing:  Won't fix
Additional comments about closing:  I am working on a partial fix but this isn't a bug. When you `set mode =` the mode plugin automatically sets the mode to the default mode which will be received after the second `set mode = insert`. It's impossible for the mode plugin to know that you `set mode = insert` microseconds after you asked it to set the mode to the default mode.
Comment by Anonymous Submitter - 2009-12-27 01:57:17 AM
What is wrong with just the 'echo "set mode = insert" > /tmp/uzbl_fifo_14680067'?
Comment by modnaru (modnaru) - 2009-12-28 06:54:20 AM
I was modifying the hinting js script.

Inside clickElem(), with clearKeycmd() at the top, and going into insert mode below, the echoing is exactly the same behavior.
Comment by Anonymous Submitter - 2009-12-28 11:53:47 AM
This is a tricky case to deal with. This is the exact sequence of events you get when you 'set mode =' & 'set mode = insert':

--> VARIABLE_SET (u'mode str',)
--> CONFIG_CHANGED (u'mode', u'')
<-- set mode = command

--> VARIABLE_SET (u'mode str insert',)
--> CONFIG_CHANGED (u'mode', u'insert')
--> MODE_CHANGED (u'insert',)
<-- set status_background = #303030
<-- set mode_indicator = Ins
<-- set forward_keys = 1
<-- set keycmd_events = 0
<-- set modcmd_updates = 0
--> KEYCMD_CLEARED
--> MODCMD_CLEARED

--> VARIABLE_SET (u'mode str command',)
--> CONFIG_CHANGED (u'mode', u'command')
--> MODE_CHANGED (u'command',)
<-- set forward_keys = 0
<-- set mode_indicator = Cmd
<-- set status_background = #202020
<-- set keycmd_events = 1
<-- set modcmd_updates = 1
--> KEYCMD_CLEARED
--> MODCMD_CLEARED


I would suggest modifying the script not to send the 'set mode ='
Comment by Anonymous Submitter - 2010-03-18 08:50:26 AM
I'm experimenting with a fix for this problem in my (partially unpublished) plugins-upgrade branch.

Loading...