about summary refs log tree commit diff stats
path: root/inputfocus.c
Commit message (Collapse)AuthorAgeFilesLines
* Backout all changes I've made to inputfocus.c.Josh Rickmar2012-08-021-152/+44
| | | | | | | It was likely something from one of these changes that introduced all of our focus bugs. We can reintroduce these commits again, much slower than as I first developed them, and see if the focus issues still appear.
* More focus improvements. Disable the can-focus property for a lot ofJosh Rickmar2012-07-271-7/+29
| | | | | | widgets that should not be receiving focus, and try focusing the HTML body to try to prevent some of the focus bugs that have been popping up. No idea if this will solve our problems but they can't hurt.
* Oops, we don't want to blindly re-enter command mode if the oldJosh Rickmar2012-07-191-1/+0
| | | | focused entry is no longer active.
* Always be sure to check if t->active is still a valid entry beforeJosh Rickmar2012-07-191-11/+51
| | | | | | | | calling any DOM functions on it. It wasn't clear before, but the WEBKIT_DOM_IS_HTML_INPUT_ELEMENT() and WEBKIT_DOM_IS_HTML_TEXT_AREA_ELEMENT() macros also seem to work for this test, even after a DOM node has been destroyed and/or garbage collected.
* Modify the keybindings in the example config so they match the same asJosh Rickmar2012-07-181-8/+9
| | | | | | | | the keys[] structure in settings.c. Before, they were missing all the !'s to set the use_in_entry flag in struct key_binding. Also, change the behavior of command_mode to find the current active element and blur that instead of t->active (which was the "page's default" entry, set from javascript).
* Make the autofocus code a bit smarter by first saving the originalJosh Rickmar2012-07-051-3/+9
| | | | | | | | | text in the text box and seeing if it's any different from the new text before attempting to enter command mode. Before, there was only a check to see if there was any text. This also only sets t->active if it is not NULL, so only the page's default text entry box is ever used when entering insert_mode, instead of the last text box that was typed into.
* Use #if for the webkit_dom_html_element_click function, as it appears this ↵Josh Rickmar2012-06-291-1/+7
| | | | is new to webkit 1.8.x
* Save a pointer to the text entry box that is focused when the page isJosh Rickmar2012-06-281-38/+70
| | | | | | | | | | load for each tab. Try to use this first when using the insert_mode command instead of just focusing on the first text box in the html. Don't switch to command mode if the currently-focused input box contains any text in it. This prevents an annoying switch to command after the page has focused a particular element and the user has already begun typing something.
* Send a click event to the focused input fields so using theJosh Rickmar2012-06-281-0/+2
| | | | | insert_mode command runs any javascript the page may specify when clicking on the textbox.
* Use g_strcmp0() instead of g_str_equal() which is meant for hashJosh Rickmar2012-06-281-1/+1
| | | | tables.
* rename xxxterm to xomreroMarco Peereboom2012-05-171-1/+1
|
* include using <> instead of ; this will have falloutMarco Peereboom2012-01-231-1/+1
|
* this should work around a crash jy-p sawMarco Peereboom2012-01-121-14/+23
|
* add passthrough mode from: Maroun NAJM <bartender@c0decafe.net>Marco Peereboom2012-01-121-2/+0
|
* webkit 1.4 doesn't do dom right so use 1.5 as the cutoffmarco2011-11-151-1/+1
|
* add webkit 1.2 codeMarco Peereboom2011-11-111-2/+49
|
* Move focus stuff into it's own file.Marco Peereboom2011-11-111-0/+263
This will enable us to support webkit 1.2 as well.