We have moved to a new Sailfish OS Forum. Please start new discussions there.

Don't enforce focus to textfield [answered]

asked 2013-12-24 21:18:45 +0200

rasjani gravatar image

updated 2014-01-19 20:12:07 +0200

nephros gravatar image

Browsing on sites with auto-focused text fields (like Together) is a bit hard because search box gets autofocus. This enforces browser to show virtual keyboard which takes half of the screen estate.

edit retag flag offensive reopen delete

The question has been closed for the following reason "the question is answered, an answer was accepted" by LaruX
close date 2013-12-29 13:10:32.939668


i was just thinking same thing... thanx for bringin this up...

Miki ( 2013-12-24 22:12:14 +0200 )edit

Yeah I keep hitting space to page down on desktop and failing

sp3000 ( 2013-12-24 23:17:10 +0200 )edit

I also try to scroll down with down-arrow, which doesn't work because of this.

pnuu ( 2013-12-25 17:15:14 +0200 )edit

Tried Together with the phone, and as the keyboard will auto-open, there's not much space left on the screen.

pnuu ( 2013-12-26 14:49:04 +0200 )edit

I had filed a similar issue -- https://together.jolla.com/question/2615/remove-on-screen-keyboard-pop-up-on-opening-web-pages/ . I think this is more browser related than website, as N9 (or iPhone..) do not have this behavior.

Hess ( 2013-12-26 15:46:56 +0200 )edit

3 Answers

Sort by » oldest newest most voted

answered 2013-12-27 03:38:00 +0200

foss4ever gravatar image

updated 2014-01-07 05:17:04 +0200

Well, beacuse it is my browser and I want to use it with my preferred way, the client app can and should have options to configure their behaviour to user's likings and not the websites.

Here is a snippet applicable to Mozilla/Gecko engines to define security policies to disable form focusing tthat is enforcable from client-side. So as web pages can automatically focus a form when a page load, this can be disabled for specific sites doing this:

user_pref("capability.policy.policynames", "nofocus");
user_pref("capability.policy.nofocus.sites", "http://www.example.com");
user_pref("capability.policy.nofocus.HTMLInputElement.focus", "noAccess");

And @Artem, regarding to your comment that "sites should be allowed to decide where my focus in the page is", I fully disagree. It is is the user/browser who should have the authority to decide this.

Just my 2 cents to this discussion ;)

edit flag offensive delete publish link more


Is there a default CSS file, or something where I could paste those lines? Useful for those of us that do not want the web page to decide focus.

00prometheus ( 2014-03-21 01:28:14 +0200 )edit

answered 2013-12-27 03:42:29 +0200

updated 2013-12-27 03:42:53 +0200

I think this is a bug with the "together" site, rather than the browser. The site is applying focus to the search input field with javascript. If the (now standard) html5 way of applying focus (<input type="search" placeholder="foo" autofocus>) is used, then the field still receives focus (and is useful on desktop browsers), but on the phone the keyboard isn't immediately displayed.

edit flag offensive delete publish link more



The selected answer does not solve the question.which was abt visibility and usability of web-pages where mobile browser displays the virtual kbd in response to sites auto-focus request.

foss4ever ( 2013-12-31 19:30:32 +0200 )edit

I agree, answer does not solve the question. This auto-focus thing is problematic also with other pages which sets focus automatically. One example is www.foreca.fi where site is almost unusable because of auto-focus. I think some browser based fix should be done.

Joni ( 2014-01-07 08:53:34 +0200 )edit

This question should be re-opened cause the issue still exists.

foss4ever ( 2014-01-09 06:52:59 +0200 )edit

answered 2013-12-27 02:43:26 +0200

Artem gravatar image

updated 2013-12-27 03:14:03 +0200

That is indeed annoying at together, however, not showing keyboard on text field focus is wrong and actually even technically difficult as modern web sites can set focus to this or that field whenever they want. Sites should be allowed to decide when they want to have a text input focused and a good touchscreen browser should show keyboard then.

The better solution IMHO is to:

  1. Realize that focusing on the input field right away is actually not the best practice in general and stop doing it at Together

  2. Let the user hide the keyboard easily (e.g. by swiping down). At the moment the only way to close it is to click on the non-active web-page space and on many websites including Together there's almost none non-active whitespace.

edit flag offensive delete publish link more


I truly hope that default settings will follow not anybody's preferred way, but W3C way whichever it is :) I think it's closer to my point of view, but I haven't actually checked. Maybe W3C says nothing about onscreen keyboards

Artem ( 2013-12-27 03:45:11 +0200 )edit

Are you @Artem seriously saying that sites can do whatever they wish with users browser? And you even claim that this is somehow a W3C-recommendation..!? The problem is more on sites that use non-standard (and malicious) ways to do things with the browser, and for this browsers can enfotce and mplement securites to prevent this. (e.g. blocking ads etc.)

foss4ever ( 2013-12-27 03:54:02 +0200 )edit

Nope, I think that showing keyboard on input focus is W3C way, because that's how iOS browser works, I never bothered to check. I do hope that people who will implement fix to this question will care to check W3C position if any,

Artem ( 2013-12-27 04:00:33 +0200 )edit

If e.g. ads-sites keep pushing stuff to user/browser but are being technically compliant to W3C-recommendations, don't you think that users should still be allowed to opt-out and disable things happening in their browser if it is either, a privacy or security concern, makes site's usablity worse, or completly makes the site unfunctional, or simply is something that the user does not want?

foss4ever ( 2013-12-27 04:06:53 +0200 )edit

Swiping down VKB already works.

veskuh ( 2013-12-27 11:32:56 +0200 )edit

Question tools



Asked: 2013-12-24 21:18:45 +0200

Seen: 1,106 times

Last updated: Jan 07 '14