On-screen keyboard should come up automatically when the user opens the find in page toolbar, and potentially in other cases

NEW
Unassigned

Status

()

Firefox
Keyboard Navigation
2 years ago
a year ago

People

(Reporter: Gijs, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(firefox48 affected)

Details

(Reporter)

Description

2 years ago
Bug 1239744 comment 19 pointed out that that bug regressed "find in page" functionality for tablet users. Bug 1239744 comment 20 also included "new tab", which is more debatable, IMO -- if the user wants to go to a frequently visited site, for which they'd want to tap one of the tiles, obscuring half the screen with an on-screen keyboard doesn't seem like the most helpful thing to do.

Jared, what do you think?
Flags: needinfo?(jaws)

Comment 1

2 years ago
Is there data that tells us what touchscreen users do when they open a new tab? I suspect by far the most common thing users do when they open a new tab is tap the URL so they can start typing. Also, on the surface pro 4 at least, when the on-screen keyboard is up on the new tab page, it only covers the bottom 4 suggested site tiles, the top 4 suggested site tiles are not covered, so if you were to automatically bring up the on screen keyboard when someone opens a new tab, you would get the best of both worlds pretty much (at least on the surface pro 4. perhaps having the keyboard automatically pop up on smaller tablets would cover all of the suggested tiles?)

Comment 2

2 years ago
also, for what it's worth, for 2 or 3 releases Firefox WAS bringing up the on screen keyboard automatically when I would open a new tab, and when the change was made to no longer open it automatically, it felt like a small downgrade, I was pretty disappointed. It was delightful that the keyboard would come up when you would open a new tab, I assumed this was a deliberate and very clever decision to save tablet users a tap.
(Reporter)

Comment 3

2 years ago
(In reply to Will from comment #1)
> Is there data that tells us what touchscreen users do when they open a new
> tab? I suspect by far the most common thing users do when they open a new
> tab is tap the URL so they can start typing.

I suspect the opposite. :-) Let's see if we have data so we can find out who's right!

I believe we have data about the new tab page and users' actions there. Ilana, what data do we have about what tiles people select on the new tab page, and how many people use that vs. how many use the URL or search bar vs. how many do something else (close the tab, quit Firefox, use a bookmark/history entry, something else...) ?
Flags: needinfo?(isegall)

Comment 4

2 years ago
We do have some preexisting data on interactions on the new tab page that was done for Content Services - https://docs.google.com/document/d/15EDEmTaiQ5txHSFf56FifryaqeiXE4RgIOxZ1vh4R1s/edit#heading=h.8zi4d3lns8o9

Flows are hard to capture with our current data packet (we don't look at the order in which actions were performed, we just have the aggregate number per session for the meantime though this may change), but we do have some very old data (3+ years) on this subject that I can dig out. Also, are we only interested in touchscreen users? I'm not sure how to discern those from other kinds of users (do we mean Android in this case, or touchscreen PC users? What does that look like in the data packet?).
Flags: needinfo?(isegall) → needinfo?(gijskruitbosch+bugs)
(Reporter)

Comment 5

2 years ago
(In reply to Ilana from comment #4)
> We do have some preexisting data on interactions on the new tab page that
> was done for Content Services -
> https://docs.google.com/document/d/
> 15EDEmTaiQ5txHSFf56FifryaqeiXE4RgIOxZ1vh4R1s/edit#heading=h.8zi4d3lns8o9
> 
> Flows are hard to capture with our current data packet (we don't look at the
> order in which actions were performed, we just have the aggregate number per
> session for the meantime though this may change), but we do have some very
> old data (3+ years) on this subject that I can dig out. Also, are we only
> interested in touchscreen users? I'm not sure how to discern those from
> other kinds of users (do we mean Android in this case, or touchscreen PC
> users? What does that look like in the data packet?).

touchscreen PC users. It seems we have FX_TOUCH_USED and TOUCH_ENABLED_DEVICE that keep track of this. Both seem to be specific to Windows already. Does that help?
Flags: needinfo?(gijskruitbosch+bugs) → needinfo?(isegall)

Comment 6

2 years ago
Maybe only really recent data should be looked at though because Firefox only started bringing up the on-screen keyboard in Windows in December 2015 (v43) and then turned it off for Windows 8/8.1 users the next release. But any touchscreen firefox data should be somewhat useful here. What do android users do when they open a new tab? 

As a side note, on the Moto E, when the keyboard is open in new tabs in Chrome, it doesn't cover any of the 8 suggest/top sites, it simply moves them up, so at least in Chrome's case there would be no downside at all in bringing up the on screen keyboard automatically when a user opens a new tab. For firefox, the keyboard covers the bottom 2 but the top 4 are uncovered. I feel strongly that users would love this, it's just removing that little bit of friction, maybe an experiment could be arranged for android aurora to get some feedback?

Comment 7

2 years ago
In that case, there's not a lot I can do to help, unfortunately, without additional instrumentation (to capture the ordering of events - something we have planned for the future but don't have right now). Is there interest in this?
Flags: needinfo?(isegall)
(Reporter)

Comment 8

2 years ago
(In reply to Ilana from comment #7)
> In that case, there's not a lot I can do to help, unfortunately, without
> additional instrumentation (to capture the ordering of events - something we
> have planned for the future but don't have right now). Is there interest in
> this?

What happens when users initially open a new tab seems like critical information to me in making that page more useful. Verdi/Dolske, is this something we would be interested in from a qx perspective, probably more broadly than limited to touch (though IMO we should take that into account - it seems likely that touch-capable machines will only become more common in the years to come).
Flags: needinfo?(mverdi)
Flags: needinfo?(dolske)
(Reporter)

Updated

2 years ago
Flags: needinfo?(jaws)

Comment 9

2 years ago
FWIW, it seems right now Firefox, Chrome and Edge all do basically the same thing (on my Surface Pro 3, Windows 10, no keyboard attached). That is, on a new tab they focus the address bar (search field in Edge's case) but don't bring up the keyboard until you tap in a text input field. Same goes for the search in page. The search field appears and is focused but you have to tap in it to bring up the keyboard. 

Like Gijs suggests, it makes sense to bring up the keyboard automatically for find in page though I think we'd have to move (finally) ours to the top of the page to make this work. Currently, the keyboard will obscure the find field until you detach it and move it up. 

As for the new tab page, my guess is automatically bringing up the keyboard is not the right interaction (i.e. we made the correct change). It would be good to have some data on tablet use though. It seems like a good portion of new Windows machines are capable of tablet mode (or at least touch screen and no keyboard) and I don't know if any of us has any idea how often Firefox users use Firefox in tablet mode.
Flags: needinfo?(mverdi)
(Reporter)

Comment 10

2 years ago
(In reply to Verdi [:verdi] from comment #9)
> As for the new tab page, my guess is automatically bringing up the keyboard
> is not the right interaction (i.e. we made the correct change). It would be
> good to have some data on tablet use though. It seems like a good portion of
> new Windows machines are capable of tablet mode (or at least touch screen
> and no keyboard) and I don't know if any of us has any idea how often
> Firefox users use Firefox in tablet mode.

We already have that data. The answer is: basically nobody.

https://telemetry.mozilla.org/new-pipeline/dist.html#!cumulative=0&end_date=2016-04-21&keys=tablet!desktop!__none__!__none__&max_channel_version=beta%252F46&measure=FX_TABLETMODE_PAGE_LOAD&min_channel_version=null&os=Windows_NT%252C10.0&product=Firefox&sanitize=1&sort_keys=submissions&start_date=2016-03-07&table=0&trim=1&use_submission_date=0

What we don't have is data about what people do with the new tab page...
(Reporter)

Comment 11

2 years ago
(In reply to :Gijs Kruitbosch from comment #10)
> (In reply to Verdi [:verdi] from comment #9)
> > As for the new tab page, my guess is automatically bringing up the keyboard
> > is not the right interaction (i.e. we made the correct change). It would be
> > good to have some data on tablet use though. It seems like a good portion of
> > new Windows machines are capable of tablet mode (or at least touch screen
> > and no keyboard) and I don't know if any of us has any idea how often
> > Firefox users use Firefox in tablet mode.
> 
> We already have that data. The answer is: basically nobody.
> 
> https://telemetry.mozilla.org/new-pipeline/dist.html#!
> cumulative=0&end_date=2016-04-21&keys=tablet!desktop!__none__!
> __none__&max_channel_version=beta%252F46&measure=FX_TABLETMODE_PAGE_LOAD&min_
> channel_version=null&os=Windows_NT%252C10.
> 0&product=Firefox&sanitize=1&sort_keys=submissions&start_date=2016-03-
> 07&table=0&trim=1&use_submission_date=0
> 
> What we don't have is data about what people do with the new tab page...

(Note that this is data about the actual Windows 10 "tablet mode" feature - people are of course free to use Windows 10 in "desktop mode" and use functionality using touch input.)
If we're consistent with Chrome and Edge, I don't think it's urgent to investigate this further right now.
Flags: needinfo?(dolske)

Comment 13

2 years ago
As of Chrome v51 stable on my SP4, the on-screen keyboard doesn't even come up when I tap the URL bar, so we really shouldn't base decisions off what Chrome is or isn't doing. And even Edge has surprising problems. For example, when you are typing in a search field or the URL bar and you hit Enter on the on-screen keyboard, it doesn't go down/close, it very annoyingly stays on the screen. Apple seems to be the only company getting on-screen keyboard behavior right (and trust me, it pains me to type that). So maybe we should just follow what Safari for the iPad does 

(In reply to Justin Dolske [:Dolske] from comment #12)
> If we're consistent with Chrome and Edge, I don't think it's urgent to
> investigate this further right now.

Comment 14

a year ago
Just thought I would give an update here: since updating to the 'anniversary update' on a surface pro 4, when using Edge (without the keyboard attached) the on-screen keyboard now opens automatically when I open a new tab and also for websites where the focus is in the search field (such as google.com) 

Also, in Firefox for android v49 beta, when I go to wikipedia.org, the on-screen keyboard opens automatically because the search field is focused by default. 

I don't know if there's any data yet but we should at least consider bringing up the on-screen keyboard automatically if a search field is focused or when people open a new tab. It's surprisingly helpful, it saves a lot of taps. It really feels like it should have been the behavior all along but I guess we have to wait for data. Maybe experiment with this in Test Pilot? (is there Test Pilot for android?)
Sorry I never replied to comment #0. I think we should match parity with Chrome here. If the tablet is in portrait mode the OSK shouldn't consume half of the screen, I can see that only happening in landscape mode.

What is the major destination of people opening a new tab? Is it search / location bar? Both of those should be above the fold. It's OK to me to make people scroll to get to the tiles if they're not typing first.
You need to log in before you can comment on or make changes to this bug.