brunnerh

That would be quite useful, but the extension has to rely on the available mechanisms. In this case a "quick-pick" which currently [has no option for that](https://code.visualstudio.com/api/references/vscode-api#QuickPickOptions).

That is unfortunately not how the API works. The dropdown list is a unit and automatically filteres upon input with no way to change its logic apart from modifying where...

That appears to use some internals that are not exposed in the public API available to extensions. There are already various issues open in the VS repository for functionality that...

This seems like a font issue; characters display for me (just very small):  These fonts are part of the window UI and cannot be changed via the settings. They...

That is not a solution. It can lead to even more broken results if the browser does not have a way of combining those symbols: 

I would suggest keeping it as is due to the mentioned ergonomics. If a component can validly be used without the given context, the `undefined` can still be added as...

If all `on:...` handlers were exposed on the component in a similar way to `$$props`, it would be very easy to implement event forwarding in client code by iterating over...

@jnm2377 This is not about one of the component library implementations but the website, that is why there is no repro example. Follow [the link](https://www.carbondesignsystem.com/components/progress-indicator/usage/#live-demo) and click one of these:...

@Addeuz That should not be done anyway because of accessibility. If something should be clickable, it should be wrapped in a button or link.

`tabindex` is almost useless, if you do not additionally handle key events, the click handler will not fire on pressing enter/space if the element is not a link/button. Obviously links...