Closed Bug 1279707 Opened 4 years ago Closed 4 years ago
the highlight will be accumulated and accumulated
Steps To Reproduce: 1. Open a page (e.g. https://developer.mozilla.org/en-US/Add-ons/Code_snippets/Tabbed_browser ) 2. Ctrl+F to open FindBar and input word ("browser") and hit ENTER 3. Click a link (e.g. "load listener" ) 4. Select textfield of Findbar and Hit ENTER Actual Results: the new Find highlight is wrong
[Tracking Requested - why for this release]: Regression
Bulk update to find bar bugs that won't be in 50 (according to https://bugzilla.mozilla.org/show_bug.cgi?id=1279695#c4 and local testing).
This should be working as expected now. If not, please re-open this bug. Thanks!
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Verified this on Nightly 51.0a1, build ID:20160914030200, on Windows 10 x64 and Windows 7 x64 and I could not reproduce it with the term searched in the Description of the bug, but the issue is reproducible when searching for " to". Reopening the bug.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee: nobody → mdeboer
Status: REOPENED → ASSIGNED
Comment on attachment 8791627 [details] Bug 1279707 - when the location changes, we need to be more thorough in clearing the state variables than we are now to make sure we start fresh in new documents. https://reviewboard.mozilla.org/r/79006/#review77618
Attachment #8791627 - Flags: review?(jaws) → review+
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/autoland/rev/f7acbdb1d9a6 when the location changes, we need to be more thorough in clearing the state variables than we are now to make sure we start fresh in new documents. r=jaws
Verified as fixed (using the steps from the description) using the latest Nightly 52.0a1 Build ID:20160928030201 on Windows 10 X64 and Ubuntu 14.04. I can still see some blank empty spaces if searching for "to" but that should be covered in bug 1302470. Considering the above, setting the status to verified fixed.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.