W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > November 2009

[Bug 8329] New: should object/@code be omitted from list of obsolete attributes?

From: <bugzilla@wiggum.w3.org>
Date: Wed, 18 Nov 2009 11:28:37 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-8329-2486@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8329

           Summary: should object/@code be omitted from list of obsolete
                    attributes?
           Product: HTML WG
           Version: unspecified
          Platform: PC
               URL: http://dev.w3.org/html5/spec/obsolete.html#non-
                    conforming-features
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec bugs
        AssignedTo: dave.null@w3.org
        ReportedBy: mike@w3.org
         QAContact: public-html-bugzilla@w3.org
                CC: ian@hixie.ch, mike@w3.org, public-html@w3.org


The "Non-conforming features" section of the spec lists "code on object
elements" as an obsolete attribute. But as far as I can tell, the code
attribute -- while widely used on the applet element -- was never valid on the
object element in any version of HTML and does not seem to be used in any
significant amount of existing Web content. See, for example,
http://dev.opera.com/articles/view/mama-plug-ins/#object

So, I'm wondering whether  the  "code on object elements" line should be
removed from that section (so that, e.g., conformance-checker developers don't
feel any need to do any special reporting for that case).


-- 
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 Wednesday, 18 November 2009 11:28:39 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:05 UTC