[Bug 12970] New: Media Events: I think it should be added to the documentation how certain events should be handled main ones being seeked and seeking. Currently some browsers when seeking a media element they fire multiple events (pause, seeking, seeked, play). While som

http://www.w3.org/Bugs/Public/show_bug.cgi?id=12970

           Summary: Media Events: I think it should be added to the
                    documentation how certain events should be handled
                    main ones being seeked and seeking. Currently some
                    browsers when seeking a media element they fire
                    multiple events (pause, seeking, seeked, play). While
                    som
           Product: HTML WG
           Version: unspecified
          Platform: Other
               URL: http://www.whatwg.org/specs/web-apps/current-work/#top
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P3
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: contributor@whatwg.org
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


Specification: http://dev.w3.org/html5/spec/Overview.html
Section: http://www.whatwg.org/specs/web-apps/current-work/#top

Comment:
Media Events:
I think it should be added to the documentation how certain events should be
handled main ones being seeked and seeking.

Currently some browsers when seeking a media element they fire multiple events
(pause, seeking, seeked, play). While some others fire (seeking, seeked). This
needs to be standardized across browsers to make tracking events standard
across browsers.  

Posted from: 206.180.38.20
User agent: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/534.30 (KHTML, like Gecko)
Chrome/12.0.742.91 Safari/534.30

-- 
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, 16 June 2011 16:59:26 UTC