Closed Bug 1554761 Opened 5 years ago Closed 5 years ago

Find in page value reappearing

Categories

(Toolkit :: Find Toolbar, defect, P2)

66 Branch
defect
Points:
3

Tracking

()

VERIFIED FIXED
mozilla72
Iteration:
71.2 - Sept 16 - 29
Tracking Status
firefox72 --- fixed
firefox74 --- verified

People

(Reporter: u635235, Assigned: mikedeboer)

References

(Blocks 1 open bug)

Details

Attachments

(4 files, 3 obsolete files)

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:66.0) Gecko/20100101 Firefox/66.0

Steps to reproduce:

  1. Open the find in page bar by pressing Cmd + F
  2. Type some text in
  3. Close the find in page bar
  4. Re-open the find in page bar
  5. Delete all text in the find in page bar
  6. Click outside the find in page bar
  7. Click in the find in page bar input field

Actual results:

At step 4 the text is often shorter than the text entered in step 2, if it is say eight characters long it will end up being 3-4.

At step 7 the find in page bar input field will contain the text deleted in step 5.

Expected results:

At step 4 the text should be exactly the same as it was when the find in page bar was closed in step 3.

At step 7 the find in page bar input field should be blank, having been deleted in step 5.

Component: Untriaged → Find Toolbar
Product: Firefox → Toolkit

The priority flag is not set for this bug.
:mikedeboer, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(mdeboer)

I can reproduce this behavior, but I'm not sure if it's critical issue.
This is a problem with the interaction between the find toolbar and the OSX system-wide Find clipboard. What I see in other Mac apps is that indeed each typed sequence of characters is saved to the Find clipboard, not just the successful finds.
I'll take a look at this, see how much I can fix this up.

Thanks for filing!

Assignee: nobody → mdeboer
Status: UNCONFIRMED → ASSIGNED
Iteration: --- → 69.4 - Jun 24 - Jul 7
Points: --- → 3
Ever confirmed: true
Flags: needinfo?(mdeboer)
Priority: -- → P2
Attachment #9079282 - Attachment description: Bug 1554761 - Small refactor, made possible because the findbar is now a custom element, implemented as a JS module. r?Gijs! → Bug 1554761 - Small refactor, made possible because the findbar is now a custom element, implemented as a JS module. r?dao!
Attachment #9079283 - Attachment description: Bug 1554761 - Align findbar interaction with the Mac OSX find clipboard to match common behavior of system apps. r?Gijs! → Bug 1554761 - Align findbar interaction with the Mac OSX find clipboard to match common behavior of system apps. r?dao!
Attachment #9079284 - Attachment description: Bug 1554761 - Add test coverage for the newly introduced BrowserWindowTracker observer API. r?Gijs! → Bug 1554761 - Add test coverage for the newly introduced BrowserWindowTracker observer notification. r?dao!
Attachment #9079284 - Attachment is obsolete: true
Attachment #9080681 - Attachment is obsolete: true

Zibi, setting the needinfo flag in order to continue the conversation in Phabricator.

Flags: needinfo?(gandalf)
Iteration: 69.4 - Jun 24 - Jul 7 → 71.2 - Sept 16 - 29
Attachment #9079282 - Attachment description: Bug 1554761 - Small refactor, made possible because the findbar is now a custom element, implemented as a JS module. r?dao! → Bug 1554761 - Small refactor, made possible because the findbar is now a custom element, implemented as a JS module. r?Gijs!
Attachment #9081748 - Attachment description: Bug 1554761 - Notify with an 'app_activate' topic when the App has been activated, capturing Command-Tabbing behavior. OSX only. r?spohl! → Bug 1554761 - Notify with a 'mac_app_activate' topic when the App has been activated, capturing Command-Tabbing behavior. OSX only. r?spohl!
Attachment #9080680 - Attachment is obsolete: true
Attachment #9079284 - Attachment is obsolete: false
Attachment #9079284 - Attachment is obsolete: true
Pushed by mdeboer@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/df0d308f3d6d
Small refactor, made possible because the findbar is now a custom element, implemented as a JS module. r=Gijs
Flags: needinfo?(gandalf)
Pushed by mdeboer@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/2581a2452450
Small refactor, made possible because the findbar is now a custom element, implemented as a JS module. r=Gijs
https://hg.mozilla.org/integration/autoland/rev/9f0da81292cc
Align findbar interaction with the Mac OSX find clipboard to match common behavior of system apps. r=Gijs
https://hg.mozilla.org/integration/autoland/rev/48b38cc561d4
Notify with a 'mac_app_activate' topic when the App has been activated, capturing Command-Tabbing behavior. OSX only. r=spohl
Blocks: 1593989
Attachment #9106524 - Attachment description: Bug 1554761 - Follow-up to add a missing module import/ constant that I missed in Part 1. r?Gijs! → Bug 1554761 - Follow-up to add a module import/ constant that I accidentally removed in Part 2. r?Gijs!
Pushed by mdeboer@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/60fdca0bdbef
Follow-up to add a module import/ constant that I accidentally removed in Part 2. r=Gijs
Flags: qe-verify+

I managed to reproduce the issue on an older version of Nightly from 2019-05-27 using macOS 10.15.
However, when I open the latest Nightly 74.0a1 with a new profile, the Find Toolbar still contained a few of the letters from the word I input in the field in the affected build.
After I redid the steps on Nightly 74.0a1, the bug didn't reproduce.
Is this normal behaviour?

Flags: needinfo?(mdeboer)

Yes.

Flags: needinfo?(mdeboer)

According to comment 17 and comment 18 I will mark this bug as verified fixed.

Status: RESOLVED → VERIFIED
Flags: qe-verify+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: