11773 2011-01-17 00:59:14 +0000 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 2011-08-04 05:12:32 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified Other other RESOLVED NEEDSINFO http://www.whatwg.org/specs/web-apps/current-work/#top P3 normal --- 1 contributor ian ian julian.reschke mike mounir public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 44379 0 contributor 2011-01-17 00:59:14 +0000 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 45687 1 ian 2011-02-16 09:45:14 +0000 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? 53303 2 mike 2011-08-04 05:12:32 +0000 mass-move component to LC1