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 11773 - Re: applet obsoleted It seems that the committee is being deliberately hostile to Java applets. This is based on the fact that, with the proposed change, it will no longer be possible to include an applet in such a way as to be compatible with all browse
Summary: Re: applet obsoleted It seems that the committee is being deliberately hostil...
Status: RESOLVED NEEDSINFO
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
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: 2011-01-17 00:59 UTC by contributor
Modified: 2011-08-04 05:12 UTC (History)
6 users (show)

See Also:


Attachments

Description contributor 2011-01-17 00:59:14 UTC
Specification: http://dev.w3.org/html5/spec/Overview.html
Section: http://www.whatwg.org/specs/web-apps/current-work/#top

Comment:
Re: applet obsoleted

It seems that the committee is being deliberately hostile to Java applets. 
This is based on the fact that, with the proposed change, it will no longer be
possible to include an applet in such a way as to be compatible with all
browsers that support applets.	It is desirable to write HTML code that will
work on all browsers that support the required features.  There are older
browsers that recognize Java applets but predated any alternative to the
<applet> tag.  Conforming to the proposed new standard requires breaking such
browsers.  And the incompatibility is completely unnecessary.  There is no
justification for breaking older browsers on that point.  The <object> syntax
is messier (because it tries to handle more things than just applets.)	The
original setup for applets had a simple, readable design.  The new proposal is
convoluted and unreadable and will not work on some browsers.  Standards
should increase compatability, not restrict it.

Any replies to pvblivs2@hotmail.com

Posted from: 68.96.63.232
Comment 1 Ian 'Hixie' Hickson 2011-02-16 09:45:14 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: Which browsers don't support the <object> syntax for embedding Java code?
Comment 2 Michael[tm] Smith 2011-08-04 05:12:32 UTC
mass-move component to LC1