Safari + CustomEvent target and srcElement are null causing TypeError: null is not an object (evaluating 'evt.srcElement.getAttribute') on yoyo.js:51

[shaynekasai]

There seems to be a recent issue in Safari causing CustomEvent to not include target and srcElement, we noticed this in afterProcessNode, you can see the error when you load up the Yoyo demo site. This causes our app not not function at all in Safari.

Version of Safari is 17.4.1
OS: MacOS Sonoma 14.4.1

Our current workaround will likely be a patch to coerce .target and .srcElement from .detail.elt in Safari but we're still trying to brainstorm around this. The bug may also be eminating from htmx

[jreviews]

@shaynekasai I see the error on the demo, but not on a local version of the app even though the local app doesn't work because the request URLs are wrong. I was able to get the local app working by replacing evt.target with evt.detail.elt. In these lines:

if (name === 'htmx:configRequest') {
	if (!evt.target) return

	Yoyo.bootstrapRequest(evt)
}

And

bootstrapRequest(evt) {
   const elt = evt.target
   ...
}

I would also need to spend more time testing a more complex app I have to see if there are any issues without and with the patch. Do you have any examples of components where you get an error, other than on the demo app?

[shaynekasai]

unfortunately we don't have anything public but what I ended up doing was temporarily coercing srcElement and target in the onEvent function -- not ideal but it works for now as I think there are a lot of references to srcElement so I suspect it will be more than just the aforementioned two places

			if (!evt.target) {
				Object.defineProperty(evt, 'target', {
					writable: false,
					value: evt.detail.elt
				});
			}

			if (!evt.srcElement) {
				Object.defineProperty(evt, 'srcElement', {
					writable: false,
					value: evt.detail.elt
				});
			}

[jreviews]

I was referring to some simple code examples where you know it fails. Please share your patched version of yoyo.js and I will use that as a starting point when I have more time to check this. Might also be a bug in Safari itself. Thanks.