Trevor N. Suarez

> I don't think this should be responsability of Svelte given that it can be trivially implemented in a few lines of code. > > ```ts > const generator =...

> `event.parent` is the intended way of doing this, but it is a little annoying as it results in a waterfall. Yea, that causes waterfalls and it has to be...

Hmm, yea this just bit me. I didn't understand why the event was just ignored when using linkify-string, until I found this issue. Strange.

Yea, I just ran into this too, but it wasn't with a store strangely... But yea, using the getter/setter pattern also resolved it with me, but again yea svelte-check was...

> EDIT: A good workaround is > > ```html > > window.addEventListener('beforeinstallprompt', event => { > event.preventDefault() > window.deferredInstallPrompt = event > }) > > ``` This is great, and...

Yea, I just ran into this while configuring CSP (via the [Content-Security-Policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Content-Security-Policy) header) on my site. I get the error: > Refused to execute inline event handler because it violates...

> Another alternative would be to use **unsafe-hashes**, since all inserted codes have the same content : `this.__e=event` > > => This works : > > csp: { > mode:...