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.

Sign up for GitHub

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

Jump to bottom

"If" element is not defined, crashing bug #1780

Closed
jacwright opened this issue Oct 18, 2018 · 6 comments
Closed

"If" element is not defined, crashing bug #1780

jacwright opened this issue Oct 18, 2018 · 6 comments
Labels
bug

Comments

@jacwright
Copy link
Contributor

jacwright commented Oct 18, 2018 •
edited
Loading

I'm not sure how to repro. Hoping it can be figured out looking at the code.

Update: Got a repro. https://svelte.technology/repl?version=2.14.0&gist=08a1f063386aa2e78b4fb0d304b7a8de

Update 2: Another repro example, with an even more common case. An each inside an if. https://svelte.technology/repl?version=2.14.0&gist=66534e753e1044b66b439e4f3e4215b5

Update 3: This only seems to affect 2.14.0, not 2.13.5 like I had previously thought.

screen shot 2018-10-18 at 9 50 38 am
@jacwright jacwright mentioned this issue Oct 18, 2018
Closed
@jacwright jacwright changed the title If anchor is not defined "If" anchor is not defined, crashing bug Oct 18, 2018
@jacwright jacwright changed the title "If" anchor is not defined, crashing bug "If" element is not defined, crashing bug Oct 18, 2018
@stalkerg
Copy link
Contributor

Try my patch #1790 it can help to your case too.

@ItalyPaleAle
Copy link
Contributor

I have the same issue. Thanks for finding a repro code! I will revert to 2.13.5 for now

@Conduitry Conduitry added the bug label Oct 20, 2018
@Conduitry
Copy link
Member

Checked and this is still present in 2.14.1

stalkerg added a commit to stalkerg/svelte that referenced this issue Oct 22, 2018
@stalkerg
fix sveltejs#1780 just start use parent instead parent.parent in IfBl…
7ce35ec 
…ock wrapper
@stalkerg
Copy link
Contributor

#1792 should fix this issue

@Conduitry
Copy link
Member

Released 2.14.2 with @stalkerg's fix!

@btakita btakita mentioned this issue Oct 23, 2018
Closed
@netaisllc
Copy link
Contributor

Hey, I was experiencing this error in may build until I updated to 2.14.2. FWIW The problem has not resurfaced. Regards to the maintainers!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@ItalyPaleAle @jacwright @netaisllc @stalkerg @Conduitry