This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 9016 - Make parameters on applet use the same rules as object (except for codebase="")
Summary: Make parameters on applet use the same rules as object (except for codebase="")
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-16 09:18 UTC by contributor
Modified: 2010-10-04 14:56 UTC (History)
5 users (show)

See Also:


Attachments

Description contributor 2010-02-16 09:18:06 UTC
Section: http://www.whatwg.org/specs/web-apps/current-work/#sandboxPluginApplet

Comment:
Make parameters on applet use the same rules as object (except for
codebase="")

Posted from: 88.131.66.111 by simonp@opera.com
Comment 1 Ian 'Hixie' Hickson 2010-02-18 09:42:49 UTC
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Did Not Understand Request
Change Description: no spec change
Rationale: Could you elaborate on exactly what you mean here? Is this just the PARAM/null thing? Are we sure Java needs this?
Comment 2 Simon Pieters 2010-02-18 10:29:02 UTC
* don't instantiate the plugin if the element's document is not in a browsing context or is not fully active
* pass the parameters in insertion order
* PARAM:null
* wait with instantiating the plugin until end tag has been parsed
* kill the plugin if the element is removed from the document
* whatever else is done for <object> but not for <applet>; I'm sure I've missed something.

As for what's needed or not for compat, I'm not sure, but it seems better to use the same rules for both unless web compat requires differences.
Comment 3 Ian 'Hixie' Hickson 2010-02-25 04:33:08 UTC
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Accepted
Change Description: see diff given below
Rationale: Concurred with reporter's comments.
Comment 4 contributor 2010-02-25 04:34:15 UTC
Checked in as WHATWG revision r4807.
Check-in comment: Make <applet> more consistent with <object>.
http://html5.org/tools/web-apps-tracker?from=4806&to=4807