find in page showing incorrect results after returning to the original web page

NEW
Unassigned

Status

()

Firefox for Android
General
a year ago
7 months ago

People

(Reporter: kr1shna, Unassigned)

Tracking

53 Branch
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

(Reporter)

Description

a year ago
Created attachment 8843269 [details]
my 1st find in page

User Agent: Mozilla/5.0 (Android 5.1; Mobile; rv:53.0) Gecko/53.0 Firefox/53.0
Build ID: 20170212084044

Steps to reproduce:

i am on Fennec 53.0a2 Build ID: 20170212084044. ls-4001/android 5.1.

What did you do? (steps to reproduce)

this is tab 1:
visit https://bugs.documentfoundation.org/buglist.cgi?cmdtype=runnamed&namedcmd=filters%3Astorage

find in page 
5.4.0 [ my preference] [ see attachment] [ 14 results ]

this is tab 2:
open in new tab a bug link from tab 1

i did not close find in page on tab 1


Actual results:

i close my previously opened bug tab [ tab 2 ]

i return to tab 1

the find in page at bottom of page has disappeared on tab 1

i again try find in page & it shows only one result [ see attachment ]

i close tab 2 showing one result

if i again load the link provided above
find in page
5.4.0 [ my preference]
it shows correct result [ 14 results ]


Expected results:

when i close tab 2 & return to tab 1:

the find in page results should not be 1 but 14 on tab 1.
(Reporter)

Comment 1

a year ago
Created attachment 8843270 [details]
my 2nd find in page,  find in page box disappeared, reload or reopen of tab 1
Hello and thanks for report!

Tested with two devices with android 5.1 (Huawei MediaPad M2 and Huawei Honor) following your steps and I cannot reproduce. 

I was able to reproduce the issue if I close the tab 2 from device back button or if I go to tab tray -> close tab 2. Following this scenario find-in-page was not displayed for tab 1. And searching again displayed the right results.
Status: UNCONFIRMED → NEW
Ever confirmed: true
You need to log in before you can comment on or make changes to this bug.