Repository: vscode
Issue: Uncompliant emmet abbreviation expansion in css
Labels: bug,emmet,confirmation-pending

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Hello everyone,
The issue :

Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.75.1
- OS Version: Mac os 10.11.6 (os still supported by vscode for about one month)
- 64x bits
- This VSCode had 0 extension installed, settings.json was empty.

This behavior was also observed on a VSCode installation on Windows 11 with about 200 extensions and modified settings, and on VSCode insiders without extension and with default parameters.

Steps to Reproduce:

1. Create a new blank css file containing the code below, remove the comment and place the cursor instead :
    ```css
    div {
        /*Place your cursor here*/
    }
    ```

2. Type the five caracters  **jc:sa**  , check that the proposed completion indicates "Emmet Abbreviation", and expand it with either enter or tab.
3. Expected behavior : "jc:sa" expands to "justify-content: space-around;".
4. Actual behavior : "jc:sa" expands to "justify-content: start;" instead.

Reference implementation to compare with the correct behavior : https://docs.emmet.io/css-abbreviations/fuzzy-search/
Cheat sheet that documents css abbreviations, including this particular one : https://docs.emmet.io/cheat-sheet/

I tested on https://codepen.io/pen/, and the behavior was unfortunately the same than in vscode, so the problem could be upstream.

Thank you for your time even if no solution comes up !

<details>
<summary>A/B Infos for the first mentionned vscode installation :</summary>
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256859
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593:30376534
pythonvs932:30410667
cppdebug:30492333
vsclangdc:30486549
c4g48928:30535728
dsvsc012cf:30540253
azure-dev_surveyone:30548225
pyindex848:30662994
nodejswelcome1:30587005
3biah626:30602489
pyind779:30662992
f6dab269:30613381
pythonsymbol12:30657548
vsctsb:30662444
</details>