Hans Raaf

@c3rtificate well, I have used go-app since the beginning in a way that it never reloads a page from the server. I don't see a problem with just updating attributes...

I may not understand your problem. I just use DOM manipulation through 'app.Window()' for whatever I need to change in the document. ```go app.Window().Get("document").Get("body").Get("classList").Call("add", "theme-dark") ```

Well. I think you need to accept that "Render()" on the objects is called all the time. It does not "render" the page, it updates the nodes of your (many...

The "Render()" is also just accessing the DOM and adds HTML elements and attributes, this is how a browser works. You can initialize a canvas and draw everything on that....

I am curious: Why would one have a component without any content? My root component does contain another component because I have a central navigation handler for all embedded components....

Nope, I have not and avoided that experience successfully so far. I still wonder how that relates to go-app, where a component is something that has a DOM node.

> So basically you can't have something like this, can you? Correct. But I am very fine with that because I do not want that component in the first place....

Well, I did not have any problem in our own larger projects yet and don't expect them. You have a point that compossibility suffers without having a nullable component, but...

I guess you should check your comment and correct the usage of the ``` code block. What I can see, from what I can see, it seems that you use...

I did not check, but can you even reliably use `ctx.LocalStorage()` outside the UI go routine? I would not try to do that. You need to have `ctx` for that,...