Closed
Bug 958666
Opened 12 years ago
Closed 12 years ago
Autofocus is delayed until first user interaction on fxos
Categories
(Firefox OS Graveyard :: Gaia::Browser, defect)
Tracking
(blocking-b2g:1.3+, firefox27 wontfix, firefox28 fixed, firefox29 fixed, b2g18 unaffected, b2g-v1.1hd unaffected, b2g-v1.2 wontfix, b2g-v1.3 fixed, b2g-v1.4 fixed)
Tracking | Status | |
---|---|---|
firefox27 | --- | wontfix |
firefox28 | --- | fixed |
firefox29 | --- | fixed |
b2g18 | --- | unaffected |
b2g-v1.1hd | --- | unaffected |
b2g-v1.2 | --- | wontfix |
b2g-v1.3 | --- | fixed |
b2g-v1.4 | --- | fixed |
People
(Reporter: rkuhlman, Assigned: daleharvey)
Details
(Keywords: regression, Whiteboard: dogfood1.3, [systemsfe] [perf-reviewed])
Attachments
(3 files, 3 obsolete files)
Mobile sites that feature radio buttons or search bars can perform strangely. The bar or button will get selected even if the user has not tapped in the hitbox to select them. When this happens, the page will auto scroll to place the button or bar into the viewing area. In some situations, the page will repeatedly scroll to the radio button, making it effectively impossible to view the rest of the page. This issue has been observed repeatedly with the search bar on the front page of wikipedia.org, and occasionally on amazon pages that contain radio buttons.
Repro Steps:
1) Updated Buri to BuildID: 20140106004001
2) Launch Browser app.
3) Navigate to www.wikipedia.org.
4) Attempt to scroll to the bottom of the page.
Actual:
Cursor is placed in the search bar, the keyboard appears onscreen, and Browser auto-scrolls to the very top of the page.
Expected:
Search bar is not highlighted unless user taps directly on search bar. Browser does not repeatedly auto-scroll user.
Environmental Variables:
Device: Buri v1.3 Moz RIL
BuildID: 20140106004001
Gaia: 35a60b82f8cf2d759939a350e2dadbb9d8b2f5dc
Gecko: a43cb4b322d3
Version: 28.0a2
RIL Version: 01.02.00.019.102
Firmware Version: Settings > Device Information > More Information > Firmware revision (example.D30008m)
Notes:
Repro frequency: 100% on wikipedia.org, ~70% on amazon.com
See attached: logcats.
Reporter | ||
Comment 1•12 years ago
|
||
I have also attached a logcat of radio buttons acting strangely at amazon.com
This issue appears to occur in Buri 1.2 COM RIL.
Environmental Variables
Device: Buri v 1.2.0 COM RIL
Build ID: 20140121004053
Gecko: http://hg.mozilla.org/releases/mozilla-b2g26_v1_2/rev/c9f305c1d9a7
Gaia: 539a25e1887b902b8b25038c547048e691bd97f6
Platform Version: 26.0
RIL Version: 01.02.00.019.102
Firmware Version: V1.2-device.cfg
status-b2g-v1.2:
--- → affected
Does not appear to occur in Buri 1.1 COM RIL.
Environmental Variables
Device: Buri v 1.1.0 COM RIL
Build ID: 20140121041200
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/e7a8e7b9b7d2
Gaia: 6ff3a607f873320d00cb036fa76117f6fadd010f
Platform Version: 18.1
RIL Version: 01.01.00.019.281
Firmware Version: V1.2-device.cfg
status-b2g18:
--- → unaffected
Updated•12 years ago
|
Keywords: regression
Comment 5•12 years ago
|
||
Strange regression, but I can reproduce it & it's annoying. This forces interaction with a HTML input element that a user hasn't requested to interact with, which heavily slows down the user from what he/she is intending to do.
blocking-b2g: --- → 1.3?
Comment 6•12 years ago
|
||
Gregor,
Please reassign
blocking-b2g: 1.3? → 1.3+
Flags: needinfo?(anygregor)
Comment 7•12 years ago
|
||
Can we get a regression range?
Flags: needinfo?(anygregor)
Keywords: regressionwindow-wanted
Updated•12 years ago
|
Whiteboard: dogfood1.3 → dogfood1.3, [systemsfe]
Comment 8•12 years ago
|
||
This issue reproduces all the way back to the first Buri 1.2 Build ID: 20130621031231
Gaia e2f19420fa6a26c4287588701efaec09a750dba1
SourceStamp 7ba8c86f1a56
BuildID 20130621031231
Version 24.0a1
Keywords: regressionwindow-wanted
Comment 10•12 years ago
|
||
(In reply to Gregor Wagner [:gwagner] from comment #9)
> So this is not a regression?
It's still a regression. The above regression range implies this regressed during the timeframe when we didn't have 1.2 builds. However, this doesn't reproduce on 1.1.
Flags: needinfo?(jsmith)
Comment 11•12 years ago
|
||
Dale, can you take a look please?
Assignee: nobody → dale
Flags: needinfo?(dale)
Assignee | ||
Comment 13•12 years ago
|
||
So at least in the case of wikipedia, this is because we for some reason only autofocus when the user starts interacting with the page, this means a user scrolls down then suddenly the autofocus grabs the page and scroll gets triggered)
There are a few bugs relating to autofocus being problematic on mobile, given the lack of screen space it seems like we should just disable it.
I feel like the current behaviour might be an intentional workaround for not hiding the page on first load as it behaves consistently and would seem hard to do by accident
Assignee | ||
Comment 14•12 years ago
|
||
I cant find anything in the log to suggest this is on purpose, taking a look at gecko to see what could be causing it, may be tricky though |prefs.push(['browser.autofocus', false])| fixes it though, I think it should be given serious thought, any site that autofocus's on load is essentially invisible on fxos, it seems like the semantics are very different on mobile (where its easy to tap the input)
Will take a look at the radio buttons thing to see if thats a seperate bug
Assignee | ||
Comment 15•12 years ago
|
||
There isnt a radio button on amazon.com
Assignee | ||
Comment 16•12 years ago
|
||
The same delayed autofocus behaviour applies to radio buttons though, so will assume that was the reported problem
Assignee | ||
Updated•12 years ago
|
Summary: [B2G][Browser][Mobile sites]Browser occasionally auto-highlights and snaps to a search bar or radio button on the site. → Autofocus is delayed until first user interaction on fxos
Updated•12 years ago
|
Whiteboard: dogfood1.3, [systemsfe] → dogfood1.3, [systemsfe] [perf-reviewed]
Assignee | ||
Comment 17•12 years ago
|
||
This disables autofocus on b2g, the majority of the large sites will disable the autofocus themselves when they service mobile content, it still happens on sites, primarily responsive / desktop ones
Attachment #8367579 -
Flags: ui-review?(jcarpenter)
Attachment #8367579 -
Flags: review?(21)
Comment 18•12 years ago
|
||
Comment on attachment 8367579 [details] [review]
Disable autofocus on b2g
Please add the pref to b2g/app/b2g.js with a bug number to turn it back on with the right behavior (followup bug that needs to be filed).
Attachment #8367579 -
Flags: review?(21)
Assignee | ||
Comment 19•12 years ago
|
||
Attachment #8367579 -
Attachment is obsolete: true
Attachment #8367579 -
Flags: ui-review?(jcarpenter)
Attachment #8367884 -
Flags: review?(21)
Attachment #8367884 -
Flags: review?(21) → review+
Assignee | ||
Comment 20•12 years ago
|
||
Comment 21•12 years ago
|
||
Assignee | ||
Comment 22•12 years ago
|
||
Ugh sorry, disabling the autofocus test on B2G, carrying r+, pushing to try to make sure
https://tbpl.mozilla.org/?tree=Try&rev=3f4c5278d9d3
Attachment #8367884 -
Attachment is obsolete: true
Attachment #8368038 -
Flags: review+
Assignee | ||
Comment 23•12 years ago
|
||
Fixed reftest mistake, carrying r+, got a green try push https://tbpl.mozilla.org/?tree=Try&rev=869e743bb02d
https://hg.mozilla.org/integration/b2g-inbound/rev/e76b333631e0
Attachment #8368384 -
Flags: review+
Assignee | ||
Updated•12 years ago
|
Attachment #8368038 -
Attachment is obsolete: true
Assignee | ||
Updated•12 years ago
|
Target Milestone: --- → 1.3 C3/1.4 S3(31jan)
Comment 24•12 years ago
|
||
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Comment 25•12 years ago
|
||
status-b2g-v1.1hd:
--- → unaffected
status-b2g-v1.3:
--- → fixed
status-b2g-v1.4:
--- → fixed
status-firefox27:
--- → wontfix
status-firefox28:
--- → fixed
status-firefox29:
--- → fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•