On Sun, Jun 05, 2016 at 02:25:11PM +0200, Ben Bucksch wrote:
> If your worry is PageUp/Down, why don't you exclude these keys from the
> input field and let them bubble up? (Possibly only in the focus() case.)
> Meaning: The focus is in a single-line text field, and the user presses
> PageUp. What should happen? I would claim that it's reasonable to make the
> page scroll.
>
> If that's not the case right now, it might be as easy as avoiding adding |if
> (key != pageUp ...) {| around event.preventDefault(); inside
> <input>.onKeyPress(event).
it is not only PageUp/Down, after reading 10 pages through a text it does
not matter at all which keypress ruins my reading experience.
Another thinkable strategy would be to make the input field loose focus once
the user did scroll, however I am wondering if this might still break some
sites that relay on .focus()?
Even than there would be still the vast majority of sites where I don't
want focus to work because the faint advantage of saving one click/tap
won't outweigh the loss of functionality when key bindings don't work.
> Just because some site are wrongly setting focus is not a good enough reason
> to entirely break it. You'd also break those pages who use it properly.
any idea how to identify those that use it properly? Or how to identify
those that would break in a bad way?
Richard
--
Name and OpenPGP keys available from pgp key servers
_______________________________________________
mobile-firefox-dev mailing list
mobile-firefox-dev@mozilla.org
https://mail.mozilla.org/listinfo/mobile-firefox-dev
