Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Emmet Expansion looses against completion proposals #19234

Closed
chrmarti opened this issue Jan 24, 2017 · 3 comments
Closed

Emmet Expansion looses against completion proposals #19234

chrmarti opened this issue Jan 24, 2017 · 3 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s) emmet Emmet related issues

Comments

@chrmarti
Copy link
Contributor

chrmarti commented Jan 24, 2017

Test item #19079

  • VSCode Version: Code - Insiders 1.9.0-insider (4265f5e, 2017-01-24T10:29:13.076Z)
  • OS Version: Darwin x64 15.6.0
  • Extensions:
Extension Author Version
autofilename JerryHong 0.1.3

Steps to Reproduce:

  1. Install AutoFileName extension
  2. Open empty html file
  3. Type: html<tab>
  4. Unexpected: the completion proposals from AutoFileName win against the Emmet Expansion command

Not sure if this is specific to how this extension sets up it completion items, but maybe we can improve that on our side.

@chrmarti chrmarti added the emmet Emmet related issues label Jan 24, 2017
@chrmarti chrmarti changed the title Emmet Expansion looses against AutoFileName Emmet Expansion looses against completion proposals Jan 24, 2017
@chrmarti
Copy link
Contributor Author

Also with other proposals:

  1. Start with an empty html
  2. Type: hr<tab>
  3. Ok
  4. Again type: hr<tab>
  5. Expected: Expansion to <hr>
  6. Actual: <tab> only accepts completion proposal, I have to hit <tab> a second time to get the expansion to <hr>

@chrmarti
Copy link
Contributor Author

Not an Emmet power user, but this seems to make it hard to use.

@ramya-rao-a
Copy link
Contributor

Duplicate of #1952

@ramya-rao-a ramya-rao-a added the *duplicate Issue identified as a duplicate of another issue(s) label Feb 1, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s) emmet Emmet related issues
Projects
None yet
Development

No branches or pull requests

2 participants