Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Autocomplete for basic events not implemented properly

See original GitHub issue

I’m submitting a bug report

Extension Version: 0.1.7

Please tell us about your environment:

Operating System: Windows 10
Visual studio code version: 1.7.0-insiders

Screenshot of incorrect highlight

HTML/JS/TS of incorrect highlight Basically unexpected event binding option

Current behavior:

Expected/desired behavior:

What is the expected behavior? Expect all basic events:
- Mouse: click mousedown mouseup mouseover mouseout mouseenter mouseleave mousemove
- Drag: dragstart dragend drag dragover dragenter dragleave drop
- Focus: blur focus
- Keyboard: keydown keypress keyup
- Form: change input submit
- Touch: touchstart touchmove touchend
- Scroll: wheel scroll

Will have delegate and trigger options only.

NOTE: Not bubbling events such as blur, focus, mouseenter, mouseout, scroll should be shown with trigger only
What is the motivation / use case for changing the behavior? Make Aurelia great

Issue Analytics

State:
Created 7 years ago
Comments:6 (6 by maintainers)

Top GitHub Comments

1reaction

erikliebencommented, Oct 22, 2016

The old autocomplete stopped working for some unknown reason in version 1.6.0 of vscode. It simply didn’t add the auto-complete suggestions anymore. Bit of bad timing for me, but I am happy it is resolved now 😃

I was already looking at re-writing it to a separate service/ process, so it would not interfering with the UI rendering and makes space for doing more processor intensive work during the autocompletion.

The current implementation is very similar to how the default HTML autocomplete/ suggest works and was the fastest way to get it working again. This can be seen as a basic version, will probably grow/ become smarter over time. The current implementation allows us to move towards auto-complete based on the Aurelia plugins you have loaded or components you have created, etc.

I think that in the future the ‘old way’ of autocomplete value.[options] will probably return or some variant of it.

I can add a configuration options for double or single quotes (#13), so it will complete according to your preference.

Thanks for the feedback/ bug report

1reaction

erikliebencommented, Oct 22, 2016

Version 0.1.8 is published and contains a fix for this. I am sorry for the inconvenience, should have tested it better myself.

Top Results From Across the Web

AutoComplete not working correctly in Outlook 2010

If it's already turned on, your first troubleshooting step should be to clear out the Auto-Complete list. Select the Empty AutoComplete List ...

autocomplete events does not trigger | Support Center

After enter a value from autocomplete field, the user moving of cursor to the second input ... Events not triggering properly in drop...

HTML attribute: autocomplete - MDN Web Docs

The HTML autocomplete attribute lets web developers specify what if any permission the user agent has to provide automated assistance in filling out...

Autofill does not trigger onChange

If you disable basic functionality, you also have to check for enabling it on startup. So put the 'if email.length' check somewhere After...

Code completion not working in 10.2

Only solution that seems to work is to move the current file into the main folder from any of the sub-folders. Auto code...