Bug 103417
Summary: | Manually dispatched "enter" event not fired for a TextTrackCue not attached to a TextTrack | ||
---|---|---|---|
Product: | WebKit | Reporter: | Antoine Quint <graouts> |
Component: | Media | Assignee: | Nobody <webkit-unassigned> |
Status: | NEW | ||
Severity: | Normal | CC: | chris.needham, eric.carlson, frances_c, graouts, karlcow, webkit-bug-importer |
Priority: | P2 | Keywords: | BrowserCompat, InRadar |
Version: | 528+ (Nightly build) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
URL: | https://wpt.fyi/results/html/semantics/embedded-content/media-elements/interfaces/TextTrackCue |
Antoine Quint
We fail the Opera-submitted test at http://w3c-test.org/html/tests/submission/Opera/media/interfaces/TextTrackCue/onenter.html.
We fail the first test because it doesn't appear that we dispatch the "enter" event on the TextTrackCue, possibly because it's not attached to a TextTrack or any sort of tree. The DOM events spec doesn't seem to force the element to be participating in a tree to allow an event to be dispatched to it, so I think the test is accurate and we have a bug (see http://dom.spec.whatwg.org/#concept-event-dispatch).
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/12758086>
Antoine Quint
We run into the same issue for the "exit" event as highlighted in the test at http://w3c-test.org/html/tests/submission/Opera/media/interfaces/TextTrackCue/onexit.html.
Frances Cornwall
I can't open the links, I think that the urls no longer exist: http://w3c-test.org/html/tests/submission/Opera/media/interfaces/TextTrackCue/onenter.html, http://w3c-test.org/html/tests/submission/Opera/media/interfaces/TextTrackCue/onexit.html.
Frances Cornwall
This bug is related to: https://bugs.webkit.org/show_bug.cgi?id=206344.
Karl Dubost
The current tests for this are probably
https://wpt.fyi/results/html/semantics/embedded-content/media-elements/interfaces/TextTrackCue?label=experimental&label=master&aligned
Karl Dubost
*** Bug 206344 has been marked as a duplicate of this bug. ***