This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
<applet> can also initiate fetches, so we should probably add a RequestContext entry for it. Or at least a recommendation for how the implementors are supposed to reflect it.
Does <applet> initiate the fetches or is it the Java runtime?
The UA may need to download the Java applet before invoking the Java runtime if it's specified using the codebase attribute, but <applet> can also refer to locally existing Java classes.
Is that cross-browser? https://html.spec.whatwg.org/multipage/obsolete.html#the-applet-element does not mention any fetching.
Reusing "plugin" for this might be good enough?
(In reply to Anne from comment #3) > Is that cross-browser? > https://html.spec.whatwg.org/multipage/obsolete.html#the-applet-element does > not mention any fetching. I don't know, but the spec doesn't really look sufficiently detailed. (In reply to Anne from comment #4) > Reusing "plugin" for this might be good enough? "plugin" means a fetch from within a plugin (right?), which doesn't sound exactly right here.
https://github.com/whatwg/fetch/commit/5fe3a2dd90be0c164b8d81655ba0714c9979f5f6 I guess we can figure out later how all browsers implement this. Given that CSP places requirements on <applet> too, this makes sense for now.