Lukas Spirig

This should be solved by #3889

Yes, it is already possible. You can register your own icon namespace. ```ts import { mergeConfig } from '@sbb-esta/lyne-elements/core/config.js'; mergeConfig({ icon: { namespaces: new Map() .set('your-namespace', 'https://domain-of-your-icons/') } }); ```

Hello @daniel-sc I think for now (and the foreseeable future), we can definitely state that we will not support this for tightly coupled elements (i.e. ``, ``, ``, `` or...

I'll try to have a look at this as soon as I have some time to spare. I apologize, as this might take a while due to the current major...

As it currently stands, we have no interest (or capacity) in supporting native Windows development. For Windows, we strongly recommend developing with either [WSL](https://learn.microsoft.com/en-us/windows/wsl/install) or [Devcontainers](https://containers.dev/).

Are you using our React wrapper? https://www.npmjs.com/package/@sbb-esta/lyne-react

Ok, we will discuss this internally. I cannot promise a timeline for this.

Thanks for the investigation! Thinking out loud here; Could we adopt this logic for sbb-select, but keep the other logic for sbb-autocomplete (etc.)? From my understanding, the necessary logic can...

I would like to avoid separating into two different elements as our current html API is aligned with the upcoming select feature: https://developer.chrome.com/blog/rfc-customizable-select

@grubeninspekteur That's the approach https://www.npmjs.com/package/angular-server-side-configuration takes, which provides a native binary and examples for nginx. I wrote this library some years ago, as we had exactly these requirements of having...