W3C home > Mailing lists > Public > public-html@w3.org > June 2008

[Bug 5757] New: MediaElement features are needed on OBJECT element

From: <bugzilla@wiggum.w3.org>
Date: Sat, 14 Jun 2008 10:57:55 +0000
To: public-html@w3.org
Message-ID: <bug-5757-2495@http.www.w3.org/Bugs/Public/>


           Summary: MediaElement features are needed on OBJECT element
           Product: HTML WG
           Version: unspecified
          Platform: All
               URL: http://esw.w3.org/topic/HTML/SpatialTemporalAudible
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Spec proposals
        AssignedTo: dave.null@w3.org
        ReportedBy: rob@robburns.com
         QAContact: public-html-bugzilla@w3.org
                CC: ian@hixie.ch, mike@w3.org, public-html@w3.org

* The new video and audio elements have many useful features valuable to
authors, but authors using the OBJECT element would also want to make use of
these MediaELement features
 * The VIDEO and AUDIO element’s create parsing tree construction problems in
legacy UAs whereas the OBJECT element with MediaElement features would not have
this problem
 * Arbitrary handlers may also be able to expose similar interfaces and make
use of the DOM methods and attributes and content attributes
 * Though some feel OBJECT is too overloaded to handle these features, the
current VIDEO element has virtually the same implementation as would be
necessary for the OBJECT element requires so it would be similarly overloaded
 * while not necessarily something HTML5 needs to address directly
implementations require — for better code maintainability — methods of
abstraction and code factoring that are independent from the elements these
classes are use with, i.e.,
  - implementations need to implement interfaces such MediaElement in a way
that it can be attached to any element regardless of its type name
  - DOM interfaces should be modularized for reuse by for instance separating
MediaElement and VideoElement interfaces into separate classes for 1)
networking, 2) audible, 3) spatial, 4) temporal, and 5) UI control interfaces —
where these interfaces can be attached to an element and have their methods and
attributes flattened for DOM interaction
   - (this is all to suggest the overloading issue is not a burden that should
be lifted off of implementors and placed on authors or by inaequately
specifying OBJECT element behavior, but instead handled through good code
 * Authors find it needlessly complicated to author using VIDEO and AUDIO in a
way that degrades gracefully in legacy UAs when required to use additional
elements that will not parse consistently and in an interoperable way across
existing UAs
 * Authors should be able to embed content using the OBJECT element with
minimal markup and expect UAs to provide sane default parameters and
presentation, but currently, prevalent browsers are not quite there yet (though

(see http://esw.w3.org/topic/HTML/SpatialTemporalAudible for evolving solution

[authoring issue, no additional implementation]

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Saturday, 14 June 2008 10:58:28 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 9 October 2021 18:44:32 UTC