inria / aiana-player Goto Github PK

WEBVTT format doesn't allow multiple line breaks, which is an issue when we want to use formats depending on line breaks (e.g. markdown).

While this isn't a problem when using HTML since line breaks can be stripped off, it makes any other format relying on line breaks unusable.

There was a regression leading bookmarks not to be displayed in the timeline.

Right now there is indication whether the media is seeking or not, and the player seems frozen when bandwidth doesn't allow for seamless loading.

This indicator could be shared with a more general purpose loading indicator.

The content timeline is an interactive element that allows users to navigate across content bound to a media time code: bookmarks, chapters, slides...

Referring to WAI-ARIA practices, the focused element should be the small handle (aka the thumb), not the whole component.

Configuration is hard coded, but it should be read from globals or imported from a remote file.

Windowed elements and controls are contained in the same element, resulting in an unwanted overlapping.

A way to avoid this would be to wrap all windowed elements (and only those elements) inside a dedicated element, and move the other ones elsewhere.

Moving, resizing, and closing windows should be optional.
v1 provides such an option, but is global to every window. A better implementation would use a per-window lock option, but use a single option to lock and unlock them at once, until we need more precise settings.

See #16

Sometimes, more than one TextTrack can have more than one active cue.
When this happens, the player keeps the one that was pushed first in the list, which can result in unexpected behaviour.

For example, If two cues A and B share the same timestamp for A end time and B start time, they are both considered active. When this happens, I think it is safe to consider track B should be displayed, not track A, as we don't handle multiple cues display on a same track (subtitles, chapters, etc).

For this reason, the active cue should be changed to the one with the highest index.

select may be suitable for regular form data with no context change, but is really difficult to style properly.

Drag handle width is 100%, making resize handles unreachable when pointer is in any window corner.

• A visual indicator could be used as a remainder to let users know in which chapter they are.
• ARIA attribute could be used to notify screen readers current chapter has changed.

In v1, any window can be hidden from the interface by toggling its status.

Adding this option would provide a better experience for a naked video player. Controls could be hidden when video is playing, resulting in a better fill size display.

Adding a main landmark ensures content will be accessible even if the page isn't played via an iframe.

There is no visual indication of what has been buffered so far. Most players are implementing it, and so does the current Aiana version.