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
Following the first-timer instructions, I ran npm init svelte@next <my-app> and launched the app using npm run dev -- --open. The demo looks very nice, but I noticed some flaky behavior with the todo item trash buttons. They seem to work at first, but after creating a couple of items and clicking around a bit, they appear to become nonfunctional. I experimented with this a bit on Mac, both Safari 15.0 and Chrome 94.0.4606.61, and in both browsers it appears to be mostly broken.
I have easily reproduced this several times. If it turns out that this is less obvious than it seems, I'm happy to attempt a more detailed reproduction.
Reproduction
npm init svelte@next my-app
cd my-app
npm install
npm run dev -- --open
Navigate to the TODO section.
Create several todo items, then attempt to delete them and/or check/uncheck completion. After playing around for a few clicks I find that the trash buttons stop working.
Describe the bug
Following the first-timer instructions, I ran
npm init svelte@next <my-app>
and launched the app usingnpm run dev -- --open
. The demo looks very nice, but I noticed some flaky behavior with the todo item trash buttons. They seem to work at first, but after creating a couple of items and clicking around a bit, they appear to become nonfunctional. I experimented with this a bit on Mac, both Safari 15.0 and Chrome 94.0.4606.61, and in both browsers it appears to be mostly broken.I have easily reproduced this several times. If it turns out that this is less obvious than it seems, I'm happy to attempt a more detailed reproduction.
Reproduction
Navigate to the TODO section.
Create several todo items, then attempt to delete them and/or check/uncheck completion. After playing around for a few clicks I find that the trash buttons stop working.
Logs
No response
System Info
Severity
serious, but I can work around it
Additional Information
No response
The text was updated successfully, but these errors were encountered: