Peter Fern

Whilst the changes in #130 did remove `Restorer`, the impact was much more pronounced than that. As a result, anywhere a `Component` is instantiated inside `Component.Render()`, with fields set from...

I have an itch that we may want to review the new API once it settles to confirm that we've arrived at the right conclusions, so I wouldn't mind keeping...

That is correct @shurcooL.

This appears to be behaving as expected - by implementing the `vecty.Keyer` interface, you allow vecty to _move_ elements around in a list, rather than mutate existing elements in place....

If you use a `vecty.List` instead of a slice, I think it does what you expect? https://gist.github.com/pdf/c689fa08b585197e917a3d382acdbe21 This is currently the recommended data type for containing dynamic lists of elements....

My notes for when we decide to tackle this: The slightly curly bit here is `vecty.Rerender()`, since we don't currently know where to insert the new DOM node for the...

Totally untested, but something like: ``` import "github.com/gopherjs/vecty/event" ... event.BeforeUnload(func(evt *vecty.Event) { evt.PreventDefault() // do your handling here } ... ``` Seems like it should do what you want, though...

> I'm not sure if you're expected to do it manually, or if Vecty should be making the top-most Namespace apply recursively to all children. Currently any tags that require...

> I actually don't think the generated SVG package will help here. After all, it still needs a simple API to create such elements as well. The current approach is...

Hrm, I guess we need to worry about code size for GopherJS. I have no problem with `SVGTag()` (my original PR for namespacing actually implemented it using `NamespacedTag()` :wink: ),...