- From: <bugzilla@wiggum.w3.org>
- Date: Thu, 27 Aug 2009 13:58:01 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7442
Summary: Java applets are never conforming, and sometimes don't
work
Product: HTML WG
Version: unspecified
Platform: PC
URL: http://www.whatwg.org/specs/web-apps/current-
work/multipage/text-level-semantics.html#the-object-
element
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: HTML5 spec bugs
AssignedTo: dave.null@w3.org
ReportedBy: scampa.giovanni@gmail.com
QAContact: public-html-bugzilla@w3.org
CC: ian@hixie.ch, mike@w3.org, public-html@w3.org
The object element in HTML5 has the following attributes:
data
type
name
usemap
form
width
height
while in HTML4 it had all those plus
classid
codetype
archive
codebase
(and others, that are not important now)
In particular for Java applets, codetype is required to instantiate the JVM (to
say "this is a Java applet", archive or codebase are required to download the
.jar or .class files, classid is required to find out which class implements
JApplet.
On the other hand, HTML5 says that
1) authors must not use any of those attributes in an HTML5 document
2) UAs must not use any of codetype, archive, codebase to instantiate the
object
This means that a document may never use Java Applets, without using the applet
element, and in any case it isn't conforming.
Therefore I propose to reintroduce those attributes for the object element and
to rewrite the processing model accordingly.
PS: also the data attribute was relative to codebase in HTML4 and some content
may rely on it
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Thursday, 27 August 2009 13:58:10 UTC