Re: [w3c/ServiceWorker] object/embed (#249)

We can only solve this if we know in advance whether the `<object>` will create a browsing context or not. That means setting the `type`, and whatever ensures strict type matching (it used to be `typemustmatch` but that seems to be gone now, replaced with `X-Content-Type-Options: nosniff` perhaps?).

However, if you're saying that this problem only exists when existing contents cannot be changed, then there's no point us fixing it, as it would still depend on existing content changing.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/issues/249#issuecomment-889760924