Thanks for filling the issue...

Tested this issue on reported chrome version 67.0.3396.99 using Windows 10. Attaching screen-cast for reference.
Steps: 
---------
1. Launched reported chrome and 
2. Navigated to given URL " https://nodejs.org/en/docs/guides/event-loop-timers-and-nexttick/ " and opened search by hitting ctrl+F
3. Opened Dev tools>> Console >> Enabled and Disabled "scroll-behavior: smooth"  
4. Entered text "queue" 
As we are observed that focus navigating normally. 

@Reporter: Could you please review the attached screen-cast and confirm if anything being missed here.
Could you please upgrade to latest chrome 68.0.3440.75, you can download latest chrome builds here: "https://www.chromium.org/getting-involved/dev-channel".let us know if issue still persists or not.

Thanks..!

Deleted: 866694.mp4 17.0 MB

866694.mp4 17.0 MB Download

Hi @phanindra,

Thanks for checking this. Yes, I have reviewed your screencast and it's exactly the behavior I originally reported. I updated Chrome to v68.0.3440.75 and unfortunately, the behavior still persists. I've attached a screencast below.

Deleted: 2018-07-27_21-10-01.mp4 3.9 MB

	2018-07-27_21-10-01.mp4 3.9 MB View Download

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

As per Comment #3 retested this issue and as we are unable to reproduce the issue on reported chrome version 68.0.3440.75 using Windows 10. 
Followed the steps in comment #2, As we are observed that focus navigating normally and not jumping like comment #3

@Reporter: Request you to retry this issue with fresh profile without any extensions/apps or reset all the flags and let us know if issue still persists.

Thanks..!

@phanindra

I have tested this once again on v68.0.3440.75. I went to chrome://flags and reset everything to default, relaunched the browser. Instead of creating a new profile, I opened in "Guest" mode since no extensions/app are interfering there. I went to the site I mentioned in Comment #1 where the CSS rule was present and did the exact same things mentioned in the comment. I'm observing the same scroll animation (instead of jumps) when using Ctrl+F.

I also have Canary installed at v70.0.3507.0. I opened a "Guest" window there and did the same steps and it's the same behavior there too. The procedure I've did for doing both of these is recorded and posted here already so I don't think any more clarification is necessary.

And yes, removing the CSS rule brings back the jump to search matches when using Ctrl+F on both stable/canary.

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Unable to reproduce on chrome version #68.0.3440.106 and latest chrome version #71.0.3541.0 on Windows 10 by following steps in comment#0. As per comment#2 and comment#5, the issue is not reproducible on TE end, hence adding TE-NeedsTriageHelp label. Requesting anyone from Blink>Scroll team to look into the issue.

Attached screencast for reference.
Thanks.!

Deleted: 866694.mp4 15.4 MB

866694.mp4 15.4 MB Download

I noticed this issue as well. Tested with version 68.0.3440.106 (Official Build) (64-bit) on macOS 10.13.6.

As OP mentioned, removing the CSS rule fixes this behavior. This is not an issue in the latest of Firefox.

Deleted: Screen Recording 2018-09-04 at 11.01 AM.mov 8.5 MB

	Screen Recording 2018-09-04 at 11.01 AM.mov 8.5 MB View Download

`scroll-behavior: smooth` should make search jump animating. I think what sangeethmanayil@ wants is to not animate when the distance is too long. Right?

@chaopeng, yes, you're right. Like I mentioned, Firefox doesn't respect this value for searches and I believe that'd be the right thing to do. Search should be immediate and the animating is just adding unnecessary delay in producing the desired results.