Skip to content

Order issue when setState changes vnode type in Fragment#1604

Closed
sventschui wants to merge 1 commit into
preactjs:masterfrom
sventschui:bug/fragment-reordering-issue
Closed

Order issue when setState changes vnode type in Fragment#1604
sventschui wants to merge 1 commit into
preactjs:masterfrom
sventschui:bug/fragment-reordering-issue

Conversation

@sventschui

Copy link
Copy Markdown
Member

This PR adds a test to showcase the ordering issue after setState when I was implementing #1593

As I don't have time to find a fix now I'll just open the PR with the test showcasing the bug. If nobody is faster than me I'll look into this tomorrow.

@sventschui sventschui mentioned this pull request May 5, 2019
7 tasks
@coveralls

Copy link
Copy Markdown

Coverage Status

Coverage remained the same at 100.0% when pulling 5f45c3b on sventschui:bug/fragment-reordering-issue into d7abd4e on developit:master.

@marvinhagemeister

Copy link
Copy Markdown
Member

This is an awesome test 👍 The error is caused by forceUpdate always appending new elements. It's not aware of any siblings yet :S

https://github.com/developit/preact/blob/d7abd4e0a2b7a6739882245e483d2f0e69348a34/src/component.js#L76

Will look into it later.

@sventschui

Copy link
Copy Markdown
Member Author

Closing as the fix will land with #1605

@sventschui sventschui closed this May 5, 2019
@JoviDeCroock

JoviDeCroock commented May 5, 2019

Copy link
Copy Markdown
Member

Let's keep this open until we land it, helps keep a clear overview. Great you're following up on things though :D Excuse me thought this was an issue and not a PR my bad 👎

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants