Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bug] pushy and default block behaviour does not work #157

Closed
cachesdev opened this issue Dec 8, 2024 · 2 comments
Closed

[bug] pushy and default block behaviour does not work #157

cachesdev opened this issue Dec 8, 2024 · 2 comments
Labels
bug Something isn't working investigating Not quite sure if it's valid, yet

Comments

@cachesdev
Copy link

Describe the bug

moving around selectors wont respect either block or pushy, instead they will simply go over the other selector.
it will also generate a whole lot of svelte warnings. bug is most likely related to svelte5.

Link To Reproduce

repl

Steps to reproduce the behavior:

pick a selector, and try to go past the other one.

Expected behavior

1- selector gets blocked
2- in pushy mode, selector gets pushed

Screenshots

If applicable, add screenshots to help explain your problem.

Device/Environtment

discovered it on android webview, also happens in firefox and chrome. firefox gets really laggy.

@cachesdev cachesdev added bug Something isn't working investigating Not quite sure if it's valid, yet labels Dec 8, 2024
@simeydotme
Copy link
Owner

hmmm.....

but....

I see the warning issue (with the perf isuse, too)... the performance/lag is being caused by the thousands of console.warn() ... and those warnings are coming from Svelte 5.9.0 ... if you change it to 5.1.0 it is not causing any problems;

https://svelte.dev/playground/hello-world?version=5.1.0#H4sIAAAAAAAAE4WQwW6DQAxEf8XyGUhImwslUfoL7TGbAxCnrATe1dqkjRD_Xi20alRV6nVGb2bsEbnqCQsMFb8R1IOqY4F3xwp-kBZcAFHngaqmddpSwAQvtiPB4jii3nyEo4DJd9Sz95lcqdOo1ZXQX3rjWIlVsMBSmmC97g0btb13QeElrnnt7JkCXILrweBCpvPOVGYr9dbL4SHLs0eDTxHvSOFadQNJDjs4bhPI16dfziY6-TqBfButcvVTz-yWs2-Gy_sNteVzseC78atgguVnq73hmYH_oc20xN-hmKDSh2KhYaDpNH0CVO_otpIBAAA=

.... I don't know what Svelte have changed but it seems like it is ALMOST breaking change, and a little worrying to say the least.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working investigating Not quite sure if it's valid, yet
Projects
None yet
Development

No branches or pull requests

2 participants