[Webkit-unassigned] [Bug 10221] [S60] no key events for text input

bugzilla-daemon at opendarwin.org bugzilla-daemon at opendarwin.org
Thu Aug 3 11:35:16 PDT 2006


http://bugzilla.opendarwin.org/show_bug.cgi?id=10221





------- Comment #5 from dacarson at gmail.com  2006-08-03 11:35 PDT -------
(In reply to comment #4)
> I would expect that key press events would match the keys that were pressed by
> the user (0-9, #, *, or more simply the keys if you happen to have a qwerty
> device).  

ok. IMHO, I think that this would be ok, as in my experience I have only seen
scripts that are triggered from the key events but do not manage the input text
using information from the key event. They query the input field for the text.
There is a technical issue in the Symbian platform as the input box hijacks the
keyboard and the application does not see any events while an input box has
focus. A workaround for this would be required.

> Ideally, the input mode would also be available via DOM (even more
> ideally, it would be settable for the current input), but I wouldn't expect
> that without DOM extensions.  In the absence of this, the JS can look at both
> the key event and the contents of the text box and decide what it thinks is the
> appropriate behavior.  

Yes. As long as existing web content is not broken by this behaviour.

> Understood that non-latin entry modes would bring their own complications, in
> this case the script would need to find another solution or disable whatever
> behavior it wanted to use -- I don't think the answer is to consider the text
> box "out of bounds" for scripts.

Definitly agree, the text box should not be out of bounds. Actually in the
current
ToT development, the input boxes are no longer platform controls, but rather
are html controls. They are essentially editable HTML DIVs. It will be 
interesting to see how this is handled in the current Symbian ToT port going
on.

> Of course, this is all predicated on scripts being written for mobile browsers.
>  Is the concern really that the browser is trying to protect itself from
> desktop pages?

The concern is that the mobile browser needs to provide a true web experience
and steps are taken in a way to ensure that the majority on existing web
content
works and is usable on the mobile browser.


-- 
Configure bugmail: http://bugzilla.opendarwin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.



More information about the webkit-unassigned mailing list