Closed Bug 1478614 Opened 6 years ago Closed 6 years ago

Scrolling to the bottom of a page with a fixed header, so that the UI bar reappears, breaks touch position.

Categories

(Firefox for Android Graveyard :: General, defect, P2)

defect

Tracking

(firefox-esr52 unaffected, firefox-esr60 unaffected, firefox61 unaffected, firefox62 unaffected, firefox63- wontfix)

RESOLVED WORKSFORME
Tracking Status
firefox-esr52 --- unaffected
firefox-esr60 --- unaffected
firefox61 --- unaffected
firefox62 --- unaffected
firefox63 - wontfix

People

(Reporter: Kwan, Unassigned)

References

Details

(Keywords: regression, Whiteboard: [priority:medium])

Attachments

(1 file)

Attached file Testcase
First seen on https://mozilla.logbot.info Somewhat simplified testcase attached and at http://kwan.perix.co.uk/mozilla/touchPosTest.html STR: 1) Open affected page 2) Scroll down until the UI autohides 3) Keep scrolling until reaching the bottom and the UI autoshows 4) Try touching on page, especially the two sets of letters AR: Client position (blue circle) of the click event is wrong Clicking on the letters on the left (in a fixed position element) Firefox targets/highlights those under the incorrect client (blue) position, which will be the letter below the clicked on one Clicking on the letters on the right it correctly targets under the page (red) position ER: Client and page position match Clicking on letters highlights the clicked on one [Tracking Requested - why for this release]: Poor & confusing user experience on some mobile pages if user scrolls to the page end and tries to click on any fixed-position elements.
This seems to have been a regression from bug 1423011. It's also possible bug 1465616 is meant to fix this, and this'll end up duped there.
Closing per https://bugzilla.mozilla.org/show_bug.cgi?id=1473195 Contact :susheel if you think this bug should be re-opened
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → INACTIVE
:susheel is ambiguous, bringing up no results with that IRC nick on bugzilla (and no-one in either #bmo or #mobile), and 5 people who include that in their name, none of whom have an official looking address. Fresh user-impacting regressions don't seem like a good candidate for resolving, reopening.
Status: RESOLVED → REOPENED
Ever confirmed: true
Resolution: INACTIVE → ---
Reopened. Can we find an owner for this?
Flags: needinfo?(sdaswani)
Andreas, should I have the Softvision dev team take a look at this? Ian, I think Emma made a small error in her closing message - I'm :sdaswani :) . One point of Emma's mass closing was to get live issues prioritized by messages like yours.
Flags: needinfo?(sdaswani) → needinfo?(abovens)
I cannot reproduce the touch issue in GeckoView, only in Fennec (from time to time). However, I do notice that the right column of letters is positioned differently in Chrome: the "a" is shown inside the light blue area, whereas in Firefox it stops just below it. It would be good to get this investigated.
Flags: needinfo?(abovens)
Looks like abovens could reproduce; whether we want QA to take a stab at it also is up to you. Either way, we need an owner for this.
Flags: needinfo?(sdaswani)
Flags: needinfo?(sdaswani)
Priority: -- → P2
Whiteboard: [priority:medium]
kashav, is bug 1465616 going to fix this?
Flags: needinfo?(kmadan)
(In reply to :sdaswani only needinfo from comment #5) > Andreas, should I have the Softvision dev team take a look at this? > > Ian, I think Emma made a small error in her closing message - I'm :sdaswani > :) . One point of Emma's mass closing was to get live issues prioritized by > messages like yours. No problem :) I was trying to ask first about reopening, but defaulted to doing so on failure to find contact. (In reply to Andreas Bovens [:abovens] from comment #6) > I cannot reproduce the touch issue in GeckoView, only in Fennec (from time > to time). What does GeckoView mean in this context? Is there a Fx4A build with it? Or were you using Fenix or FocusGV? If so Fenix doesn't hide its UI, and Focus doesn't auto-unhide UI on reaching the bottom of the page, so neither would be able to trigger the issue.
(In reply to Ian Moody [:Kwan] (UTC+0) from comment #8) > kashav, is bug 1465616 going to fix this? It fixes it, but I'm not entirely sure why just yet (going to look into it more, will comment here with what I find). I did find a regression caused by bug 1465616 with your testcase, so thanks for that! It's related to fixed position elements disappearing when the dynamic toolbar reappears at the bottom of the page - I'll file a bug for this.
Flags: needinfo?(kmadan)
Based on comment 10 I will close this issue as WFM, thanks.
Status: REOPENED → RESOLVED
Closed: 6 years ago6 years ago
Resolution: --- → WORKSFORME
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: