Commit | Date | |
---|---|---|
2010-04-23 20:00:00 | Tree | |
[r1589]
by
oconnell@adobe.com
The SerialObjectDisplay trait was relying on a valid MediaElement's displayObject. Proxies broke this behavior. Fixes 767 and 768. |
2010-04-23 17:31:04 | Tree |
[r1588]
by
briggs@adobe.com
Don't let invalid cuepoints trigger an RTE in VideoElement, we should swallow them instead. Update comments and unit tests accordingly. |
2010-04-23 16:47:25 | Tree |
2010-04-22 22:29:17 | Tree | |
2010-04-21 23:41:58 | Tree | |
[r1585]
by
briggs@adobe.com
Rest of fix for FM-764. This fix ensures that a DurationElement will auto-rewind when played for the second time, this was the reason why the second play of the SerialElement in the bug resulted in a failure. |
2010-04-21 23:05:08 | Tree |
[r1584]
by
briggs@adobe.com
Partial fix for FM-764. This addresses the case where a capability change event was being dispatched prior to the capability getter being updated, thus making it seem as if a mid-roll was unseekable (on second play) when it was indeed seekable. |
2010-04-21 22:53:48 | Tree |
2010-04-21 22:45:26 | Tree | |
[r1582]
by
briggs@adobe.com
Improved fix for FM-347, where autoRewind false would prevent subsequent playback. The new fix is to base the autoRewind-on-play decision on an internal "mediaAtEnd" property rather than on the duration equalling the currentTime. The problem with the latter is that some media (e.g. HTTP streamed DVR content, as seen in FM-681) will dispatch the "complete" event without the currentTime equalling the duration, and in fact the currentTime may never end up equalling the duration. Added unit test to catch the original bug. |
2010-04-21 21:19:18 | Tree |
[r1581]
by
briggs@adobe.com
Update ExamplePlayer readme with instructions for using with Flex 4 SDK. |
2010-04-21 19:32:13 | Tree |