Even if I hit escape to dismiss intellisense, then hit tab, emmet expansion doesn't kick in.

Also I should always be able to type a html tag, or user defined react, angular tag, like "<from" hit tab and emmet should know what to do when fail on a keyword!

Where is this from keyword coming from? I can't get a repro. If I can repro this, I can look into why the from is sorted higher compared to form.

You can also add the below 2 settings to ensure emmet suggestions always appear on top

 "emmet.showSuggestionsAsSnippets": true,
    "editor.snippetSuggestions": "top"

Even if I hit escape to dismiss intellisense, then hit tab, emmet expansion doesn't kick in.

Emmet expansion on tab in the absence of intellisense occurs only if you have added the setting "emmet.triggerExpansionOnTab": true

No idea where from is coming from and why?
Try creating a simple react.js app, then create a new component file with a .jsx extension to enable emmet for this file. If you're not sure how to do this, just ask me to create a simple project you can fetch from github.

Also thanks for the setting suggestions, I added, "emmet.triggerExpansionOnTab": true but don't want to use the other for now.

FYI: I did try all 3 settings you suggested and still from get selected even though it's not the top item.

Please share a sample project where I can try and get a repro.

Also, try running code --disable-extensions and see if you still see the from. That will tell us if the suggestion is coming from one of your installed extensions

Using --disable-extensions still shows the bug for me, as well as "from".

1. Please make sure you remove those 3 vscode settings you shared earlier when investigating.
2. Here is the demo app: https://github.com/rajinder-yadav/demo_app
3. Open file src/containers/user-form.jsx, inside the render function, type, "form", you should see the bug. GL :)

Thanks for the sample code @rajinder-yadav, I can repro it now.
My mistake, I was trying to repro in stable, whereas this issue only appears in Insiders
The root cause is the we recently implemented a feature request #15419 that accommodate typos.

@jrieken Here is a case where relaxing for typos is counter productive. In this case both form and from get the same score. Shouldnt the non typo match be scored higher than the one for the typo?

Repro steps: Using Insiders, type form in any jsx file. from is preselected instead of form

Linking this to #39550

I see... I will penalize permutation matches which should make this better. Still, it is fuzzy by its nature