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

site is borked #3001

Closed
Rich-Harris opened this issue Jun 10, 2019 · 15 comments
Closed

site is borked #3001

Rich-Harris opened this issue Jun 10, 2019 · 15 comments
Labels

Comments

@Rich-Harris
Copy link
Member

  1. go to https://svelte.dev/
  2. navigate to examples
  3. click the logo in the top left to go back to the homepage
  4. yikes

Screen Shot 2019-06-10 at 11 35 08

@s0kil
Copy link

s0kil commented Jun 10, 2019

Cannot reproduce this issue

@paulocoghi
Copy link
Contributor

paulocoghi commented Jun 10, 2019

That does not happen to me. The site is working perfectly on Firefox 67 - Ubuntu 18.04 64bits

@popaprozac
Copy link

popaprozac commented Jun 10, 2019

Reproducible on Chrome 74.0.3729.169 MacOS on second loop of steps 1-4.

@paulocoghi
Copy link
Contributor

Reproducible on Firefox 67 - Ubuntu 18.04 64bits

Thanks, @zb0t . In fact, it is happening every time now, after I repeated the steps.

@Conduitry
Copy link
Member

Conduitry commented Jun 10, 2019

I updated the version of Svelte the site uses this morning, which is probably what caused this. Running the site locally, it looks like this weirdness appears between Svelte 3.4.4 and 3.5.0.

edit: I don't always see this when following the steps in the OP, clicking quickly back and forth between nav links generally triggers it.

@Conduitry
Copy link
Member

I've locally rolled the version of Svelte the site uses back to 3.4.4 and have redeployed.

@popaprozac
Copy link

Behaving normally for me now

@paulocoghi
Copy link
Contributor

Those images on each item on the left-menu are on purpose?

@Conduitry
Copy link
Member

If I revert #2690, this issue with the site seems to go away locally. This is really mysterious, as that looked like a really obvious and correct fix.

@Conduitry
Copy link
Member

In particular, if I change this line back to the Clearly Definitely Wrong if (outro_block) {, rebuild Svelte, and link it into the site folder, this borkedness goes away.

@Conduitry
Copy link
Member

Something else that seems to make this go away (without reverting the above change) is removing the delay on the slide-in transition in https://github.com/sveltejs/svelte-repl/blob/master/src/Message.svelte - I wonder whether there's a corresponding bug to #2871 except with transitions.

@Conduitry
Copy link
Member

Conduitry commented Jun 14, 2019

I have pretty much no idea about the inner workings of Svelte's transitions, but: https://github.com/sveltejs/svelte/blob/master/src/runtime/internal/transitions.ts Look at create_in_transition - shouldn't there be a started = true; somewhere in there? If I put one right after the if (started) return; this seems to fix the issue.

edit: That may not in fact be the whole solution, but there's definitely something awry in create_in_transition.

edit again: Merely linking the svelte-repl dependency in here is seemingly causing the issue to go away, without changing its transition in Message. So I think I'm actually being affected by sveltejs/rollup-plugin-svelte#58 except in this case, this is a bug that is being masked by having two copies of Svelte's runtime.

edit: If I edit node_modules/@sveltejs/svelte-repl/src/Message.svelte in place to avoid the linking/duplication complication, then removing the delay from the in transition does not actually seem to help. Removing the out transition entirely does seem to help.

@Rich-Harris
Copy link
Member Author

ok i think i've made a minimal repro of the underlying bug: https://svelte.dev/repl/52955234b8a44873a37b104954854432?version=3.5.1

@Rich-Harris
Copy link
Member Author

possibly related: #2402

@Rich-Harris
Copy link
Member Author

looks like this is fixed in 3.5.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants