Skip to content
This repository has been archived by the owner on Dec 11, 2019. It is now read-only.

Find in page doesn't work correctly after navigation if 0 results #6147

Closed
bbondy opened this issue Dec 12, 2016 · 5 comments
Closed

Find in page doesn't work correctly after navigation if 0 results #6147

bbondy opened this issue Dec 12, 2016 · 5 comments

Comments

@bbondy
Copy link
Member

bbondy commented Dec 12, 2016

This works in 0.12.14
This fails in 0.13.0

Run this test:

npm run test -- --grep="findbar input remembered"

It fails for a legit reason. You can reproduce as follows manually:

Start an http server in the browser-laptop test dir

  1. cd test/fixtures
  2. python -m SimpleHTTPServer 9099
  3. Load http://localhost:9099/find_in_page.html
  4. Open find bar and type Brad
  5. Load http://localhost:9099/find_in_page2.html
  6. Open find bar and press enter

It doesn’t find the match

It should find the match

@bbondy bbondy added this to the 0.13.0 milestone Dec 12, 2016
@cndouglas
Copy link

I think I can reproduce this issue on both 0.12.14 and master. The only change (in 0.13.0) I can think of is my PR #5786 (commit 29e7d53) that changed the findbar's onKeyUp to onInput.

@cezaraugusto
Copy link
Contributor

@liunkae your commit isn't added yet on the latest release (v0.13.0dev-Preview2). See here.

@bbondy
Copy link
Member Author

bbondy commented Dec 12, 2016

I confirmed it wasn't because of your change @liunkae by the way by reverting it and testing.

@bbondy bbondy self-assigned this Dec 13, 2016
@bbondy bbondy changed the title Find in page doesn't work correctly after navigation Find in page doesn't work correctly after navigation if 0 results Dec 13, 2016
@bbondy bbondy modified the milestones: 0.13.1, 0.13.0 Dec 19, 2016
@bbondy bbondy removed their assignment Dec 19, 2016
@bbondy bbondy removed the chromium54 label Dec 26, 2016
@bbondy
Copy link
Member Author

bbondy commented Dec 26, 2016

I think I tested wrong before this seems to have always been a problem, or at least for the last couple releases.

@bbondy bbondy removed this from the 0.13.1 milestone Dec 26, 2016
@bbondy bbondy mentioned this issue Dec 26, 2016
21 tasks
@bbondy
Copy link
Member Author

bbondy commented Dec 26, 2016

Disabling the test for now #5389

bbondy added a commit that referenced this issue Dec 26, 2016
Issue #6147 tracks the issue but it's been open for a while and isn't a new issue with 0.13
@luixxiul luixxiul added this to the 0.15.400 milestone May 15, 2017
@alexwykoff alexwykoff removed this from the 0.16.100 milestone May 23, 2017
@bsclifton bsclifton added this to the Triage Backlog milestone Nov 27, 2017
@bsclifton bsclifton removed this from the Triage Backlog milestone Oct 19, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants