| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
focused entry is no longer active.
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
| |
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).
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
is new to webkit 1.8.x
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
insert_mode command runs any javascript the page may specify when
clicking on the textbox.
|
|
|
|
| |
tables.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
This will enable us to support webkit 1.2 as well.
|