You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm playing with web-awesome in svelte kit, and the wa-button with href somehow "loose" their style and can no longer be focused when I'm navigating (using SvelteKit's SPA mode).
I reproduced it in a more minimal way, and it also happens when a new wa-button is dynamically created (except for first one 🤷).
Non-link button looks fine.
To Reproduce
Steps to reproduce the behavior:
Create a new bare bone svelte project: npm create vite@latest
Update the index.html to include the webawesome CSS and script
<script>letbuttons=$state([]);functioncreateLinkButton(){buttons.push('wa-button as link');}</script><buttonclass="wa-brand" onclick={createLinkButton}>Create new wa-button with link
</button><hr/>
{#each buttons as button}
<wa-buttonhref="/">{button}</wa-button>
{/each}
Screenshots
20250221-1000-33.3201258.mp4
⬆ The first button created is fine, the subsequent ones loose their bakcground color and are no longer focusable
Browser / OS
OS: Windows
Browser: Chrome
Browser version: 133.0.6943.127
Additional information
Provide any additional information about the bug here.
The text was updated successfully, but these errors were encountered:
Describe the bug
I'm playing with web-awesome in svelte kit, and the
wa-button
withhref
somehow "loose" their style and can no longer be focused when I'm navigating (using SvelteKit's SPA mode).I reproduced it in a more minimal way, and it also happens when a new
wa-button
is dynamically created (except for first one 🤷).Non-link button looks fine.
To Reproduce
Steps to reproduce the behavior:
npm create vite@latest
src/app.css
src/App.svelte
withScreenshots
20250221-1000-33.3201258.mp4
⬆ The first button created is fine, the subsequent ones loose their bakcground color and are no longer focusable
Browser / OS
Additional information
Provide any additional information about the bug here.
The text was updated successfully, but these errors were encountered: