Why a NIP-5D napplet binding was revoked.
window-message
napplet.hello
second-hello
invalid-hello
second-load
port-closed
deferred-overflow
filterNappletMessage
nested-context
host
Why a NIP-5D napplet binding was revoked.
window-message— a window-level message other than the onenapplet.hello.second-hello— a secondnapplet.hellofrom the same iframe.invalid-hello— anapplet.hellowithout exactly one transferred port.second-load— the iframe loaded a second document (navigation or reload).port-closed— the bound port closed or failed to deserialize a message.deferred-overflow— too many envelopes were waiting onfilterNappletMessagedeferral.nested-context— a napplet running under the experimental nested-context lock held a child browsing context.host— the host revoked the binding itself.