Tao Xin

`GalleryThumbs` will be reactive because of `vanX.list`. But `selectedCanvasID` as a reactive primitive doesn't make much sense. You can simply use `van.state` for it. `vanX.reactive` is for objects or arrays...

I think you should use `selectedCanvasID.val` instead of `selectedCanvasID` for all its appearances.

I'm confused. Do you want `Thumb` reactive to `selectedCanvasID`, or not reactive to `selectedCanvasID`?

My understanding is class image shouldn't be reactive to the `selectedCanvasID`. Do you have a link to show the entire code?

Calling `GalleryThumb` will create the intersection observer. So that's a possibility. Without the access to the full code, I am not able to tell what exactly can trigger the calling...

Thanks for the suggestion! My current feeling is that since `isProps` function is quite easy to add on the client side (a just a couple lines of change) it probably...

My take is that adding `join(" ")` at the end isn't too much overhead. It probably doesn't worth the complexity of introducing the special handling of `class` property.

Hi @laoshaw, Here is an SPA example with client-side routing support, based on VanJS's powerful builtin state management and state derivation: https://vanjs.org/demo#code-browser

Thanks for raising this interesting point! The `__proto__` property is a tricky topic in JavaScript and understandably there are misunderstandings about it among developers. This is not the first time...

This is due to the behavior of `number`-typed `` element. When you delete `x`, `event.target.value` equals `1`, not `1.`, as only numbers are allowed in the input box.