Closed mmontone closed 2 years ago
One thought that comes to mind if you are using create-child is that perhaps the html you are passing to create-child has no outer tag and so no ID can be assigned to it to create a valid clog-element. (I will do some experiments)
Example "<p>hello</p><p>how are you?</p>" would be an issue. "<span><p>hello</p><p>how are you?</p></span>" would be ok.
Well that thought doesn't seem to create a similar issue.. at least in a one off.
I have seen that error show up in the past on connection shutting down mid event. If you can give me a bigger snippet or something that recreates happy to flush out the error. In mean time will try and reproduce.
Thanks. Don't worry about this. This probably some issue with my code. I was asking just in case. I'm closing for now and I'll report when I find something.
I think where the problem is. The dom element I'm trying to attach to is not being properly created browser-side. Has to do with some library usage, etc.
Either way I am going to handle this error more gracefully as can happen in a race condition between setting an event and a connection closing. Thanks!!!
Sometimes I get the following error:
after trying to set-on-event after creating a clog-element with create-child.
Error occurs in set-event, when trying to set the handler:
(setf (gethash hook (connection-data obj)) handler)
Have you encountered this before? Perhaps I'm doing something wrong ... I don't see these for all cases.